- Deconstruct any underground belt exit
- Wait for bots to remove it
- Undo it
- The underground belt exit will be replaced with an underground belt entrance. Has the wrong rotation too
[2.0.67] Underground belt exits are replaced by entrances after deconstruct-undo
-
- Inserter
- Posts: 41
- Joined: Thu Oct 31, 2024 4:43 am
- Contact:
[2.0.67] Underground belt exits are replaced by entrances after deconstruct-undo
- Attachments
-
- deconstruct-undo underbelt exit reverse 2.mp4
- (2.91 MiB) Downloaded 8 times
Re: [2.0.67] Underground belt exits are replaced by entrances after deconstruct-undo
This also happened to me when I used the upgrade planner to change the belt tier
Re: [2.0.67] Underground belt exits are replaced by entrances after deconstruct-undo
Confirmed that this is happening in recent experimental version 2.0.67. Turned off all mods, still happens. I thought it might be something in the creative mod, but it is in the vanilla game with space age at least.
Please fix quickly, it is really annoying.
Please fix quickly, it is really annoying.
Re: [2.0.67] Underground belt exits are replaced by entrances after deconstruct-undo
Thanks for the report. Issue is now fixed for 2.0.68.
It looks like this issue got introduced due to changes made for 130707 since there was a logic error where copying settings allowed to change loader type and the same logic error was present with underground belts in some extreme modded use cases (when mods marked underground belts as supporting copy settings through additional_pastable_entities). It looks like UndoRedo was not adjusted correctly in .67 causing this bug to appear, however now i made it work correctly and as such the issue will be fixed.
It looks like this issue got introduced due to changes made for 130707 since there was a logic error where copying settings allowed to change loader type and the same logic error was present with underground belts in some extreme modded use cases (when mods marked underground belts as supporting copy settings through additional_pastable_entities). It looks like UndoRedo was not adjusted correctly in .67 causing this bug to appear, however now i made it work correctly and as such the issue will be fixed.