What is Marauroa: Difference between revisions

Jump to navigation Jump to search
← Older edit
Content deleted Content added
imported>Hendrik Brummermann
No edit summary
imported>Hendrik Brummermann
No edit summary
 
(17 intermediate revisions by the same user not shown)
Line 9: 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.
* 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.
* You can develop an arianne client, using the arianne client framework, on any system that is able to compile C code.
* To play a game every player needs an account on the server that is identified by an username and a password.
* 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.
* 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: Line 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 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 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 a mySQL database (so you can later generate fancy statistics from them). Or in case you don't require them, they can be disabled to save CPU cycles and disk space. Marauroa features a modular structure that means modules can be changed and disabled without affecting the operation of other modules.
* The server generates statistics of usage which are stored in the database (so you can later generate fancy statistics from them). Or in case you don't require them, they can be disabled to save CPU cycles and disk space. Marauroa features a modular structure that means modules can be changed and disabled without affecting the operation of other modules.
* Both the server and clients are fully and wisely documented, with documentation about specification and design and not just API documentation.
* Both the server and clients are fully and wisely documented, with documentation about specification and design in addition to the ordinary API documentation.


[[Category:Marauroa]]
[[Category:Marauroa]]
{{#breadcrumbs: [[Marauroa]] | [[Marauroa|Overview]] | [[What is Marauroa]]}}
Retrieved from "https://meet.konsthol.eu/w/index.php?title=What_is_Marauroa"