[LDSO] Tron 2.0 Forum

Hi guys,

I wanted to create a new TRON KillerApp server, but I have only a decent Linux box running Debian. But I thought, 2x2,4 GHz and 8 Gig of RAM would make a damn fine machine for all of you out there, so I figured out a way to run it on Linux anyway. Without a monitor, from commandline and with an extra user in its own environment, so it should not be possible to use its security holes for gaining access to your machine. I also added a failsafe script that kicks in and restarts the server if it crashes.

You will have to install Tron, the unofficial patch 1.042 and KillerApp on your Windows machine in order to copy some files from there later on. Lets start:

First, we login to our machine via ssh (as root user) and create a new user called gameserver. This one will be used for running our TRON server:
Now we have a new user without a shell. No one can login to your box with this user. Its home directory is /home/gameserver. Fine. Lets move on, the next step is installing the needed software for running the TRON server:
Wine is needed to emulate a windows environment, xvfb is creating a virtual screen later on, so we can run the server without a screen attached.

Now create a new directory /home/gameserver/tron with
and place the following files into it:

Note that there has to be a config inside the ServerData folder. And JUST ONE CONFIG. So you should start up the program at least one time on your windows box and do all the required settings in the multiplayer wizard. After that, you have a preconfigured configfile that you can copy to your linux box.

Second note: Get a msvcirt.dll somewhere on the internet or copy it over from your Windows box into the tron-folder. Wine needs this file to start up the server.

This is it - the tron server files are on your box and your user is created. But in order to start up properly it still needs some registry entries in your fake windows environment. Otherwise the TRONSrv.exe fails with a "Could not load resource file" error.

To create your fake wine folder, type
into your terminal. The program will create a /home/gameserver/.wine folder for our settings. In that folder, our registry settings are stored.

Press CTRL+C to quit the program (you can't use it without a display) and type
to return to your previous user.

Now type the following into your terminal
An editor should open up. If not, install the program mc with apt-get install mc.

Directly after the line
add the following code
Don't forget to enter a correct cdkey. I will not give you mine

Since you chose to start TRONSrv from the Z: drive you will still have to tell wine which folder to use as the Z: drive. In our case, this is /home/gameserver.
To do so, create a symlink with the following commands:
Now we set up a script that starts your tron server.

Create a new crontab for the gameserver user with the following command:
Paste the following content into the editor and press F2+F10 to save and close it:
What this does: It starts the script tron_check.sh every 60 seconds - so we gonna have to create that and fill it with contents:
The editor opens again. This time, paste the following commands into it. Close with F2+F10.

Important: Don't add more than one config in the "ServerData" folder. This does not work and opens the wizard. Since we have no screen, we can't use it to start the server.

Now we will make sure, that the whole directory belongs to the right user and that the script is executable:
Done! Now wait some seconds and your server should show up in the master list! If not, unblock the ports 13139, 28888-29901 (TCP) and 27888-29901 (UDP) in your firewall.

You can check my server status here, it is running very stable via wine:

http://hirnschwund.net/" onclick="window.open(this.href);return false;

Running a second server is also possible, but a bit more complicated. I will not cover that here, however I am here if anyone needs assistance.

Wow, that's really a lot of work isn't it. But I guess it's worth it, since Linux servers are easier/cheaper to obtain and are more stable.

Thanks for going to the trouble to write up this guide.

Not a Linux user myself, but brilliant job with the tutorial! Information like this is always helpful.

Maybe we should add it to the wiki?

Nice stuff! As a Linux user, i know that it must have took some time to build up that setup. And good to see that there is an option to play for guys like me (as i'm from Germany), so not needing to 'jump over the great lake'... if i just would find some time to play again... geez.
Good job, keep going!

xistence wrote:Nice stuff! As a Linux user, i know that it must have took some time to build up that setup.

Building up the scripts was very easy as I figured out how to write them a long time ago. The biggest problem was the fact that the server doesn't startup without proper registry entries. Adding them without any interface was a bit hard to manage. Older Lithtech games are a bit more userfriendly (:

The system is far from perfect as it cannot detect if the servers uses 100% CPU and kill it afterwards. This happens very rarely but it can happen and affect all other servers running on the machine.

Once I figured out how to do that I will post it here. Servers are running until I run out of money (which will hopefully never happen).

deeahchur wrote:Maybe we should add it to the wiki?

Sounds like a good idea. I can add it later. Or, schmatzler can add it himself.

I've been doing a bit of work on the Wiki, updating things a little here and there. I took the opportunity to add schmatzler's tutorial to the Wiki.

I didn't spend too much time on formatting it, which probably could have been done better. I might go in and clean it up a bit more, later. Or perhaps schmatzler can edit it himself, to make it the way he wants.

Thanks. I'm fine with it the way it is. I have never been much into WIKI's, because I think someone that needs this information will find it much easier on this forum than in the Wiki.

Thanks for this guide!

Just a quick addition: I refined the script that checks if the server is running.
It also runs a second check on my web frontend here to see if the server is really online.

Doing the sidecheck will restart the server if the .exe is still running, but it has lost access to the internet, because it somehow broke. This will also cover things like "Damn, it runs but takes up my CPU".