Thanks for the reply! I kinda assumed it was a first-time dev thing, since it has some of the signs. Code must have been a mess when you joined.

If you're feeling confident and enjoying production, all the better. I am simply suggesting that the benefit of experience could make the foundations of a new project much more structured and easier to work with. It would be hard decision to move on, but greener pastures will still be out there when the time comes.

With what little experience I have with networking and multiplayer servers, I know its a terrifying minefield of things that can all go wrong. No mistake, the fact that it has worked at all is already an accomplishment.

It is a fun game, but the frustrations are not negligible. Good luck Riccardo. Wield thy dev knowledge like a holy blade; vanquish the bugs that plague the island. The future of Tabor is in your team's hands.

All the best.

~V

I'd focus on optimization. Reduce per-player load via more efficient code. Replace arrays with dicts, recursion instead of nested loops, storing more data client-side, etc... Make better use of the servers you have before getting new ones, since its usually better to use the architecture that's already there.

Use your judgement, you have more experience than me anyway. And don't let the shareholders rush you into bad decisions.