I was wondering if the reason why server freezes keep happening is because some people haven't updated their .WZ files yet. I don't really know anything about running a server, but I thought I'd throw this out there.
It shouldn't if the server is coded well. I think a poorly coded server could easily run into problems with out of date WZ files; any incorrect client input to the server can be very dangerous if not handled correctly. In saying that, I have doubts that this is the problem here. If it was possible to slow down an OdinMS based server in that way, then it'd be abused greatly to bring servers down and everybody would know about it.
The server isn't coded very well at all, and we don't think it is a hard drive issue this time, it's likely that mysql is the bottleneck. However with that said, we are working on getting everything fixed (not just the lag), but unfortunately it's gonna take a few months.
Good luck! Thanks for the honesty, and you guy are doing an awesome job keeping such a large server up as much as it is, given that you aren't even being paid to do it
It's not like Matt, John and other (former) developers are to blame; as this is a low-version server, it's bound to have more bugs than newer servers.
I thought it would have been the opposite, for a couple of reasons. a) people have had longer to perfect the features of the earlier versions (remember that the server code, unlike the client code, was written from scratch by the authors of OdinMS because there was of course no access to Nexon's server code). And b) The more features you have, generally the more complex the code becomes to maintain, particularly in poorly written code. The newer versions probably suffer from both these points.
At the same time, as you add more features, if you aren't careful, you could be building memory leaks or bad code on top of poor code. Kind of like creating a giant tower on top one small block. It may hold for awhile but may eventually topple over. This code run on the server has been heavily modified by multiple developers, and some who thought their changes would make the game run "faster" or "more efficiently." I have no numbers to support it, but it's possible that code may have exacerbated, rather than abated the issue. As Matt said, we continue to work on finding solutions to the issue at hand, but we are finding ourselves quite confused as we have ruled out, or thought we have been able to rule out, many potential causes. Thank you for remaining loyal to Royals and realizing there's a reason we have the largest preBB community around
