Preston Crow wrote: > Playing on Metalforge with the recent update, there are frequent > crashes. It appears to happen when someone applies an exit in a random > map (to go to the next level). This only happens perhaps 5% of the > time. I've fixed the bugs as they've shown up on metalforge. So far, most of them have been related to the event code (the one that wasn't was related to the dragon player code assuming that there would always be appropriate dragon force objects. That shoudl be the case, but always better to not crash if possible). The event bugs would most often show up when a map is being loaded or saved, as that is when objects with events tied to them would be created. For the most part, it was the same bug causing multiple crashes. Given metalforge hasn't crashed today, I'm thinking those bugs are fixed. For those that may have 'issues' with metalforge being the latest, and thus, not necessarily reliable code, I'd point out that the event stuff was checked in in June, and apparantly no one else found the bugs (granted, metalforge runs with debug malloc which will find uninitialized value errors much more quickly). But the reason metalforge tends to run latest is simply to find the bugs. _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel