Revision as of 22:39, 22 February 2010 view source imported>Hendrik Brummermann No edit summary ← Older edit		Revision as of 21:11, 26 February 2010 view source imported>Hendrik Brummermann No edit summary Newer edit →
Line 16: * 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 ~~a mySQL~~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~~in ~~not~~addition ~~just~~to the ordinary API documentation. [[Category:Marauroa]]

What is Marauroa: Difference between revisions