Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renaming a already established connection does not update any connected P2Ps accordingly #14

Open
Speecker opened this issue Jun 14, 2024 · 2 comments
Labels
question Further information is requested

Comments

@Speecker
Copy link

Speecker commented Jun 14, 2024

As the title says i noticed yet not connected ones change their name to the newly connected p2p.
But if you rename already connected ones it doesnt update the name change on any connected p2p.
Running MC1.20.1 v1.4.1 Forge

@LasmGratel LasmGratel added the question Further information is requested label Jun 14, 2024
@LasmGratel
Copy link
Owner

There's a confusion in renaming an entire "channel" or solely a P2P device, I will look into it

@Speecker
Copy link
Author

Speecker commented Jun 14, 2024

The behavior in GTNH (as a reference) is that it renames all p2p points that are connected to the one u renamed to match that name.
I would have assumed it was meant to behave like that with the 1.20.1 port as well ?
Otherwise you would have to rename each connected p2p point individually.
I'd understand this as an entire "channel" of p2p points that form a group to keep organized.
In large bases this will be for example a bunch of different fluids where you need each of them multiple times and possbily have mutliple sources or sub routes that would became chaotic quickly if you would have to rename each individual point whenever you make a edit to the naming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants