RolePlayingDesign: Difference between revisions

This is possibly the most complex part of all the middleware that makes up Arianne.<br>

Role Playing Design is the determining factor on how ''easy'' is to create a new game for Arianne. We had to choose easing the creation of turn time limited based games. Arianne will work better with this kind of games (also known as realtime games).

The whole Marauroa system is managed by two main entities, RPAction and RPObject. There are also several helper classes like Attributes, RPSlot and RPClass

 

Attributes is a collection of pairs of values in the form name-value.

We can store almost any basic type in a Attribute object:

* Sync perceptions: these are used to synchronize clients with the server world representation. This is the only valid way of knowing world's status.

* Delta perception: this is used to send only the changes to the world since the last perception.

 

Our actual Perception system is called Delta². It is heavily attached to the Marauroa core, so I recommend you to use it :)

In a first attempt, we send clients back an action that was the result of their action. However, this made the code really hard because we had to update two different things, perceptions and actions. Instead the solution appears intuitively: Why not join action reply and perceptions.

 

 

See Actions reply in the Objects documentation to know exactly what is returned. However, keep in mind that the return result depends of each particular game.

 

[[Category:Marauroa]]