Originally Posted by jaliborc
I don't understand nothing about server querying, so this may seem stupid, but I though that the client already queried the server for completed quests, to know if the quest givers can offer us such quests.
|
More likely is that the server only sends the client information about nearby quests when necessary (and applicable).
This makes a LOT more sense when you also factor in pre-reqs, level ranges, class-only quests, etc.
Just have the server do the calculation (since it has all the data) and return what the client needs to know, rather than send all the data to the client and have it do the calculations.
Originally Posted by jaliborc
EDIT: But I think that the event is also a good idea (added it to the list). And the gossip functions wouldn't cause any overload, am I right?
|
I wouldn't consider this to be much overload. In addition to simply passing the gossip text and type (note how it's !/? mark?), the server also sends the quest id, and that's enough to generate a link from.