Topic.
Today's Barreling Machines update broke the compatibility.
What should we do?

Looking into it, but there's a 50/50% chance this mod will become deprecated. He's a pretty stubborn guy and is very unlikely to change his mind about anything tbh

First thing I will check is if the other auto-barreling mods actually work with Pelagos now. That was the primary reason this mod existed in the first place, so if they just work now, then I guess it's fine.

If they don't work (they didn't last time I checked), then I'll look into it. There's a possibility to maybe reverse the blacklisting, if I add a setting to duplicate the machines instead of modifying them directly, and then make that setting the default. That should circumvent his primary concern, while allowing the rest of us the ability to use the mod as before.

Four solutions atm:

1. Manually download and enable Talandar's Barreling Machines v0.1.2, restart the game, then enable this mod. While Barreling Machines will be locked to an older version, Pelagos and its other dependencies can currently still be updated as normal.
   This is likely to be a temporary stopgap, since it can be easily broken if Talandar updates Pelagos or any of its other dependencies to force a higher version of Barreling Machines.

2. Every time you download an update of Talandar's Barreling Machines, you can extract the mod's info.json and manually remove the line:
   "! pelagos-autobarreling"
   (also remove the comma from the line above, regarding "diesel machines", or else the folder will be ignored entirely)

3. Extract the most recent version of this mod, then change the name of the folder and the name under info.json to literally anything else (as long as they match each other). Make sure to keep the version numbers in the folder name; check the FAQs for more info

4. Use FCT's Barreling Machine for Pelagos instead. It enables compatibility between FCT's Barreling Machine and Pelagos, which accomplishes the original goal.

Thanks, I had already done 1 while waiting.
To do 4, I should also update the json of pelagos, right?

Ah, you already did. Great.
Thanks a lot!

Four solutions atm:

1. Manually download and enable Talandar's Barreling Machines v0.1.2, restart the game, then enable this mod. While Barreling Machines will be locked to an older version, Pelagos and its other dependencies can currently still be updated as normal.
   This is likely to be a temporary stopgap, since it can be easily broken if Talandar updates Pelagos or any of its other dependencies to force a higher version of Barreling Machines.

2. Every time you download an update of Talandar's Barreling Machines, you can extract the mod's info.json and manually remove the line:
   "! pelagos-autobarreling"
   (also remove the comma from the line above, regarding "diesel machines", or else the folder will be ignored entirely)

3. Extract the most recent version of this mod, then change the name of the folder and the name under info.json to literally anything else (as long as they match each other). Make sure to keep the version numbers in the folder name; check the FAQs for more info

4. Use FCT's Barreling Machine for Pelagos instead. It enables compatibility between FCT's Barreling Machine and Pelagos, which accomplishes the original goal.

2 and 3 also require to edit the "barreling_machines <= 0.1.2" in your mod, you would not have to do any of these 4 points, if barreling_machine were still on 0.1.2, since someone updated, your mod would mark anything >0.1.2 as incompatible as well.

Very important note, I forgot I added that bit to the latest updates.

Officially speaking, I want the "final update" that is available directly from the mod portal to have that restriction so that it will force the user to download Barreling Machines v0.1.2 manually. I'll add a note about editing that line to the FAQ section

Haha, downloading the previous version no longer works. When the author saw we found a way to use the mod, they proceeded to delete the necessary repositories. So now what? I can't continue my 300-hour save file without damaging my factory because of this intentional block. After the update, the original file was lost, and I can't find a way to recover it.

The last option is to modify the file. Thanks for the information.

WOW

I can't imagine putting so much effort into making sure somebody else's mod doesn't work, even in an unofficial capacity. I've updated the main mod again to remove the, now pointless, maximum version restriction. I've also updated the FAQ section once again to remove that info, as well as to add some more context.

I'll be keeping a google drive version up-to-date, in case he tries to blacklist whatever name it's currently under. It's easier for me to update the mod name when it's off the mod portal, than it is for him to keep adding new names to his blacklist on the mod portal. Sucks for anyone who wants to play with this mod in multiplayer though

Jesus Christ, what an asshole, I didn’t even know you could take old versions of mods down. Surely that’s gonna break things for other people? What the fuck.

I was working on a fork of Pelagos a while ago plus submods to make some changes Talandar was intentionally rigging his mod to prevent but I never publicly released it, but seeing THIS I will definitely have to finish those up and release them. This is genuinely the pettiest most insulting thing I’ve ever seen in all my years of modding.

Here is a reupload of v0.1.2, the only real changes made since are a couple of fixes and the petty script, so this should work for the foreseeable future.

While I completely disagree with the way Talandar has handled this whole situation, I'd rather not be completely antagonistic by forking his planet/submods, just to get one change that I personally want in my game (and that other people clearly want in theirs). Splitting up the install base just seems like a bad idea, even if it would get me what I want.

He seems to be unusually protective of his planet, while I believe that other modders should be allowed to do what they want (and I don't believe he should blame the existence of my mod, when the problem only occurred because of random person A using random person B's modpack and misunderstanding the situation)

At the very least, I already know that there are solutions to get around the blocks he's set up, that don't involve modifying his code (so I can keep updating them without issues, while preserving the functionality that I want) but I probably won't release that info publicly (because it would be just as simple for him to un-circumvent my circumvention, and I'd rather not get into a whole arms race over this; I'm too busy with my other mods as it is).

I'm sure others can figure out how to circumvent the blocks, if they study the control code long enough.

Regardless, once Factorio 2.1 hits stable (or when Pelagos hits 2.1, whichever comes first), I'll deprecate this mod and just focus on the FTC Auto-Barreling Fixes mod, which provides a close-enough experience that doesn't touch his barreling machines (and has more compat with some of FTC's other barreling related mods)