Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

created splitting darknut crashes

17 replies · 3,106 views · Started 27 July 2007

I created a splitting darknut with all of the exact same settings as the original except for a different graphic and on the 4th hit from the magic sword the player crashes.
The graphics I'm using are down around the 58000 area in tiles, although I don't think that should really make any difference.

I was playing with this some more this morning, I tried the original splitting darknut on a screen and it crashed too, so thinking maybe ALL splitters crashed, I tried a Vire Tribble, and it works just fine.

Here's an update to this bug in the 500.

The created Darknut will now split IF you use the default (50) for it to split into, however if you try to make it split into one you have created (179) then the player will crash to desktop when it splits.

Hmmm... there's no immediately discernible problem on my system. Any other developers...?

Then I'll triple check my numbers and play with it some more to see if I can figure out why it's crashing for me and not you.

EDIT;
Nope, nothing wrong with the way they are set up, it just crashes.

IT WORKED!!!
I put another "blue Helmasaur" on the screen with it, and it doesn't crash then.... go figure.
I'll go back and see what happens if I remove the extra enemy.

It may not be a problem with the darknut, but rather the enemy 179 you created. Although I have no idea why. It's just a while back on the 300's builds i'd input a bunch of "wrong" (i guess) numbers for some enemies and I saw alot of crashes from that.

There wasn't anything wrong with the enemy I created, it was exactly the same as the blue darknut except the graphic and the I.D. number.
The program has been doing that a lot, first something won't work, then it just starts working.
It seems that what made it start working was putting the other enemy on the screen, prior to that it kept crashing.

Never mind, it's crashing again.
I don't know what to say about this one, it works one day and crashes the next.

DarkDragon,
I sent you a link via PM to the quest that displays this problem and the ladder bug.
I'll find and move that post up too.

Frustratingly, I can't get your splitting darknut to crash, and examining the splitting code has proved unenlightening.
Is there anything specific you do while killing the Darknut that might provoke a crash?

Just slashing him with the magic sword, it crashes on the 4th hit, last time I tried, it froze my computer as well.

Tried this again in the 536.
This time I used the hammer.
1 hit on the Helmasaur it changes to a graphic which is not there, possibly would be a no shield graphic, hit two it splits into two (blue) Helmasaurs, and it doesn't crash!

I left the dmap and came back and fought him with the sword the second time and it didn't crash when he split.
This is something like what happened before, once it started working, after I put another blue on the screen and killed him, then it would work again and again, but until then it would crash.

I also can't understand why the no graphic thing with the hammer, that part I might have set up wrong, do splitters normally lose their shields or just split?

EDIT;
Ok this is really messed up now.
I think I see what _L_ did.
I think he made it so now you HAVE TO choose the "S" tile and if you don't it will NOT go to the default spaces down from it, whatever those were, something like 120 tiles below.
So now all my splitters are "broken" in effect, but I can go and set them and fix them, but will this effect other quests?
I say all my splitters.... I'm only talking about all Darknuts, I haven't tested any others.

ALSO the SHIELDLESS aren't displaying their animation right once they are split, they are only using the first 4 tiles, so they have their back to you always, no matter where they are going.

Bright side?
Yep, it isn't crashing anymore. 😉

The darknut code was untouched between this and the last build, so if the crash bug isn't showing up now it's likely to again in the future. It's got me baffled.