David Seikel wrote: >> tend to guess that it is the loading/saving of maps which is going to be >> the major performance hit on the server site - and communicating what is >> on the map frm the server to client and back again. > > > Since the WG is just another client, the server only needs to send the > usual info to it, no performance hit there. Sending info back again would > bog down the server, if it was a large lump of info. With the current > weather resolution, it won't be a large lump. I am trying to cut it down > to only the info needed for the map the WG is currently on. > <snip> Ok. You explanation makes sense. As said, it sort of depended on what your goal of the WG was. _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel