What is Marauroa: Difference between revisions
Content deleted Content added
imported>Hendrik Brummermann No edit summary |
imported>Hendrik Brummermann No edit summary |
||
| (20 intermediate revisions by the same user not shown) | |||
Line 9:
* Clients communicate with the server, and vice-versa, using a TCP portable network protocol with reliability in mind to allow a stabler experience when online game lag occurs.
* To play a game every player needs an account on the server that is identified by an username and a password.
* Players use their account to login into the server and then choose a 'player' stored under their account to play with. The server then checks the login information using the MySQL or H2 backend and loads the player into the game using the persistence engine.
Line 16 ⟶ 15:
* The server transparently and automatically stores players and game status modifications on the persistence engine, and also information decided by the game developer using their game definition scripts.
* The server side game rules can be written in Python to allow simple and rapid development without needing to recompile the rules engine and without having to know anything about Marauroa's internals. Games rules can also be coded in Java.
* The server generates statistics of usage which are stored in
* Both the server and clients are fully and wisely documented, with documentation about specification and design
[[Category:Marauroa]]
{{#breadcrumbs: [[Marauroa]] | [[Marauroa|Overview]] | [[What is Marauroa]]}}
| |||