Marauroa Core API: Difference between revisions

These methods add attributes to the RPClass and set their type and visibility. You can also set the parent of this class. Of course, however, a class can have no parent (be parentless).

Once the class has been filled, you can query the data using these methods. These methods alow you to get the class name of the class, the the type of an attribute, determine if an attribute exists and to know if that RPClass is a subclass of another.<br>

You can query the system classes using these methods. Note that it is '''not''' a good idea to modify them once you are running. The class definitions are send to the client on connect hence if you change the class definitions in the middle of a game you will crash your clients!<br>

* ''boolean hasRPClass(String name)''

* ''RPClass getRPClass(String name)''

objclass.add("x",RPClass.BYTE);

objclass.add("y",RPClass.BYTE);

objclass.add("name",RPClass.SHORT_STRING);

objclass.add("dir",RPClass.SHORT_STRING);

objclass.add("score",RPClass.INT);

objclass.add("super",RPClass.BYTE);

objclass.add("!vdir",RPClass.STRING,RPClass.HIDDEN);

objclass.add("!hdir",RPClass.STRING,RPClass.HIDDEN);

objclass.add("?kill",RPClass.FLAG);

Each time you create a new RPClass, as long as you give it a name ( ie: player, position, ... ), it will be added to the system list of classes.

Notice in the example that the HIDDEN attribute must be specified if you want the RPClass to have this property otherwise by default an attribute is visible.

Note: You can choose not to use RPClasses in your application BUT the performance penalty will be big on bandwidth and CPU usage.