I killed a monster, but he was still visible and I was able to hit him once again
issueid=282 07-18-2011 09:19 PM
Junior Member
Number of reported issues by Orion: 16
I killed a monster, but he was still visible and I was able to hit him once again

I got the message that I killed the monster, but he was still visible. And I was able to hit him once again... I got the message "you hit the monster" (I do not remember the name) and after that the monster dissapears from the screen.
Issue Details
Issue Number 282
Project ADOM II (formerly known as JADE)
Category Unknown
Status Fixed
Priority Unknown
Affected Version JADE 0.1.3
Fixed Version JADE 0.1.4
Users able to reproduce bug 3
Users unable to reproduce bug 0
Assigned Users (none)
Tags (none)




07-19-2011 01:55 AM
Junior Member
I could reproduce that just now. Not only is the orc warrior I'm fighting dying multiple times like the black knight in Monty Python, but he's also giving away weapon skill marks and EXP for every kill.

07-30-2011 11:08 AM
Senior Member
I got the same for a goblin scavenger just now, which did not come in from another level (so this is not a duplicate of the stairs-luring bug). Maybe it's because the enemy needs a turn to recognize that it's dead and its speed was so low that we got another turn before them?

08-14-2011 11:40 AM
The Creator
Fixed for JADE 0.1.3. Please send your real name to creator(at)ancientdomainsofmystery.com for it to be included in the credits.

08-15-2011 09:52 AM
Senior Member
I can still reproduce both bugs (the one with stairs and the one without) in JADE 0.1.3

08-15-2011 04:59 PM
The Creator
That's really amazing. I have killed thousands of monsters by now and it didn't happen once. Can I see the log file from your user home/.jade/log directory? Is there anything special in it?

08-15-2011 06:21 PM
Ancient Member
I also just was able to reproduce the stair bug multiple times.

08-15-2011 06:55 PM
Joe Joe is offline
Senior Member
I also have encountered this feature several times.

08-15-2011 07:57 PM
Senior Member
Well I cleared my log and reproduced the bug again. I don't think it gives any information though, for I lured a rat and killed it more than 20 times. Here it is:

2011-08-15 21:44:44,906 ERROR Thread-13 de.adom.jade.utils.ErrorUtils - Handling error.
java.io.EOFException: Unexpected end of ZLIB input stream
at java.util.zip.InflaterInputStream.fill(Unknown Source)
at java.util.zip.InflaterInputStream.read(Unknown Source)
at java.util.zip.GZIPInputStream.read(Unknown Source)
at java.util.zip.CheckedInputStream.read(Unknown Source)
at java.io.ObjectInputStream$PeekInputStream.read(Unknown Source)
at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readInt(Unknown Source)
at java.io.ObjectInputStream.readHandle(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readArray(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readArray(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readArray(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at java.util.HashMap.readObject(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at de.adom.jade.kernel.storage.ObjectSerializationGamePersistenceHandler.loadImpl(SourceFile:123)
at de.adom.jade.kernel.storage.AbstractFileBasedGamePersistenceHandler.load(SourceFile:115)
at de.adom.jade.kernel.game.startup.loader.steps.RestoreGameStep.execute(SourceFile:49)
at de.adom.jade.kernel.game.startup.loader.StartupSequence.execute(SourceFile:102)
at de.adom.jade.kernel.game.startup.loader.JadeLoader$1.runImpl(SourceFile:71)
at de.adom.jade.utils.VerboseRunnable.run(SourceFile:35)
at java.lang.Thread.run(Unknown Source)

It's a nice bug, killed about 400 ogres with my last char :D

08-15-2011 09:15 PM
Junior Member
I'm able to reproduce the stair bug - but less consistently than in 0.1.2.

08-15-2011 09:38 PM
Junior Member
Lured a hobgoblin upstairs in 0.1.3 and killed him few hunderd times.

08-16-2011 12:43 AM
Senior Member
I need to re-evaluate my morals jade 1.3 just came out and I'm already stair scumming... and things were going pretty good to until hobgoblin chieftain got a crit on me and took me from 87 hp to -21... grrr

This petition for a change to Confirmed was accepted
08-18-2011 05:50 AM
Junior Member
Ok, after some testing, I think Moeba is right when he said "Maybe it's because the enemy needs a turn to recognize that it's dead and its speed was so low that we got another turn before them?"

Not only does this happen sometimes, although infrequently, with normal speeds of slightly over 100, but as your speed increases, the chance of this happening increases as well. With over 300 speed, you can usually kill a monster three times before it is removed from the map.

Similarly, the problem with bringing them upstairs appears to be caused by the same. Supposed you spend 1000 turns on level 1 of the dungeon. Areas seem to keep track of their elapsed time, and when you leave the level, time does not pass on other levels. So when you descend to level 2, it is generated at turn 1000; then you spend another 1000 turns on level 2 and end on the upstairs to level 1 with a monster next to you. You go upstairs, and the monster follows you... the next turn the monster is set to act is turn 2001; but the time on level 1 is still at turn 1000, so the monster won't get its turn for the next 1000 turns, so it will neither move nor be removed from the map if it dies. You can test this yourself rather easily, and it always happens that the monster doesn't move or is not removed after death for the same number of turns as you spend on the other level of the dungeon.

Turns of course is just a measure of time and depends on your speed.
 

08-18-2011 03:01 PM
Ancient Member
Telrunya, it's just as you say. I have checked and it works 100% of the time: if you meet a monster on level X+1 and go back with it to level X, then it stays frozen and repeatedly dying for the same time that you have spent in level X+1. It seems that the monsters have their internal clock referenced to their level's clock and they get confused when they enter a different level with a different time... monster jet lag! :)

08-18-2011 08:26 PM
The Creator
Found more problems related to this. Fixed for JADE 0.1.4.

Please send your real name to creator(at)ancientdomainsofmystery.com for it to be included in the credits. (If you were aleady asked to do so you can ignore this message. Please include a reference to the bug or RFE you are credited for.)

08-18-2011 08:29 PM
The Creator
Fixed once more. I can't reproduce the problem anymore.

+ Reply