Marauroa Core API: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hendrik Brummermann |
imported>Hendrik Brummermann No edit summary |
||
| Line 209: | Line 209: | ||
Now for the complex part. Where it all becomes a little nuts!: IRPZone and IRPRuleProcessor interfaces |
Now for the complex part. Where it all becomes a little nuts!: IRPZone and IRPRuleProcessor interfaces |
||
=RPWorld= |
==RPWorld== |
||
This class is just a container of zones. |
This class is just a container of zones. |
||
| Line 248: | Line 248: | ||
</source> |
</source> |
||
=IRPZone= |
==IRPZone== |
||
IRPZone is the interface that handles the world content and the perceptions. In most cases you should use the implementation MarauroaRPZone and extend it. |
IRPZone is the interface that handles the world content and the perceptions. In most cases you should use the implementation MarauroaRPZone and extend it. |
||
| Line 298: | Line 298: | ||
* buildMapObjectsList |
* buildMapObjectsList |
||
=IRPRuleProcessor= |
==IRPRuleProcessor== |
||
This class must be implemented fully, but it is a childs toy compared to IRPZone :). This is where you code all your games rules.<br> |
This class must be implemented fully, but it is a childs toy compared to IRPZone :). This is where you code all your games rules.<br> |
||
The API is as follows: |
The API is as follows: |
||