README


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

Setting up a Mana server
========================

COMPILATION

0) autoreconf -i (when you cloned via git)
1) ./configure
2) make

The compilation should produce two binaries:

* manaserv-account - The account + chat server
* manaserv-game - The game server


SERVER DATA

The server depends on parts of the client data and also has its own data
repository. These are the 'manadata' and 'manaserv-data' repositories.
Currently, manaserv expects these to be merged into a single 'data' directory.

1) Clone manadata and manaserv-data next to the manaserv repository
2) Symlink a 'data' directory in manaserv to manaserv-data
3) Symlink the following files from manaserv-data to manadata:

  * data/items.xml - Item definitions
  * data/monsters.xml - Monster definitions
  * data/maps/*.tmx{.gz} - Maps


CONFIGURATION

The configuration is currently loaded from ~/.manaserv.xml. An example file is
located at docs/manaserv.xml.

Default option values:

    accountServerAddress    localhost
    accountServerPort       9601
    gameServerAddress       localhost
    gameServerPort          9604


RUNNING

1. Run manaserv-account on one single computer. It will open three consecutive
UDP ports, starting from the one given by the configuration option
"accountServerPort". This first port is the one you should advertise to your
users. The configuration option "accountServerAddress" should contain the
public address the server runs on, as it will be sent to the users as the
address of the chat server, which happens to be the account server for now.

2. Run manaserv-game on multiple computers. Each game server will open one UDP
port given by the configuration option "gameServerPort". It will also connect
to the account server given by the configuration options "accountServerAddress"
and "accountServerPort". The configuration option "gameServerAddress" should
contain the public address of the computer the server runs on, as it will be
sent to the users. The file data/maps.xml contains the maps the server will
load and register on the account server; split it across your multiple game
servers, in order to balance the load.

Access to port "accountServerPort + 1" of the account server can be restricted
to connections from game servers only. Users do not need to access it.


TODO: Explain about automatic first time creation of database
TODO: Explain about setting a character to be administrator