I have a proposal to offer that allows blueprints to be versioned using a constant combinator in the blueprint.
This of course assumes that you have enough space in the blueprint for a combinator. It works well for the train blueprints I'm using and working with.
The idea is to set some values in the combinator. For this example blueprint the version is "v2.0". I set the combinator to output the following values:
- v - 1000
- 2 - 10
- 0 - 1
is significant and places viewed output into the correct order. The v part is probably totally unnecessary but it helps with the intention of the combinator in the blueprint.
I did do a search to see if someone else had ideas about this, but they all involved game development changes. This is badly needed by the way.
What I like about my approach best currently is that my blueprints tend to undergo continuous improvement and I do bump the version number when
I make changes. Once I have a few hundred of these T intersections around my base, it's hard to tell what version a particular one was. By checking the
combinator value on it - I know if it needs an upgrade or not. I'm not sure how the developers might deal with that in game, or if they would even attempt it.
I'm attaching an image of a T intersection. It's RHD. (Any suggestions on signal improvements would be much appreciated.) This is the best
I've been able to put together without making a buffered intersection. I'll also try to insert the blueprint string for it so you can all try out what I'm suggesting and see if it has any merit. This isn't so much a proposal I guess as more of a guideline for players who produce blueprints.
Thanks for your time!
