View Issue Details

IDProjectCategoryView StatusLast Update
0004483Dwarf FortressDwarf Mode -- Jobs, Building Construction and Destructionpublic2011-04-11 14:25
ReporterDekon Assigned Touser6 
PrioritynormalSeverityminorReproducibilityrandom
Status resolvedResolutionno change required 
Product Version0.31.25 
Summary0004483: Non-Existent creature occupying space - cannot build
DescriptionWas building a wall, and found a single spot where a 'creature' is 'occupying [the] site'. Using k, there is no creature. It's an open spot. Tried restarting the game, cancelled the building and rebuilt. Can't find any means to not have anything in that slot.
Steps To ReproduceNo Idea
Additional InformationWill submit a save once I know the bug number. The exact location for this problem is placed on a note, so there shouldn't be any ambiguity. Still, it's on the surface level z-level, and the last remaining wall to be built there.
TagsNo tags attached.

Activities

Dekon

2011-04-09 09:12

reporter   ~0017235

Save uploaded:

http://dffd.wimbli.com/file.php?id=4168

user6

2011-04-09 12:20

  ~0017253

Were there any creatures that were caught in a cage trap at that location, or died in a cage at that location?

Dekon

2011-04-09 18:09

reporter   ~0017260

Nope. I haven't used cage traps at all. The closest thing was that that area used to be part of a pen, before I moved all the animals to the larger separate pens they're quite obviously in now.

ellindsey

2011-04-11 12:45

reporter   ~0017301

Did you use Runesmith or a similar memory hacking tool to kill something? I find that if you do, the tiles where the creature was standing never gets marked as unoccupied and nothing can ever be built there.

Dekon

2011-04-11 12:48

reporter   ~0017302

Once, but it wasn't on that tile. It was many z levels down.

user6

2011-04-11 14:25

  ~0017305

Using memory hacking tools is playing with fire, and I doubt whether there's any way to tell whether the bug in your save was induced by DF itself or a badly programmed utility. Please reopen this report if you can reproduce the problem in a save that is unblemished by memory hacking.

Issue History

Date Modified Username Field Change
2011-04-09 09:08 Dekon New Issue
2011-04-09 09:12 Dekon Note Added: 0017235
2011-04-09 12:20 user6 Note Added: 0017253
2011-04-09 12:20 user6 Tag Attached: AWAITING UPDATE
2011-04-09 18:09 Dekon Note Added: 0017260
2011-04-11 12:45 ellindsey Note Added: 0017301
2011-04-11 12:48 Dekon Note Added: 0017302
2011-04-11 14:25 user6 Note Added: 0017305
2011-04-11 14:25 user6 Status new => resolved
2011-04-11 14:25 user6 Resolution open => no change required
2011-04-11 14:25 user6 Assigned To => user6
2011-04-11 14:25 user6 Tag Detached: AWAITING UPDATE