I think it's positive to have alternatives, if one of you stops supporting his mod because of lack of time/interest, there can always be an alternative..
Code: Select all
{
"name": "Factorio-Time-Lapse-Maker-master",
"version": "0.1.1",
"title": "TimeLapseMaker",
"author": "LithDev",
"contact": "",
"homepage": "",
"description": "Adds a simple tool to create Time Lapses",
"dependencies": ["base"]
}I'm the author of the "Time Lapse Mod" mod for Factorio 0.11.x and 0.12.xKoub wrote:Absolutely not
In the case you had used part of the other mod to make yours, however, you would have been expected to give proper credit, and keep and respect the original licence. And as the other mod was published under http://creativecommons.org/licenses/by-nc-nd/4.0/, the Non derivative wouldn't have allowed you to distribute modified versions of it.
But if your mod was entirely made without reusing anything from the other one, then this is a non-problem
-- if this option is set to "true" the game time will be changed shortly while taking a screenshot so all screenshots are taken at noon; default: false
onlyDayScreenshotsCFG = false
I'm not sure that is possible.Senshi wrote:Second issue:
The script apparently is MP synced. If one user sets up a new timelapse, this also happens with all connected players, and they get the screenshots taken as well. Which might be a nasty surprise if their %appdata% gets flooded with unwanted .png files.
It'd probably be best to not have the script setup broadcast in the network, so every user can do his own timelapses however he wants.
The devs are so paranoid about desync that they even try to replicate file writes.As far as I know there is no "true" server, the server is just another peer, like all the players, therefore every player has to have the same mods install.DaveMcW wrote:I'm not sure that is possible.Senshi wrote:Second issue:
The script apparently is MP synced. If one user sets up a new timelapse, this also happens with all connected players, and they get the screenshots taken as well. Which might be a nasty surprise if their %appdata% gets flooded with unwanted .png files.
It'd probably be best to not have the script setup broadcast in the network, so every user can do his own timelapses however he wants.
Thanks for the Input! I added support for "Nightless" mode and I tried to fix the multiplayer file sync issue. There is an option in the take_screenshot() function to say which player is taking the screenshot, maybe this will fix it? I don't have any way to test in multiplayer, so if anyone could let me know if this works, that'd be greatSenshi wrote:I like this mod, the GUI is simple and works well.
Two issues I noticed:
The day/night cycle can be very annoying for "long-duration" timelapses which are transformed in a high-fps gif.
Example of why this can be annoying: https://www.youtube.com/watch?v=2FusxEWCw2I - It's hard to actually discern the progress being made in the base during nights. With an even higher fps, it would lead to a severe stroboscope-like effect.
MrP's mod offers an option to switch the gametime to Noon for the screencap tick, ensuring uniform illumination in all pictures:-- if this option is set to "true" the game time will be changed shortly while taking a screenshot so all screenshots are taken at noon; default: false
onlyDayScreenshotsCFG = false
Second issue:
The script apparently is MP synced. If one user sets up a new timelapse, this also happens with all connected players, and they get the screenshots taken as well. Which might be a nasty surprise if their %appdata% gets flooded with unwanted .png files.
It'd probably be best to not have the script setup broadcast in the network, so every user can do his own timelapses however he wants.
not the best service, many will not be able to downloadtinyupload
With github you have the ability to post downloadable releases for your repositories which works amazingly. It's also very use to setupFactorio2016 wrote:Perhaps it would be better if you put it on github.
What I do is:LithDev wrote:The issue I had with GitHub was that it was downloading the zip as "TimeLapseMaker_0.1.2-master.zip", which would be incompatible with the info.json. Is there a way to change what the file would be downloaded as?
Edit: Tried making a release out of it and messed around some settings, closest I could get was "TimeLapseMaker-0.1.2.zip", which is still incompatible :/
Beautiful. Thank you for the tip!Roktaal wrote: What I do is:
1. Download ZIP (from GitHub)
2. Change the name of the zip file and the name of the folder inside to what it needs to be
3. Draft a new release on GitHub uploading the changed file
Then I use a link to that file on GitHub as a download link in the thread
