Page 1 of 1

[1.0] Amusingly catastrophically bad luck bug!

Posted: Sat Jan 12, 2013 9:12 am
by KiTA
Ok, so this character uh, well, is lost. He's not dead, he's not lost he's just... not there?

http://te4.org/characters/160/tome/ea5a ... b949db80bd

To be succinct:

Apparently, dying in the Fearscape to a Summoned Monster (Shade of Player) while also gaining a level from killing said Summoned Monster with a ranged attack while unlocking an achievement for gaining said level while unlocking a class for killing said monster (Doomed) all at the exact same time causes T-Engine to throw up it's arms and say "that's it, I'm done," causing the game to catastrophically fail, corrupting the save file.

(Frankly, I'm surprised such an obvious bug made it through beta testing! ;) :P :mrgreen: )

I had not unlocked Doomed as of yet, I was fighting the boss entirely too early with it going very poorly. So in my desperation I cast Fearscape, hoping to gain an advantage before he killed me.

While in the Fearscape he summoned my Shade, so I turned and unloaded on the shade. My Shade was actually dying very fast. My last shot fired off, just as I apparently died to the boss, kicking me out of the Fearscape. (Edit: There is a small chance that I just ended up getting punted out of the Fearscape at this time naturally.)

My last shot apparently killed the Shade.

Which Unlocked the Doomed class.

Which conflicted with me dying and being sent to the Afterlife.

Which conflicted even more with me gaining a level -- which healed me to full. While dead.

Which was level 30, which should have popped up an achievement.

The entire screen went blank, I was not allowed to save and exit (the game ignored that menu option) but I could continue to talk in game. I was able to select Save Game, but it froze at 89%. I could see both the "you're in the afterlife" icon as well as my current buffs, although my spell timers were all reset to their max -- i.e., the game thought I was dead.

Upon forcing the game to close and reopening it, the game now does not load that character's save file past 89%, instead launching me back to the main menu.

I have the save game uploaded here:
http://dl.dropbox.com/u/63119417/save%20-%20Copy.rar

Re: Dying in the Fearscape to a Shade while gaining a level.

Posted: Sat Jan 12, 2013 9:23 am
by KiTA
Oh, and for good measure, that level I gained? Level 30, which is an achievement (so that's another popup at the same time)...

Re: Dying in the Fearscape to a Shade while gaining a level.

Posted: Sun Jan 13, 2013 3:34 am
by KiTA
So this is the error I got. Well, got two in a row:

1:

error = "Lua Error: /engine/utils.lua:1668: attempt to index field 'level' (a nil value)\
At [C]:-1 __index\
At /engine/utils.lua:1668 circle_grids\
At /engine/utils.lua:1857 findFreeGrid\
At /data/talents/corruptions/shadowflame.lua:266 \
At /engine/Game.lua:239 onTickEndExecute\
At /engine/Game.lua:230 tick\
At /engine/GameTurnBased.lua:44 tick\
At /mod/class/Game.lua:1041 "
seen = true
reported = true


2:

error = "Lua Error: /engine/interface/PlayerMouse.lua:39: attempt to index field 'level' (a nil value)\
At [C]:-1 __index\
At /engine/interface/PlayerMouse.lua:39 mouseMove\
At /mod/class/uiset/Minimalist.lua:1610 fct\
At /engine/Mouse.lua:52 "
seen = true
reported = false


I have a feeling I'm pretty much boned. Looking in the save folder there is no .teaz file for the crypt, and opening the save file with a hex editor, it appears to crap out at the very end -- a good clean save ends with "mod.class.Zone-0x0a05d1a8PK", the bad save ends with "mod.class.Object-0x292a3478PK". It looks like the game just died before it could finish writing the tail end of the save file, or the glitch caused it to not write a .teaz file for the crypt.

I did notice just now that the game DOES load, but immediately closes. The bar fills up 100%, I see the UI appear for a split second, then the game exits back to the main menu. At this point I am logged out of the online server but immediately reconnect.

Re: [1.0] Amusingly catastrophically bad luck bug!

Posted: Sun Jan 13, 2013 7:19 am
by KiTA
Also: I love how the constitution is a floating point number: 55.274729776574 That's not right, is it? haha

Re: [1.0] Amusingly catastrophically bad luck bug!

Posted: Fri Jan 18, 2013 3:35 am
by PeterW
KiTA wrote:Also: I love how the constitution is a floating point number: 55.274729776574 That's not right, is it? haha
Well, at least it's not the exponent.

:D

Pete

Re: [1.0] Amusingly catastrophically bad luck bug!

Posted: Sat Jan 19, 2013 8:34 pm
by azrael
...wow.

Re: [1.0] Amusingly catastrophically bad luck bug!

Posted: Sun Jan 20, 2013 2:40 am
by LNQ
The constitution is a floating point because of Rotting Disease lowering it by 20.725270223426 (rounded to 21 in the desc).