tentative fix for the crash today: a summoned monster has been removed twice, casuign the crash. the reason _probably_ was that follow_owner couldn't follow the owener but left the monster removed. The monster later died, was removed, and the server crashed. some callers of follow_owner checked for this and removed the monster in _SOME_ cases, leading to a certain crash if the monster dies for whatever reason (in our case, poison). fix: changed follow_owner to free the object in every case. simplifies code and gets rid of weird undocumented conditions that would lead to a sure crash anyways.
Another case of calling on_same_map but then ignoring its results. Caused pets to run away from you on map boundaries. Likely, other callers of on_same_map still suffer from that same bug. If only whoever changes crossfire functions semantically would fix up the callers of that functions. But thats too much to ask. Grrr.
fix another of those pesty crashing bugs. The incompetent crossfire developer (I sense redundancy here) who did the SIZEOFFREE* change(s) left another bomb for us to fix. likely, that same incompetent developer left more SIZEOFFREE bugs where 'directions' are being confused with the indices returned by find_free_spot and so on.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.