42f4cbdc9c
found this bug with blueprint-generated blueprints. if both a channel and the resulting ramp are explicitly marked in the blueprint (like the blueprint plugin does), the channel is processed first, pre-creating the ramp in the tile designated for a ramp. Then, when the ramp designation is processed, the ramp is already there, which is an invalid tile to make a ramp on, so the designation is skipped (and therefore not cleared). this change clears the designation for both the ramp tile and the channel tile when either is processed. this opens another edge case where the designation under a channel is a regular 'd' mine, which will now get ignored and leave a ramp insead of a flat floor. but I'll address that in the next commit. |
||
|---|---|---|
| .github | ||
| CMake | ||
| build | ||
| ci | ||
| data | ||
| depends | ||
| dfhack-config | ||
| docs | ||
| library | ||
| package | ||
| plugins | ||
| scripts@c4568af3dc | ||
| test | ||
| travis | ||
| .gitignore | ||
| .gitmodules | ||
| .ycm_extra_conf.py | ||
| CMakeLists.txt | ||
| CMakeSettings.json | ||
| LICENSE.rst | ||
| README.html | ||
| README.md | ||
| conf.py | ||
| dfhack.init-example | ||
| index.rst | ||
| onLoad.init-example | ||
README.md
DFHack Readme
DFHack is a Dwarf Fortress memory access library, distributed with scripts and plugins implementing a wide variety of useful functions and tools.
The full documentation is available online here,
from the README.html page in the DFHack distribution, or as raw text in the ./docs folder.
If you're an end-user, modder, or interested in contributing to DFHack -
go read those docs.
If that's unclear or you need more help, try the Bay12 forums thread or the #dfhack IRC channel on freenode.