Possible to delete monsters by swapping with the construct generators
issueid=5031 09-17-2017 11:47 PM
Ancient Member
Number of reported issues by Grond: 971
Possible to delete monsters by swapping with the construct generators

The permanent stone statues and golems in the alcoves of the dwarven fortress can be swapped with. If you swap a monster back into the alcove, it will be deleted, with the following message:
Code:
Stacking monsters (a stone statue/281 {0, 16640} [50, 9] with a stone statue/281 [50, 8]) at (50, 8) is not allowed (L: 11, 5; LI: 115).
***I'm trying to fix this by simply deleting the stone statue.
Issue Details
Issue Number 5031
Project ADOM (Ancient Domains Of Mystery)
Category All without NotEye
Status Fixed
Priority 5 - Medium
Affected Version ADOM 2.3.0 (r73)
Fixed Version ADOM 2.3.2
Milestone (none)
Users able to reproduce bug 0
Users unable to reproduce bug 0
Assigned Users (none)
Tags (none)




09-18-2017 08:01 AM
The Creator
Fixed.

09-18-2017 05:56 PM
Ancient Member
This still seems to be broken in 2.3.1.

09-19-2017 07:59 AM
The Creator
Can you please provide a test case if possible? The code IMHO clearly states that no statues/golems will be generated if a being already is standing at the target position (which would cause the deletion). Maybe I'm doing it wrong...

09-19-2017 02:46 PM
Ancient Member
On the file attached you can swap with the monster to the north in order to get the error. I'm guessing this is just another case of a fix not getting pushed to 2.3.1.

09-19-2017 03:44 PM
The Creator
Amazing find. The bug still existed. But the trick was to stand in the alcove. Which caused ADOM to erroneously create another statue "beneath" the PC. And then led to the problem. Because the replenishment code had forgotten to check if the PC was standing on that position. Which is a special case (always) in ADOM as the PC is not represented like other monsters.

Thanks so much for the save file!

09-19-2017 03:44 PM
The Creator
Fixed.

09-21-2017 03:28 PM
Ancient Member
Still happens in 2.3.2. Attached another save.

09-22-2017 09:35 AM
The Creator
Quote Originally Posted by Grond
Still happens in 2.3.2. Attached another save.
And I understand correctly: This character also was created in 2.3.2? Otherwise it might carry over the error condition from 2.3.1.

09-22-2017 02:33 PM
Ancient Member
Quote Originally Posted by adom-admin
And I understand correctly: This character also was created in 2.3.2? Otherwise it might carry over the error condition from 2.3.1.
Yes, the "Again" save was created in 2.3.2.

+ Reply