Dungeon Dilettante
Posts: 2
Joined: Friday, 22nd November 2013, 16:23
Odd vault error / Sprint WIP
I'm working on a Sprint map, and while it's coming along fairly well, I just started getting a strange error concerning one of its subvaults, "the_charnel":
(these error messages repeat themselves three times)
What's very strange is that this error only appears around 20% of the time; most games the error does not appear at all.
Stranger still, the error seems harmless. Not only does the_charnel get placed in (9, 27) to (45, 43) just fine, but the callback.sealing_stone function triggers exactly as expected. There doesn't seem to be any different between the games when these errors appear and the games when they don't, both play exactly the same.
The .des file is at http://bpaste.net/show/152139/
I'd also appreciate any comments on the map in question. It's slower-paced than most sprints, and probably easier too--I'd appreciate comments on how to adjust the difficulty curve. I'm worried that EEs, formicids, and merfolk will have an unfair advantage, but I'm not sure. It's not complete, so there's just a bunch of empty space near the bottom.
One feature I was unsure about was including a Pikel band. On the one hand, freed slaves can upset the balance a little bit, taking out an early "boss" or opening doors before you're ready. On the other hand, it's kind of a fun question whether to try to free them to soften the upcoming enemies a bit, or kill them so that they don't ruin your stealthy approach. And it's nice flavor, too. I'm a bit split.
Lua error: ...crawl/crawl-ref/source/dat/dlua/fnwrap.lua:30: Could
not resolve 'callback.sealing_stone' to a function x100
Lua error:
crawl/crawl-ref/source/dat/des/sprint/kobold_mines.des:20:
Could not fit 'the_charnel' in (9,27) to (45, 43).
(these error messages repeat themselves three times)
What's very strange is that this error only appears around 20% of the time; most games the error does not appear at all.
Stranger still, the error seems harmless. Not only does the_charnel get placed in (9, 27) to (45, 43) just fine, but the callback.sealing_stone function triggers exactly as expected. There doesn't seem to be any different between the games when these errors appear and the games when they don't, both play exactly the same.
The .des file is at http://bpaste.net/show/152139/
I'd also appreciate any comments on the map in question. It's slower-paced than most sprints, and probably easier too--I'd appreciate comments on how to adjust the difficulty curve. I'm worried that EEs, formicids, and merfolk will have an unfair advantage, but I'm not sure. It's not complete, so there's just a bunch of empty space near the bottom.
One feature I was unsure about was including a Pikel band. On the one hand, freed slaves can upset the balance a little bit, taking out an early "boss" or opening doors before you're ready. On the other hand, it's kind of a fun question whether to try to free them to soften the upcoming enemies a bit, or kill them so that they don't ruin your stealthy approach. And it's nice flavor, too. I'm a bit split.