How to setup Renegade server

[ExEric3]

1. Download Renegade FDS.
First of all, you need FDS binaries. You can download the stock FDS binaries below. You need this before TT patch else server will not function.

Download mirror provided by CnCFPS: Renegade Free Dedicated Server installer

2. Download TT Patch
TT patch adds a lot of features, fixes and improvements to both Game and FDS. To download the TT patch for server, you need to visit https://www.tiberiantechnologies.org/downloads
You should download the "The Tiberian Technologies server files - 4.x" from the page, under title "The Tiberian Technologies server files".
After downloading the zip file, open it and you'll see "serverfiles" folder. Extract everything in it to your server folder, overwrite existing files.

At this point, you have a fully working FDS with basic features in. Optionally, you can install an advanced server side manager which is called Dragonade, by Whitedragon.
Dragonade adds a lot of features like advanced kill messages, it's own Gamespy broadcaster, vehicle queue and more. I'll detail more in the next title. If you don't want to install Dragonade, jump to 4th step.

Direct link to latest server package build (actually v4.8 Update 3 - revision 8951)

3. Download Dragonade
Dragonade is an advanced server side game manager made by Whitedragon, adding countless features to game, console and scripts development. You can find the latest Dragonade releases from this GitHub repository by Unstoppable: Dragonade Releases

After you download it, extract the contents of "Server" folder to your server folder, overwrite existing files. Congratulations, now you have a fully functional server with advanced features in.
Next step, you need to configure your server.

4. Configure FDS

• If you didn't installed Dragonade, you can configure your server from ssgm.ini.
• If you installed Dragonade, you can configure your server's core features from da.ini, crates from da_crates.ini. You can also use gamemode specific features from da_<gamemode name>.ini, every option from da.ini works in here as well.

If you have Dragonade or not, you must go to ssgm.ini and da.ini (if exists) and change your Port (for ssgm.ini) and LogPort (for da.ini) to something else except 7025. This is a very sensitive port which everyone can read your server console and execute commands freely. If you want to leave it 7025; well, you've been warned. Make sure both values match if you're using Dragonade.

If you want to use XWIS instead, you can fill in the required options in server.ini, if you want to use GameSpy:

• If you don't have Dragonade, set the GameType to GameSpy.
• If you have Dragonade, set GameType to LAN (LAN option forces your game port to 4848) then in da.ini, set EnableGameSpy option to 1. (You can also set GameType to WOL if you want to list your server both in XWIS and GSA)

If you want to host your server both on GameSpy and XWIS, you will need Dragonade. Or you can use GameSpy plugin of BRenBot, in 8th step. BRenBot's GameSpy plugin is not recommended for use as it's not giving enough information about server, compared to Dragonade.

• "server.ini" file also lets you to choose few options for gameplay.
• "svrcfg_cnc.ini" in Data folder lets you change your server name, max players, message of the day, and basic information.

Every option in all configurations are self-explaining, reading comments should be enough to understand their operation.

• "tt.cfg" is where you should put your rotation and/or game definitions. A tutorial to install maps and content pack is detailed on 5th and/or 6th step(s). 7th step will guide you to add your content packs and maps in rotation.

5. Install maps

TT uses a new system called TTFS, which supports clients to download maps from in-game while joining a server, or in background while playing (if enabled). Create a folder in your server folder, and put your maps in the folder, for example "mapfiles". Do not put your maps in Data folder! 

There are 2 ways to convert and install your maps:

• You can convert and install your maps and packages using command line, TT wiki explains it briefly at https://www.tiberiantechnologies.org/wiki/index.php?title=Resource_manager_documentation#PackageEditor. Assuming your maps in your "mapfiles" folder, open a Command Prompt, browse to your server folder, and type the following command:

  packageeditor convert "mapfiles\YourMapName.mix" <Version (Example: "1.0")> <Author (Example: "Westwood")>

  You don't have to put actual author's name for Author, but it's preferred to put map owner's nick or your server's name.
  After that, you will get a response from application like this:

  Package was saved to 'C:\Your\Server\Renegade\FDS\ttfs/packages/01234567.tpi'. You can now install it via 'packageeditor install 01234567'.

  You should do what the message tells you to do.

  packageeditor install 01234567

  After this you can delete the maps you converted to save from space.

If you want to create a server content pack to add features like chat sounds, custom models, replacements, modifications, jump to the next step; if you don't want to, jump to 7th step for "tt.cfg" guide.

