Closed rpdelaney closed 2 years ago
Bocian's Book of Rails 1.5 MB
holy
The issue is that I've forgotten that you can put upgrade planners and deconstruction planners in blueprint books, which causes problems. I forgot about these, so I'll add two new classes for them DeconstructionPlanner
and UpgradePlanner
, but the quickest patch until 1.0.2
would be to simply remove these items from the blueprint book and reimport it, providing that you don't actually need those constructs in the blueprint book. I assume you're autogenerating a rail grid?
I assume you're autogenerating a rail grid?
He got everything aligned manually already because he's some kind of lunatic hero. I want to use his rails but purge the lamps (I hate lamps) and big poles (I have my own tiling blueprint for power, and it lines up with his rails but not the poles already there). Obviously with a book this big, nobody (least of all me) is gonna do that post-production manually. :)
Alright, UpgradePlanner
and DeconstructionPlanner
are now implemented. After trying to load that blueprint design again however, some of the signal id's on some of the rail signals appear malformed:
{
"entity_number": 18,
"name": "rail-signal",
"position": {
"x": 336.5,
"y": 26.5
},
"direction": 6,
"control_behavior": {
"circuit_close_signal": false,
"circuit_read_signal": true,
"red_output_signal": {
"type": "virtual",
"name": "signal-1"
},
"orange_output_signal": {
"type": "virtual",
"name": "signal-1"
},
"green_output_signal": {
"type": "item" # <-------- what
}
},
...
}
Of course, this imports into Factorio no problem! It lives as an empty signal, and persists if you place the blueprint down and create a new blueprint from the placed entities, implying this intentional. Just documenting another very strange edge case here before I forget about it, though it is confusing how this ended up like this in the first place.
Unfortunately, the blueprint book does contain modded entities, so even after 1.0.2
goes live importing it will still be difficult unless you install the associated mods. I'll add this issue to the 2.0 milestone to track it there as well.
the blueprint book does contain modded entities
Wait, what? Can you tell me which ones? (I recognize this is a fucking tome of a blueprint, so please don't spend much time on that.) It may be a bug that the author will want to fix.
...
raise InvalidTileError("'{}'".format(value))
draftsman.error.InvalidTileError: 'dect-concrete-grid'
Which I assume is a decorative grid tile, and if I ignore unknown tiles:
...
raise InvalidEntityError("'{}'".format(name))
draftsman.error.InvalidEntityError: 'logistic-train-stop-output'
LTN train stops. Of course, these are just the first tiles/entities that appear before Draftsman errors out; there may be a few more tiles/entities from the same mods or different ones elsewhere in the blueprint.
Oh yeah. I forgot about LTN. That's for sure not a bug in the book. I think that closes this, and the issue with LTN stops is better captured in #42 -- of course, you should feel completely feel free to re-open if you disagree.
When importing Bocian's Book of Rails using this code:
Stack trace
```python Traceback (most recent call last): File "/home/ryan/src/me/factorio-rails-cleaner/foo.py", line 18, in