The 1.30 update is on German worlds. It’s been quite some work to get it there. First we had an inefficient SQL-query that blocked the update process on the first world we updated – it took about 6 hours until the server was back online. We cancelled the script in between and had a database that was in a pretty wacky state. We still managed to drag it over to 1.30 so it’s running fine now. The only problems we currently have are the two biggest worlds. The chat is not working properly when the server is on heavy load and that is pretty annoying. I worked quite a lot this weekend to find solutions, but it’s anything but simple. The problem is too technical to be explained easily, but altogether, it’s a architectural misconception footing on my first concepts when laying out the software. We try to figure out ways to counter this, but in general, it’s pretty complicated to get out of that now. For smaller worlds (<2k online users) it’s not really a problem, but above the 2k limit, the air gets thin. So I am working now on that – that’s why beta chat is wonky today.
12 Comments
Comments are closed.
i wish you verry much luck ;).
zet, just disable the chat and voila. how about permanent removal of the county chat? it’s usually abused and not very important part of the game… if that would help, remove that county chat for good, i don’t think anyone would object. 😉
anyway, for the time being, ppl can rely on forums and 3rd party chat if needed.
Agree with Joxer about the county chat. In all the world I play i see no one use it.
Hope to see the update in the other worlds soon.
Good luck with the problems.
@JoxerTM you lack imagination about players. There’s always at least always one who’ll object. It already steers up much trouble on german board that the chat is disabled – since chat and fortbattles are handled in the same application (unwise, but I didn’t know better), it affects each other.
Version 1.3 > chat.
Yes chat is important to quiet a few players (it makes the game lively) but pants/belt/new jobs ect are the things that people are really exited about.
I think most players will understand and be patient if told/warned ahead of time that this is something that is still being worked on,players aren’t as upset about things is they know what’s happening ahead of time.Maybe an announcement in the main forum would be good.
I’m aware someone will always object, but players in a roleplay game should not object like players in a farm-till-you-die games, but instead they should adapt. 😉
I seriously thought the fort chat, in fact the whole fort minigame, runs as a separate application. Although fort fighters usually use 3rd party chat “just to be sure”, battle orders are always given through the ingame chat, so in this case turning the chat off can cause some serious trouble.
I hope you’ll fix the issue as soon as possible. Keep up the good work!
Joxer just gave me an idea.
Binning the chat altogether isn’t such a bad idea.
Replace it with an optional integrated 3rd party type system.
I imagine all the server load or whatever is causing you the chat problems could be sorted this way.
isn’t the solution a better server that can handle more people?
@mennik , I am working on exactly that. Splitting these parts would still make sense. But the efforts are looking fine so far, though still not yet fully stable, it’s doing a quite good job now.
if your problem is that js keeps open conections to server try this: http://code.google.com/p/jsocket/, with fallback to old method 🙂
the problem is that the server can’t handle all the activity or that is what zet says “The only problems we currently have are the two biggest worlds.”
and the big worlds got more people 🙂 or that is what I make of it
@mennik too many active people == too many open connections 😛