6. Create a server content pack
For this step, we will use a tool called XCC Mixer, included in XCC Utilities from XWIS. After downloading XCC Utilities, copy a random Mix file from your game, server or wherever you want and rename it whatever you want (do not prefix your content pack's name with "C&C_").

Then, open it with XCC Mixer and clear everything in it by selecting all with Ctrl+A and Delete key. Now you can add whatever you want in your content pack.

If your modification modifies presets, don't forget to include the "objects.ddb" in your content pack. Otherwise your modifications to presets will not work. Loading up your modifications will be detailed in 7th step.

After you're done with your content pack, install it like a map just like in 5th step. Put your content pack into "mapfiles" folder, and execute the same commands to install it. You can create as many as content packs you want, there is no limitage as far as I know. After this you can delete the content pack you converted to save from space. If you want to update your content pack, you need to delete old one using the following command:

packageeditor uninstall <Name of your content pack's MIX file (example: if mix file name is "ContentPack.mix", type "ContentPack")>

And then, you can install new one like a normal map. Now, proceed to 7th step for "tt.cfg" guide.

7. Configure rotation

TT uses a new method to define rotation. Compared to svrcfg_cnc.ini, this rotation structure allows you to define game definitions (for example, custom preset databases and content packs) and a location to let clients know where to download maps.

Typically, a tt.cfg file should look like this:

gameDefinitions:
{

};

rotation:
[
   "C&C_Field"
];

downloader:
{
   repositoryUrl = "http://ttfs.ultraaow.com";
};

If you have any content packs installed and you want to use them, you will need to add game definitions first.

Game definitions are maps with extra dependencies. Game definitions allows clients to install more than 1 mix files for a single map. This is a useful case for modders and server owners to keep stuff organized. And in our case, which is content packs, you can add every asset you want into server without modifying map files. Creating game definitions are easy:

YourMapName:
{
	mapName = "C&C_YourMapName";
	packages = ["C&C_YourMapName", "YourContentPack"];
	serverPresetsFile = "objects.ddb";
};

This is the structure of a game definition. You should replace "YourMapName" with the map name you want, and "YourContentPack" to your content pack. So if you want to install "C&C_Field", with a content pack named "MyServerContent" with no custom presets file, game definition should look like:

Field:
{
	mapName = "C&C_Field";
	packages = ["C&C_Field", "MyServerContent"];
};

If you have a custom presets file and want to use it instead of default objects.ddb, first you need to move your preset file in Data folder, and give it a different name or extension. (Changing extension name is generally preferred, and the example below takes a custom preset file named "objects.aow") Then you should add an option to load your custom presets file for the game definition, like so:

Field:
{
	mapName = "C&C_Field";
	packages = ["C&C_Field", "MyServerContent"];
	serverPresetsFile = "objects.aow";
};

You can have as many preset file as you want to use with game definitions, but since each server content can have only 1 objects.ddb file, you may need to create multiple content packs containing your custom presets file.

And finally, you need to add game definitions you created under gameDefinitions section, and "YourMapName" under rotation section like this: (I also added C&C_Canyon for example)

gameDefinitions:
{
	Field:
	{
		mapName = "C&C_Field";
		packages = ["C&C_Field", "MyServerContent"];
		serverPresetsFile = "objects.aow";
	};
	Canyon:
	{
		mapName = "C&C_Canyon";
		packages = ["C&C_Canyon", "MyServerContent"];
	};
};

rotation:
[
   "Field",
   "Canyon"
];

downloader:
{
   repositoryUrl = "http://ttfs.ultraaow.com";
};

If you don't want/have a content pack, add the full map name to directly rotation section like this:

gameDefinitions:
{

};

rotation:
[
   "C&C_Field",
   "C&C_Canyon"
];

downloader:
{
   repositoryUrl = "http://ttfs.ultraaow.com";
};

The TTFS URL "http://ttfs.ultraaow.com" is obsolete and no longer maintained. Check also 10th step - How to setup own TTFS server for custom content and maps

8. Install a bot/regulator

This setup is optional and is not required, but it's recommended to have a server regulator. If you don't want to install a bot, skip this step.

You may need a fast and pratic way to regulate and moderate your server, here comes IRC bots for your help. There are really a lot of options, but I'm going to detail the most popular one BRenBot. Since it's original website at new.brenbot.com is down, there is BRenBot repository at https://gitlab.com/danpaul88/brenbot. There is an auto-builder when the repository gets updated. You can view all builds at here. Click the latest "passed" job, and then in the sidebar at right, click "Download". After downloading it, extract it to a folder like "brenbot" in your server folder. Before running it, configure your bot. It's self-explained as well as other configurations.

Even though it's website is down, there are still several plugins available such as Jukebox, Status Reporter, Ping, Seen, etc. from here and here. All you need to do is putting ".pm", ".xml" files in plugins folder.

If you're experiencing issues while getting your moderator/administrator powers with BRenBot, make sure the option called "Moderators_Force_Auth" in brenbot.cfg is 0. If you want to leave it 1, you have to register your nick. To do that join your IRC channel, type /query <your bot name> (or right click your bot, and choose "Query", "Message", "Page", or any other option to private message), and use !help command to find out the right command to register your ingame name to bot. Once you do that, you will need to authenticate yourself either:

• Paging /Host, using !auth command like "!auth <your password>",
• Page your server if it is XWIS, using !auth like "!auth <your password>",
• Use !auth command in admin channel of your bot, like "!auth <your ingame name>".

 

9. Final touches
Your server is now ready a double-click away to run! If you need to open ports, follow these steps:

• Open "server.ini" configuration, if your GameType is not LAN, open the Port value in configuration on UDP. If your GameType is LAN, open 4848 port on UDP.
• If you are hosting your game on GameSpy using Dragonade (GameType is LAN) : In "da.ini", open the GameSpyQueryPort value in configuration on UDP.
• If you are hosting your game on GameSpy without Dragonade (GameType is GameSpy) : In "server.ini", open the GameSpyGamePort and GameSpyQueryPort, both on UDP.
• If you need to read your console or send commands to your server externally, or you have a remote control utility for your server, in "server.ini", open RemoteAdminPort on UDP. Only open this port if you need remote access to your FDS console using RenRem.
• This is NOT recommended, but if you need to access your SSGM Log Port server, open the Port value in "ssgm.ini", on TCP. This port is extremely vulnerable, do not open this port if you don't know what you're doing.
• Open ports in your firewall

10. Follow others tutorials in this topic:

How to configure Windows Firewall for server

How to setup own TTFS server for custom content and maps

You are done.

Credits to Unstoppable and his tutorials.

 

Changes - 15.9.2024:

• added links for downloads to latest TT server build v4.8.3
• added TTFS setup and Firewall setup into one thread

[ExEric3]

In this tutorial I'll tell about how to create your TTFS server, containing your packages and maps.

This tutorial will assume you installing the web server into a Windows system, for the first time (while no other instances of any web server running), FDS being in the same computer, and use the web server for only TTFS hosting.

 

1. Install XAMPP

XAMPP is the most popular (as far as I know) hosting application. You can see a list of downloads at https://www.apachefriends.org/download.html

The main topic of this post is not how to install XAMPP, but I'll tell the steps briefly:
Download the latest version of XAMPP.
On "Select Components", we only need "Apache". You can untick everything else. But if you know what you're doing, you can choose other stuff.
You're done! You can control web server from "Apache" module in Control Panel.

2. Prepare your server

Now, navigate to your XAMPP folder, then "htdocs" folder. You'll find some initial files there, you can delete them all.
Open your notepad, and save that blank file at your "htdocs" folder as index.html, don't forget to choose All Files (*.*) from dropdown. This file will prevent others to see your web site root.

3. Create a symbolic link

Symbolic links are shortcut-kind links which appears as folders or files. We'll use this to link our server's TTFS folder to web server. Open a Command Prompt, and navigate to your web server's "htdocs" folder with "cd" command.

Then, type the following command:

"mklink <Your server name here> /d <Your server's TTFS directory here>"

<Your server name here>: Name of the link.
<Your server's TTFS directory here>: The root folder of your TTFS.

For example:

"mklink MyServerTTFS /d "D:\MyServer\Renegade\FDS\ttfs"

You're done! Now if you check your "htdocs" folder, you'll see a shortcut named <Your server name here>. And when you open it, it'll appear in your "htdocs" folder instead of taking you to actual place.

4. Configure tt.cfg

We need to tell the server where your TTFS server is. First, you need to find out your public IP address. To do that, go to https://www.whatismyip.com/ and note down your IP address. Now, go to your server's tt.cfg and open it.

Scroll down until you see "repositoryUrl". Type in "http://<Your IP address here>/<Your server name here>"

<Your IP address here>: The IP address you noted down.
<Your server name here>: The server name you entered in 3rd step.

Now Renegade knows where your TTFS server is.

5. Final touches

If you need to open ports, open the default port, which is 80, on TCP protocol.

Credits to Unstoppable and his tutorials

[ExEric3]

If you opened a server recently and nobody can join server even if you did port forwarding correctly, there might be an issue with your firewall, and you will need to add rule in your firewall to allow forwarded ports. Follow this tutorial to add a rule in your firewall.

1. Inbound rules

First, you need to open Windows Firewall, open "Run" window by hitting Win+R, type "WF.msc" in it, then hit Enter.

You should get a window like this:

Then on the left panel on the window, there are "Inbound Rules" and "Outbound Rules". Click on "Inbound Rules", then on Right panel, click "New Rule..."

Clicking on it will open a pop-up. On first step, click on "Port" and then "Next".

On second step, window will ask you to choose protocol type and ports. Choose the protocol you want, choose "Specific local ports", and then put the port you want to allow.

On third step, window will ask you to allow or block this connection. Choose "Allow the connection".

On fourth step it will ask which profiles to apply this rule, check all profiles.

On final step, it will ask you to name your rule, and an optional description. Name of the rule will help you to find this rule when you need it.

When you done, click Finish and you should see the rule added in list.

2. Outbound rules

Now, you need to do the same steps on "Outbound Rules". Follow the same steps just like how you did for "Inbound Rules". Click on "Outbound Rules" and click "New Rule..." on the right panel.

Choose "Port",

Choose your protocol and put your port in,

Allow the connection,

Check all profiles,

Give it a name,

And you're good to go!

Final touches

• You will need to repeat this entire process for all of your ports.
• If your port serves both on TCP and UDP, you will need to repeat the process to add other protocol.
• If adding rules didn't work, you may need to restart your computer/server for changes to take effect.

Credits to Unstoppable and his tutorials