Request: Default encoded network ID

Adds new train stops forming a highly configurable logistic network.

Moderator: Optera

Post Reply
rdrunner
Burner Inserter
Burner Inserter
Posts: 6
Joined: Thu Sep 13, 2018 9:14 am
Contact:

Request: Default encoded network ID

Post by rdrunner »

By default each station is treated to belong to network FFF...

Can we define a default if this number is missing in the options?

It would make setting up a new network later MUCH easier since i don't need to assign ALL stations to a default network.

User avatar
Optera
Smart Inserter
Smart Inserter
Posts: 2915
Joined: Sat Jun 11, 2016 6:41 am
Contact:

Re: Request: Default encoded network ID

Post by Optera »

Turning a user defined bitmask into default would make finding errors much harder.

It wont even save much work.
Station blueprints for new network or combined network stops would have to have network id's included regardless.
Speaking from experience, stamping a blueprint with updated constant combinator signals takes a few minutes even on maps with 100+ stops. I did change stop networks on my test world multiple times when experimenting with optimal train usage.

rdrunner
Burner Inserter
Burner Inserter
Posts: 6
Joined: Thu Sep 13, 2018 9:14 am
Contact:

Re: Request: Default encoded network ID

Post by rdrunner »

the FFFFFF bitmask will prevent me from creating my first subnet without updating all other stations first, since all stations will be a member by default. If given the option I can move them all to ID=1 for example and thus have a new default network. The default is already different from the "expected" value for a missing signal (Which would be 0) so there must be a special handling for a missing signal in the code already ;)

I wont have the blueprints for all 100 stations ready in my book, since many stations would have custom settings for me.

User avatar
Optera
Smart Inserter
Smart Inserter
Posts: 2915
Joined: Sat Jun 11, 2016 6:41 am
Contact:

Re: Request: Default encoded network ID

Post by Optera »

rdrunner wrote:
Thu Oct 18, 2018 8:42 pm
The default is already different from the "expected" value for a missing signal (Which would be 0) so there must be a special handling for a missing signal in the code already ;)
There is no need for special treatment. The beauty of two's complement makes decimal -1 set all bits regardless of integer length.

I'm not making this configurable since finding configuration errors from train size and network id mismatch is already hard.
Allowing network id default to anything except any would make it next to impossible without combing through debug log.

Post Reply

Return to “Logistic Train Network”