diafero wrote:Given that you control the engine, I'd suggest to equip plNetLinkingMgr with such a database and make it reject and/or correct linking requests with the wrong linking rules (and display name and spawn point title, though those only affect the UI, not database consistency). That would even work for linking responders embedded in PRP files.
I would forward a subset of the linking rules to the server and let it perform load balancing (and instancing decisions...). I think there is some value in the way Guild Wars 2 handles instancing. Of course, this would probably need drastic changes such as removing the concept of age vaults... So not now
Thanks for the links to your scripts. OU is way behind the times on basic Uru server administration knowledge like how a data server works, so I've been working on a MOUL-centric data server script, which, of course, has its own set of fun to handle... It's always interesting to compare approaches.
Chacal wrote:Maybe it's due to lots of positive money coming to Cyan lately.
More due to folks collectively holding the feet of the OpenURU organization to the fire recently. They (OpenURU) have been the roadblock, not Cyan.
Charura wrote:Specifically for Moul(a) or just being generous? Maybe you have some insider info?
Cyan did just have a successful crowd funding initiative for a new game that raised over one million smackers...