[2.0.21] Renaming logistic group creates new group instead

[factoriouzr]

Allow renaming requester settings without creating a new request section. Behaviour unintuitive.

Expected behaviour: Renaming a request should just rename it. If you go into the gui to select from existing requests, there should be a button to copy an existing request and a popup should appear to give it a new name.

It's not intuitive at all that renaming a request would make a copy of it.

[LCStark]

I guess it's been made that way to prevent you accidentally renaming the group on other combinators and chests that could be using it. If you're sure that's what you want to do, hold Control while applying the name change.

group.png (40.27 KiB) Viewed 461 times

[factoriouzr]

The expected behaviour is that Other combinators and chests that use the group should still be using the same group after the rename. Ie. the group should be renamed without changing what other entities use. Ie. all existing entities that used the group before the rename should now use the same group after the rename. Ie. the entities should all auto-update. The default should be to rename the group and not make a copy of it. It's so not intuitive that the rename button creates a copy of the group. I just want to rename the group. This is a common operation. It works this way for other entities, like train names, blueprint names, etc. When I rename a train or blueprint, you don't get a duplicate of that train or blueprint. The current behaviour is not intuitive and inconsistent with how other rename operations in the game work.

Think of it this way... I create a group and realize I have a typo or I want a different name for it. I press the rename button and without even realizing it (unless you already know that it works not intuitively), under the hood it created a new group. Then later on I find I want to rename the group again and it creates another copy under the hood. Then later I add a whole new group, go to the group list and see there are tons of similarly named groups. It's just a huge mess.

The bottom line is: This is not intuitive and it's inconsistent with all other rename operations in other GUIs in the game.

Rename should be easy and non-destructive. If I want a copy of a group, I should be able to click an explicit copy group button like I do for blueprints.

[LCStark]

The expected behaviour is that Other combinators and chests that use the group should still be using the same group after the rename. Ie. the group should be renamed without changing what other entities use. Ie. all existing entities that used the group before the rename should now use the same group after the rename. Ie. the entities should all auto-update. The default should be to rename the group and not make a copy of it. It's so not intuitive that the rename button creates a copy of the group. I just want to rename the group. This is a common operation. It works this way for other entities, like train names, blueprint names, etc. When I rename a train or blueprint, you don't get a duplicate of that train or blueprint. The current behaviour is not intuitive and inconsistent with how other rename operations in the game work.
[...]

Hey, no argument from me there. I too expected it to work the other way around - rename all by default, create a copy with a modifier key. It took some time to get used to this system. But it's not a bug, it's working as the devs expect it to. I'd agree that it isn't intuitive, so it's a good suggestion to change it.

The bottom line is: This is not intuitive and it's inconsistent with all other rename operations in other GUIs in the game.

Almost all of them, there is one operation that works almost exactly the same, and it looks like that behaviour was reused for the logistic groups. That is renaming train stops - by default, it renames just the train stop you are editing, leaving all others using that name untouched, and holding Control changes them all.

And that actually makes the logistic groups renaming feel even more weird. With train stops it works, because when you rename the last stop with that name, all trains using that stop will adapt their schedule to use that new name. But with logistic groups the group gets stuck in limbo with no combinator or requester using it.

[Loewchen]

This is working as intended, for renaming you need to hold Control. You can make a suggestion here: viewforum.php?f=6.

[factoriouzr]

This is working as intended, for renaming you need to hold Control. You can make a suggestion here: viewforum.php?f=6.

I already made a report here. Please move it to ideas ans suggestions if you don't like calling it a bug. To me this is a bug as it's unintuitive, but you can classify it however.

[Muche]

I already made a report here. Please move it to ideas ans suggestions if you don't like calling it a bug. To me this is a bug as it's unintuitive, but you can classify it however.

I'd say the original post does not conform to the Ideas and Suggestions formatting/template guidelines - Read this before making suggestions!, Suggestion Template.

[Loewchen]

And it's an original report, so it needs to stay. You can copy or quote what you need to create your suggestion.