Server configuration

The configuration file has to be named configuration.conf and must always be stored in the same directory as the Node.

This file follows the commonly-used ini format which separates the configuration in named sections and keys. For more information on the .ini format click here

database

Configuration of the database connection. This section is required for the server to startup.

[database]
username=evesharp
password=passwordhere
hostname=localhost
name=evedb

username

The user to use when connecting to the database

password

The password to use when connection to the database

database

The name of the database to use for storing the data. This database has to be setup manually following the installation steps.

hostname

The server where the MySQL instance is running.

logging

force

Indicates the log channels that should be enabled regardless of the supression state they are in (for example for debugging network packets). The list is separated by commas. This is intended for developers only.

[logging]
force=NetworkDebug

Suppressed by default

NetworkDebug

Prints the full package data input/output on the node.

logfile

Configuration for the file log output. If this section is not present there will be no log file created for the session.

[logfile]
directory=logs
logfile=Node.log

directory

The directory where to save the log files.

logfile

The name of the log file to write the loggin information to.

loglite

LogLite is an official CCP tool that allows external logging. The protocol is implemented to allow for an easier log inspection and can be run on any machine as long as the server is configured properly to connect to it. This section contains the server information the log should be sent to.

[loglite]
hostname=localhost
port=3273

hostname

The hostname of the loglite server is running

port

The port in which the loglite server is running

authentication

This section controls various authentication details.

[authentication]
autoaccount=yes
role=ROLE_PLAYER, ROLE_LOGIN, ROLE_ADMIN, ROLE_QA, ROLE_SPAWN, ROLE_GML, ROLE_GDL, ROLE_GDH, ROLE_HOSTING, ROLE_PROGRAMMER
loginMessageType=MESSAGE
loginMessage=Welcome to EVESharp, the EVE Online server emulator written in C#

loginMessageType

Indicates whether the user will receive a message or not upon login. Possible values are: MESSAGE and NONE

loginMessage

Indicates the message to be displayed to the user when logged in. The value can be any kind of HTML or plaintext text, but be wary, no new lines are supported

autoaccount

Enables/disabled the autoaccount functionality. Valid values are: yes, true, 1. Disabled by default

role

The role to use for the accounts created automatically, depending on your setup you might want different roles here. For a development machine these should be okay:

ROLE_PLAYER, ROLE_LOGIN, ROLE_ADMIN, ROLE_QA, ROLE_SPAWN, ROLE_GML, ROLE_GDL, ROLE_GDH, ROLE_HOSTING, ROLE_PROGRAMMER

You can check all the available roles here

character

This section controls various details of the character creation process.

[character]
balance=50000

balance

The default balance a character will have when created. This only applies to new characters. If not specified the default value will be 50000

machonet

This section controls what role the server will fulfill

[machonet]
mode=single
port=26000

mode

What mode the server should be running, there's three different values:

• single: Single instance mode, everything runs off the same server
• node: Node mode
• proxy: Proxy mode

cluster

url

While running in node or proxy mode, the server needs to communicate with the orchestrator, which will keep track of the current cluster status, with this setting you can specify the URL where the Orchestrator is listening for requests

[cluster]
url=http://localhost:5085