Marauroa Glossary

• General Information
  • Overview
  • What is Marauroa?
  • Features
  • Glossary
  • Differences
  • History
  • New in Marauroa 3.8
  • New in Marauroa 3.9
• Using Marauroa
  • Building
  • Initial Steps
  • Tutorial
  • Core API
  • Adventure Games Concepts
  • Database Access
  • server.ini
  • Testserver
• Internals
  • Network Design
  • Role Playing Design
  • Database Design
  • Database Access
  • Eclipse
  • Roadmap
  • JUnit

A

Action

An action is a command sent from the client to the server. For example "move to the right".

E

Event

todo

G

GenerateINI

see server.ini

M

Message

The low level network communication between client and server is message based. There are for example message for login attempts and confirmation or rejection of the login. Actions from the client to the server and perceptions from the server to the client are transmitted using messages, too. As a developer using Marauroa to code your own game, you will not see those messages as they are only used internal. The page on network design explains the inner works.

O

object

todo

P

Perception

Perceptions are information about the zone and its content sent from the server to the clients. Marauroa uses a delta^2 algorithm to keep the size of the network traffic down.

R

RPAction

see action

RPEvent

see event

RPObject

see object

RPSlot

see slot

RPWorld

see world

RPZone

see zone

S

server.ini

server.ini is the configuration file of the Marauroa server. It contains both game specific configuration information for the engine and administration related information for example how to reach the database. Most games (and even marauroa itself) provide a GenerateINI program to generate a stub.

slot

todo

W

world

todo

Z

zone

todo