Wed May 18, 2005 6:51 am by AuGuR
(Not that this reply really belongs in this particular thread, but...)
I think the crash while launching bug more refers to what happens when a pilot currently landed on a station, the station being destroyed while docked, and then attempting to launch from a station that no longer exists in game, no? Or even if a player docked at the now destroyed station before leaving the server and has come back to play, but now docked on the destroyed station.
What would have to happen to avoid this is to have the pilot docked on the station that was just destroyed to be moved to a nearby station by an "emergency rescue ship" or the like. To help do this in a very rough way would be to have a global message saying that "So-and-so station was destroyed, please contact an admin for transfer to a safe haven.", both when docked or just logging onto the server. The pilot then sends a msg to an admin and the admin basically kick/moves the player to another station or system. Something like that at least. Otherwise the crash would still happen.
Another option, tho I don't know how it could be done is to have a secondary base model with docking harpoints, but with no .sur file (so it can't be damaged) and somehow force freelancer to replace the now destroyed station. This condition would also have to be temporary as I believe that systems in multiplayer are reset every-so-often or when the system itself is clear of all players.
Either way, some serious scripting would have to be done. Something to think about over morning coffee, eh?
Aug
When all else fails...
RUN AUG RUN!!!
Edited by - AuGuR on 5/18/2005 7:52:11 AM