TL;DR
Trains should have a "Group ID" if they're within a group in the train system. Train stops should be able to report this to the circuit network.What?
loving 2.0 trains, loving 2.0 circuits.IN SHORT:
- 2.0 added train groups, super cool!
- in sequential order of being added to the group, trains should have some group ID associated to them similar to the train ID field that already exists.
- train stops should be able to report the group ID to the circuit network to some variable; say G.
- we all get a cool new feature that enables cool circuit X interrupt stuff
)Why?
here's some boring optional text if you'd like as to why I'm specifically thinking about this:in my current save, i've got a generic train interrupt system working that goes off of train ID to ensure "atomic access" to the resource request signals; so only one train serves a signal every cycle (2 ticks)
how i've implemented that is a clock that goes through the range of train IDs. however, not all trains are apart of this system, and so the range in which i'm polling has a large number of "dead addresses" that don't reflect the IDs of trains in this system.
if i were to have a group ID i could go off of instead, then this concept would be a perfect fit, as I can then direcly poll each train in a group and have each address represent something. super cool!
thanks for reading
- ramar