Client Object

• 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

This article describes a future concept. It may still have some open issues and it was not decided, yet, whether to implement it in this way.

Proposal

• Instead of having custom client objects in a per application basis define one that can be enhanced via plugins.
• Specify Client Object implementation on ini file

Reason

• Not all applications need existing attributes like x and y
  • Those should be handled via plugins
• Standardize approach

Example Implementation

Client Object

Discussion

I am strongly opposing putting such game specific attributes and logic into Marauroa. It might be a good idea to create a set of libraries that can help developing certain types of games by providing functionality that is typically used by a game of the respective type. But Marauroa should focus on client/server communication and database persistence. Marauroa does not even know about x and y as your wrongly claimed although most games have coordinates. So adding even more things such as grumpy, buddies, ignore in your code is out of scope for Marauroa. --Hendrik Brummermann 18:07, 14 May 2011 (CEST)

I'm not saying that my example is the way to go, I'm saying it should be extensible enough. I use interfaces and define the client object at runtime loading by reflections like other objects are (i.e. world implementation). The same should be available for the client object.--Javydreamercsw 22:17, 27 September 2011 (CEST)