And so says Mark Wedel on 23/06/05 12:58...
> Real bug here was the commit of the settings files that changed the
> value of fastclock. Unfortunately, changing the settings file back
> doesn't really help things out because by default, the settings file is
> not installed if one already exists - thus, all the people will broken
> settings file will continue to have it.
May I respectfully suggest a hard throttle, so that no matter what else,
the server just won't talk to the metaserver more than, oh, once per
minute or so? Then even people with fastclock on will have this solved.
best,
Lalo Martins
--
So many of our dreams at first seem impossible,
then they seem improbable, and then, when we
summon the will, they soon become inevitable.
--
http://www.exoweb.net/ mailto:[EMAIL PROTECTED]
GNU: never give up freedom http://www.gnu.org/
_______________________________________________
crossfire mailing list
[email protected]
http://mailman.metalforge.org/mailman/listinfo/crossfire
