Setting Up

This page will help you setting up a RetroSpy Server.

First, make sure you have produces a working binary. If not sure, see here.

Here's what we need to do in order to achieve this result:

1. Adding RetroSpy database into MySQL Server
2. Configuring the INI file
3. Connecting the Game into the Server

Database setup

None yet.

INI Configuration

Create an INI file in your Server directory called RetroSpy.ini

Configure a basic ini as following: `[Database]

Host=Your database host (leave empty if you're using a socket)

Password=Your password (leave empty if you don't have a password)

Username=Your username

Database=Your database name

Socket=Your socket (leave empty if you are on Windows or you use a host-based connection)

[Server]

DefaultIP=Input the ip that the server will bind

[Modules]

Load0=playersearch

Load1=qr

Load2=keyserver

Load3=natneg

Load4=playerchat

Load5=playerspy

Load6=serverbrowsing

Load7=peerchat

Load8=legacyms

Load9=legacystats

Load10=legacystatsprocessor

[natneg]

Instances=1

ProbeIP=The probe ip that will bind

BindIP1=The first ip that the negotiation will bind

[legacystatsprocessor]

WebDir=gamestats

[peerchat]

QueueIP=127.0.0.1`

If you want a detailed explanation of the INI file, see here

Connecting the Game into the Server

There are currently 3 methods to connect a game into the Server.

1. Patching the game
2. Patching the hosts file
3. Using a DNS Server

Patching the game give the best performance, and it's the onliest method that could use TLS/Secure connections, but systems that can't load the hacked game won't be able to use it.

Hosts file is the easiest to configure, and it's perfect for Development devices (since you will connect to yourself), but requires that all the devices to patch this file, and dosen't work on consoles.

DNS Server is the best configuration for device that cannot patch the game (like consoles). It needs that all the devices sets the primary DNS server to the server you're creating.