GameDesign: Difference between revisions

So let's define the reply to each message. Before explaining how to process eahc message, let's clarify that the best way of modelling this system is using finite automates, (finite state machine) where, based on the input, we change the state we are currently in and produce an output.

So open the configuration file marauroad.ini ''(or any other)'' and edit the next fields

jdbc_class is the field that says what Driver to use. Please refer to your software manual to see the multiple options.

jdbc_url points to the type and source of the information, for MySQL the string must be as follow:

jdbc:mysql://ip:database_name/

jdbc_user is the username for the database and jdbc_pwd is the password for that username in the database.

Then simply save the changes and ready.

Before using the application with the database, you need to create the database itself. So in case of MySQL just open MySQL and write:

The rest of code is handled by the server itself, and will create the tables if they don't exits.

PlayerContainer is the data structure that contains all of the needed info about the players to keep the game running.

It consists of a list of RuntimePlayerEntry objects, and is heavily linked with the PlayerDatabase, so we can hide the complexity to GameManager. By making PlayerDatabase hidden by PlayerContainer we achieve the illusion that managing the runtime behavior we modify automatically the permanent one.