How we built an auto-scalable Minecraft server for 1000+ players
1–10 of 145 posts
Re: How we built an auto-scalable Minecraft server for 1000+ players
#2This is nice magical software. Well done.
Re: How we built an auto-scalable Minecraft server for 1000+ players
#3I’m curious to know how or if this solved any of the issues inherent with multithreading. Moving the threads to new processes can’t fix race conditions.
Re: How we built an auto-scalable Minecraft server for 1000+ players
#4How did MMOs like Asheron's Call and Wow handle this?
Re: How we built an auto-scalable Minecraft server for 1000+ players
#5How did MMOs like Asheron's Call and Wow handle this?
For WoW, at a very high level, instancing and sharding. Players are spread across realms.
The zones are so large that by nature players will be spread out leading to less interactions. Raids are instanced to just your party. In areas with natural congestion (such as auction houses), things could lag at times.
While combat and movement is realtime, it's mostly waiting for timers, so the latency and bandwidth requirements are reduced compared to a first person shooter for example.
Re: How we built an auto-scalable Minecraft server for 1000+ players
#6Hi, I made this! Was gonna wait until it was downloadable and the documentation was more complete before posting it on HN. Thanks for sharing it though.
The Minecraft setup will be available and useable by anyone Wednesday of next week. More documentation and a roadmap will follow shortly after.
Re: How we built an auto-scalable Minecraft server for 1000+ players
#7Hi, I made this! Was gonna wait until it was downloadable and the documentation was more complete before posting it on HN. Thanks for sharing it though. The Minecraft setup will be available and useable by anyone Wednesday of next week. More documentation and a roadmap will follow shortly after.
This is very impressive work! Do you plan to make WorldQL highly available? It seems like if it died you'd loose the server.
Re: How we built an auto-scalable Minecraft server for 1000+ players
#8I’m curious to know how or if this solved any of the issues inherent with multithreading. Moving the threads to new processes can’t fix race conditions.
It utilizes a rollback-based system to mitigate races between Minecraft servers.
I’m writing up some formal documentation on it now, I really wanted to have that done before this project was exposed to the scrutinizing Hacker News community, but I can’t control what people share! :)
Stay tuned.
Re: How we built an auto-scalable Minecraft server for 1000+ players
#9Hi, I made this! Was gonna wait until it was downloadable and the documentation was more complete before posting it on HN. Thanks for sharing it though. The Minecraft setup will be available and useable by anyone Wednesday of next week. More documentation and a roadmap will follow shortly after.
Curious how you plan to handle Redstone and hostile mobs.
Re: How we built an auto-scalable Minecraft server for 1000+ players
#10Hi, I made this! Was gonna wait until it was downloadable and the documentation was more complete before posting it on HN. Thanks for sharing it though. The Minecraft setup will be available and useable by anyone Wednesday of next week. More documentation and a roadmap will follow shortly after.
Curious how you plan to handle Redstone and hostile mobs.
Thanks for your question! Redstone is still WIP but will follow:
1. An optimistic execution strategy (the servers can run their own redstone)
2. A locking system allowing only one server to have redstone current in a given chunk at once.
3. A rollback-based system to repair race conditions caused by (1)'s optimism.
Hostile mobs are ALSO still WIP and:
1. Are only synced if two players are near each-other on two different servers.
2. Have their aggression entirely managed by a WorldQL script which sends messages to the appropriate servers instructing them to call LivingEntity.setTarget on the correct player.
Was hoping nail those both down before I shared it here, so please forgive me! Thanks for your interest and stay tuned.