Problem with Very Fatal Errors

[Tsukiyomaru0]

Remember when I mentioned them previously? Well, they have the awful habit of haunting me on Megaman 8-Bit Deathmatch and used to haunt me on few mods that existed for Skulltag. However, they show rather pointless data and provides little to no possibility of tracking the error itself. I mean, look at these:
http://www.mediafire.com/?jt1d9hb1nmgglao
http://www.mediafire.com/?lns2qudm6cf734r

The game goes to Very Fatal Error window, asks me to save this or scrap, and that's it! If you are on a situation where you can't return right away, you are doomed.

What will be done about this kind of problem?

[Torr Samaho]

I've already fixed numerous of these problems. Check if it's still happening in the latest Zandronum beta build. If it does, create a ticket at the tracker, describe what was happening before the crash and attach the crash log. Then I can try to find out what's going on.

[Tsukiyomaru0]

I've already fixed numerous of these problems. Check if it's still happening in the latest Zandronum beta build. If it does, create a ticket at the tracker, describe what was happening before the crash and attach the crash log. Then I can try to find out what's going on.

Thing is: It happens only in MM8DM now, and they have yet to migrate to Zandronum (you know how things are over there). But, my main worry is the lack of a console log/dump, or even ACS log/dump to understand what and where it is going wrong. I have suspicions that it is Null Pointer Exception.

And, so far, haven't played much on Zandronum yet. But I look forward to in future (After first stable build, as it will be when the servers I like will update their sourceport).

[ZzZombo]

Just curious when the "Send report" button will function.

[Torr Samaho]

Just curious when the "Send report" button will function.

Right now I have no plans to implement this.