This is overkill for a game with a modding API.TheTom wrote:You need to update. All mods broke. This definitely need some (a lot) more rework. But for now - waiting for the mods to update...
So once in a while, you choose to reset all mods, to see which ones are going to be updatedKlonan wrote:When they update to 0.14, they can actually load the game, and update and see which mods have not been updated
That's rude, but I suppose it's a good filter 
Except now mod authors have to maintain multiple versions of the same mod where quite likely the only difference is that 1 line. As long as the API for the functions they are using hasn't changed, it should be compatible. If it has changed then they can have 2 different versions where one has the new API and one has the old.Klonan wrote:binbinhfr wrote:Only on a modding point of view, there is not much difference between 0.14.0 and 0.13.18 than between 0.13.17 and 0.13.18 . So why this need to reset ? You did not force us to reset between 0.13.17 and 0.13.18... Mysterious to me... And effectively very annoying when you have more than 20 mods to update...kovarex wrote:This invalidates all the mods for old version automatically, it might be little annoying, but it solves a lot of trouble.
By the way, I still use Dependencies on base, because sometimes you change API between 2 subversions and the mod is not retro compatible in this case, otherwise people who do not update factorio, but update the mod have problems.
For the end user this system works better,
When they update to 0.14, they can actually load the game, and update and see which mods have not been updated,
Before, when you update say 0.11 to 0.12, your game would just crash when it tried to load, and you would have to manually go to the mods folder and delete mods until it worked
I hope this doesn't require all of the Lua code to be changed into Lau code.Changed LauItemStack::grid to return nil if the item doesn't have a grid.
One 0.12 and one 0.14? Stable and Experimental branch? Sounds good to me.iamwyza wrote:Except now mod authors have to maintain multiple versions of the same mod where quite likely the only difference is that 1 line. As long as the API for the functions they are using hasn't changed, it should be compatible. If it has changed then they can have 2 different versions where one has the new API and one has the old.Klonan wrote:binbinhfr wrote:Only on a modding point of view, there is not much difference between 0.14.0 and 0.13.18 than between 0.13.17 and 0.13.18 . So why this need to reset ? You did not force us to reset between 0.13.17 and 0.13.18... Mysterious to me... And effectively very annoying when you have more than 20 mods to update...kovarex wrote:This invalidates all the mods for old version automatically, it might be little annoying, but it solves a lot of trouble.
By the way, I still use Dependencies on base, because sometimes you change API between 2 subversions and the mod is not retro compatible in this case, otherwise people who do not update factorio, but update the mod have problems.
For the end user this system works better,
When they update to 0.14, they can actually load the game, and update and see which mods have not been updated,
Before, when you update say 0.11 to 0.12, your game would just crash when it tried to load, and you would have to manually go to the mods folder and delete mods until it worked
Or worse : in ULLA code, see this very old but famous french advertisingNurstin wrote:I hope this doesn't require all of the Lua code to be changed into Lau code.Changed LauItemStack::grid to return nil if the item doesn't have a grid.
Don't use any beta...Uxi wrote:How does one select 0.13.18 on Steam?
I can only select between 0.12.35 and 0.14.0...
-None- Should get you 13.18Uxi wrote:How does one select 0.13.18 on Steam?
I can only select between 0.12.35 and 0.14.0...
One for 0.13 and one for 0.14.Kamel wrote:One 0.12 and one 0.14? Stable and Experimental branch? Sounds good to me.
Code: Select all
"factorio_version": "0.13",
"dependencies": ["base >= 0.13.17"]
Code: Select all
"factorio_version": "0.14",
"dependencies": ["base >= 0.13.17"]Experimental is what it says: "experimental" = for trial only.kyranzor wrote:So if i update my mod with factorio_version = 0.14 , all my users who are on .13 still (99.9%) will be unable to load the mod, and the few who have started using 0.14 already will not be able to use it.
Where is the safe middleground? How can I update my mod so that both 0.13.18 and 0.14 users can use it without a huge headache?
There is no middleground. 0.14 is quite special, as it doesn't invalidate most of the mods, but other major releases are not like that. And we prefer to make it easy for the users rather than mod developers. You would have to update your mod once, but thousands of users (potentially) would have to manually solve problems if they get outdated mod in their mod folders.kyranzor wrote:So if i update my mod with factorio_version = 0.14 , all my users who are on .13 still (99.9%) will be unable to load the mod, and the few who have started using 0.14 already will not be able to use it.
Where is the safe middleground? How can I update my mod so that both 0.13.18 and 0.14 users can use it without a huge headache?
I think the issue is the in game update mods link pulls the latest version of a mod with no additional filter. Now users that don't update their game will get disabled mods on using the in game updater.kovarex wrote:There is no middleground. 0.14 is quite special, as it doesn't invalidate most of the mods, but other major releases are not like that. And we prefer to make it easy for the users rather than mod developers. You would have to update your mod once, but thousands of users (potentially) would have to manually solve problems if they get outdated mod in their mod folders.kyranzor wrote:So if i update my mod with factorio_version = 0.14 , all my users who are on .13 still (99.9%) will be unable to load the mod, and the few who have started using 0.14 already will not be able to use it.
Where is the safe middleground? How can I update my mod so that both 0.13.18 and 0.14 users can use it without a huge headache?
It's almost true... since now for each mod there is a need to publish same version twice with different factorio_version tag to allow people from both versions get the update. And since most of the code will work as is this will be the real pain for modders.kovarex wrote:There is no middleground. 0.14 is quite special, as it doesn't invalidate most of the mods, but other major releases are not like that. And we prefer to make it easy for the users rather than mod developers. You would have to update your mod once, but thousands of users (potentially) would have to manually solve problems if they get outdated mod in their mod folders.kyranzor wrote:So if i update my mod with factorio_version = 0.14 , all my users who are on .13 still (99.9%) will be unable to load the mod, and the few who have started using 0.14 already will not be able to use it.
Where is the safe middleground? How can I update my mod so that both 0.13.18 and 0.14 users can use it without a huge headache?
