Quote:
Originally posted by Com013
But still...the NPC Server would have to keep record of timeouts in
2000 levels or so.
And I'd have to add this NPC to all of this levels.
|
Okay, here: Every time a fish dies, it sends a trigger to the server. The server then replaces it, possibly with a delay for realism. Then the only problem is the actual placing of the fish in the first place, and easy ways could be concocted to handle that. For example, something in the CNPC could trigger the server every time it enters a suitable level. If the server agrees that the level is fine for fish then it places some there. Then the workload is spread according to the activities of the players, and perhaps levels that don't get many visitors could empty out their fish after a while to reduce server load.
Question, though: What do these fish do? If you're worried about timeouts then how are you going to make them do anything other than float on the water's surface and do nothing?
Quote:
Originally posted by Tyhm
Terrible how all the NPCServ people look down on Classic people for not having a year or so experience
|
Not at all, my suggestion had nothing to do with exclusively-serverside stuff. It was just maths, y'know?