Here you should find all the technical
information needed in order to run iGOR successfully.
iGOR Ports - a
listing of all the ports used by iGOR.
GPL Ports - a listing of all the
ports used by GPL.
Files and Installation - the
files and folders that iGOR creates/needs.
Coding Notes - what makes an
iGOR.
iGOR.ini
and Multiple Installations - more tech.
iGOR uses several ports for internet
communications. Some of these can be changed,
others cannot.
IRC Chat
Port 6667 (TCP/outgoing)
- cannot be changed.
IRC Ident
Server
Port 113 (TCP/incoming)
- cannot be changed.
- it is not essential that this port is opened, but chat connections
will be much quicker if you can open this port for incoming connections
/ add it to your port forwarding list.
Race List
Port 30197 (TCP/outgoing)
- cannot be changed.
Remote Hosting
Client
Port 30196 (TCP/outgoing)
Remote Hosting
Server
Port 30196 (TCP/incoming)
- this can be changed either in the Listening dialog, or (when iGOR is
not running) by editing iGOR.ini, line
"ListenerPort
= 30196"
- if you are running as a remote host, using NAT (or similar), this
port will need to be forwarded on your router.
Racelist
Pinging
Races in the racelist will be pinged in the normal fashion (ICMP), so
ports do not need to be opened. When hosting a race, you have the
option of making your server non-pingable. Use this only if you
really don't want your host to be pinged, and cannot prevent pings with
other hardware or software on your system.
Security Client
Port 30198 (TCP/outgoing)
- cannot be changed.
Security Server
Port 30198 (TCP/incoming)
- cannot be changed.
- if you are running as a remote host, using NAT (or similar), this
port will need to be forwarded on your router.

GPL Ports
By
default, GPL uses the following ports:
Broadcasting
Port 6970 (UDP/outgoing)
- used by GPL to broadcast the status of the races to the RaceList
server.
HOWEVER, iGOR changes this port to 30199
(UDP/outgoing) to keep the range of ports required by iGOR to a single
block (30196-30199).
Pings
Port 6971 (UDP/incoming)
- used by GPL for ping responses. Not used by iGOR.
Racing
Connections
Ports 32766-32786 -- 21 in total (UDP/incoming)
32766 is used for incoming connections,
32767-32786 are used for existing connections to each individual client.
- if you are hosting a race you will need to open/forward 32766 to
32766+n, where n is the maximum number of players you will be allowing
to join your races. e.g. for a 6 player server, you will need
32766-32772 inclusive.
To install iGOR, simply run the combined
GEM+iGOR installation program. This will install both GEM+ and
iGOR into the same folder structure.
Before running iGOR for the first time, you must run GEM+ to patch your
Modded exes and create the necessary files in
sierra/gpl/mods/. Without these files, iGOR will not know
about your GPL setup, and you will not be able to host or join a race.
iGOR consists
of:
iGOR.exe - the program.
chanbeep.wav
- used for audio notifications of public chat messages.
userbeep.wav
- used for audio notifications of private chat messages.
iGOR.ini
- created and updated whenever you run iGOR.
Files created
during your use of iGOR:
iGOR/uids.ini
sierra/gpl/gplload.txt
sierra/gpl/postgpl.txt
sierra/gpl/securserver.ini
sierra/gpl/securserver2.ini
Secur files:
sierra/gpl/gplsecurloader.exe
sierra/gpl/securserver.dll
sierra/gpl/toreadenc.txt
GPL files
loaded when starting iGOR:
all
sierra/gpl/players/player__name/player.ini files
all sierra/gpl/tracks/trackname/track.ini files
all sierra/gpl/seasons/__season.ini files (as listed by gplmods.ini)
sierra/gpl/mods/gplmods.ini
all sierra/gpl/mods/*.bmp (as listed in gplmods.ini)
sierra/gpl/mods/gearsets.ini - for Setup
Shop only.
Coding
iGOR was
written using Borland C++ Builder 5.0. It uses a number of
third-party addon components:
TTaeRichEdit
- memo component for IRC chat windows
TircClient
- IRC protocol
TAdvListView
- customisable list view
TFloatAdjuster
- edit box with mouse drag changing of the numbers
Indy -
various internet components
And I expect some others that I can't remember at this time...
iGOR.ini and
Multiple
Installations
At
present, only one copy of iGOR can be running on one machine at the
same time. This is in order to prevent numerous bugs that could
occur with e.g. one copy reading and another copy writing to the same
file. I plan to change this in the next release so that multiple
copies can be made to work, so long as they are completely separate
installations.
Additionally, it should be noted that iGOR doesn't do anything with the
Windows Registry, so you are free to install it wherever you like;
moving the install to a new folder won't break anything. The one
file that iGOR depends on for settings is iGOR.ini (and obviously your
GPL installation ! )
If you ever need to edit iGOR.ini, MAKE SURE iGOR ISN'T RUNNING!
On exit, iGOR updates iGOR.ini with any changes made during runtime, so
if you edit it whilst iGOR is running, you'll lose those changes!
|
|
|
|