-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration with Game Engines #7
Comments
Better late than never: As it is, given the content of this repository, pygase is a Python-to-Python technology. Concerning the MMO part: The core requirement for an MMO would be optimizations that allow for horizontal scaling, so you would want to have several GameStateMachines that simulate different "zones" or independent sub-states of the overall game state in parallel. You would also want to divide players/clients into groups that can be served and simulated independently. This is some higher level architecture I have not yet incorporated into pygase, although I do have some ideas for it. Basically, I have the idea to provide a logical structure for zoning and a template for containerized pygase backend components (where servers and game state machines are separate kinds of docker containers and the game state store runs on redis) that can be used with orchestration technologies, such as Kubernetes. The background behind this project is exactly that I wanted a viable networking technology for backends of MMO-like games in Python. I'm working full-time on non-game related stuff though, which leads to this project lying dormant for countless months for example. TL;DR: Only with a lot of work. Feel free to fork though. |
Noted! The "zoning" logic might even be an implementation detail on the game side of things by the sound if it. |
Can this be used as a backbone for an MMO built using Unity3D or Unreal Engine?
The text was updated successfully, but these errors were encountered: