🌐Planet Rubia


Discover the wind planet Rubia. Belts and inserters work differently on Rubia, leading to unique building challenges not seen on any other planet. Your whole factory must go with the wind as a never-ending barrage of waste is hurled at your base.

Content
5 days ago
2.0
15.6K
Factorio: Space Age Icon Space Age Mod
Planets Logistics Trains Environment Mining Manufacturing Power

g [Not a Bug] Long handed inserters not merged with other mods

4 months ago

The moshine planet adds one long handed inserter, I noticed that you do have some compatibility (that module tech), so I just want to point at the fact that both rubia and moshine add a long handed stack inserter. Maybe remove one of them when both mods are installed?

4 months ago
(updated 4 months ago)

Thank you for the report.

Consider these scenarios:
-My code removes Rubian long stack inserters IF Moshine is installed. Then: someone beats Rubia, does the hard biofusion science line, unlocks/automates Rubia's long stack inserters. They now add Moshine to your save file. My code removes my stack inserters, wrecking chunks of their base.
-My code removes Moshine long stack inserters IF Moshine is installed. Then: someone beats Moshine, uses Moshine stack inserters, uses them, then later add Rubia to their save file. My code removes their inserters, destroying chunks of their base.

Basically, I cannot do what you propose without wrecking someone's save upon the addition of one of the planet mods. This is not acceptable, so we just need to live in a world with both. Sorry.

4 months ago

But isn't it possible to simply replace all the long inserters on like first world load? Though I guess that would wreck havoc if someone then removed Rubia, cause all of the long stack inserters would switch to those and be removed...

But there must be a better way than this, maybe not removing but hiding one of the long stack inserter technologies if both mods are present? So both inserters can be used on worlds where one mod was added after the other, but all players who have started a playthrough with both mods have a less confusing time?

Also both of them are widly different, the rubia one has a rot speed of 432 degrees, while the moshine one has 648. So maybe it would be a good idea to either make them different or similar enough to not cause a problem because someone confused one with the other and now has a slower rotational speed.

4 months ago
(updated 4 months ago)

I made my long inserters the way that I did (colors, stats, recipe, tech requirements, etc) based on the needs and philosophy behind my mod. I will not be altering the gameplay of my inserters just because Snouz also has long stack inserters.

I know there are many other mods out there with long stack inserters. I explicitly coded my inserters as a separate entity ("rubia-long-stack-inserter") to avoid overwriting inserters of other mods, because this causes many of the issues outlined in this thread. This way everyone can do their own thing without making a mess of conflicting mods.

FYI Several other planet creators warned me in advance to give my items unique names to avoid conflicts--especially for T4 modules and long inserters.

2 months ago

Apology for the thread necromancy here. Would a possible solution to this problem be to introduce a mod setting that the user can toggle to either include or not include the research/recipe for the Rubia stack inserter & module that conflicts with other planet mods? I myself also view the repeat entities as a bit taboo in mods, so having that ability without breaking the handshake between Moshine/Rubia is something I feel could be done.

2 months ago

I understand your frustration, but this is simply not Rubia's nor Moshine's responsibility because these are planet mods--not entity merging mods. This is in addition to the technical issues of json migrations, which cannot decide if/what entities to merge by looking into your settings or what mods you had installed first.

What you are looking for is a separate mod that consolidates these sorts of entities with its own rules. Even if such a mod does not exist, that would not justify adding a feature into Rubia that it should not have.

New response