Dungeon Master Forum

I wasn't really expecting a bug, so, I'm sorry I don't have very detailed information, but, basically, I was running around SS, about to fireball a Giggler, and, as soon as I pressed the spell symbols to let the fireball loose, I get kicked back to windows with the crash message. Here's the diagnostics:

Error:
an access violation exception.

Stack Dump:
RTC.MakeSoundXYZ();
RTC.DamageMonster(int 566, int 850, char 34, char 7, char 2, int 5);
RTC.DamageTile(char 34, char 7, char 2, int 850, int 5);
RTC.SpellHitSomething(pointer 0x045D0304, int 19997, int 566, char 34, char 7, char 2);
RTC.ItemHitSomething(int 19997, int 566, char 34, char 7, char 2);
RTC.AddItemToTileCheckHitSomethingMonster(int 19997, int 2272, int 566, int 1681, char 34, char 7, char 2);
RTC.AddItemToTileCheckHitSomething(int 19997, int 2272, int 566, int 1681, char 34, char 7, char 2);
RTC.AddItemToTileCheck(int 19997, int 2272, char 34, char 7, char 2);
RTC.AddItemToTile(int 19997, char 34, char 7, char 2, char 2);
RTC.UpdateItemStdSpell(int 19997, int 2272, char 35, char 7, char 2, pointer 0x00000000);
RTC.UpdateItem(int 19997, char 35, char 7, char 2, pointer 0x00000000);
RTC.UpdateDungeon();
RTC.ProgStateInDungeon();
RTC.DoFrame(int 50);
RTC.WinMain();

I think this might be the same bug you had twice from me too, so having got it a third time trying to hit a muncher (two squares away, fireballed started to sail across then crash city) thought I'd post it here instead

RTC (V0.37) Diagnostic file - Wed Apr 19 19:27:30 2006

Error:
an integer divide by zero exception.

Stack Dump:
utilMemory.utilFreeCheckBlock(pointer 0x00000000);
utilMemory.utilFree(pointer 0x04604854);
RTCModule.DestroyItemCloud(pointer 0x03B26FD4);
RTCModule.DestroyItem(int 19941);
RTC.UpdateItemCloud(int 19941, int 1669, char 27, char 10, char 3);
RTC.UpdateItem(int 19941, char 27, char 10, char 3, pointer 0x00000000);
RTC.UpdateDungeon();
RTC.ProgStateInDungeon();
RTC.DoFrame(int 50);
RTC.DoFrame(int 5);
RTC.WinMain();

These are actually two completely different bugs in totally separate areas of the code. Both are now fixed though for V0.38

But...they both happened under RTC right? So at least that's somethign they have in common, right? : )