Let’s face it; making a dedicated server for ATOM’s Breach wasn’t ever the easiest of tasks and managing it was far more annoying. The chore-like pre-requisites such as running TELNET and entering cryptic commands crippled the interest of the players to do the necessary task: manage and enjoy playing on their server.
All hope seemed lost until a clever little somebody managed to create a simple yet intelligent software that lets you manipulate the server’s parameters as easily as anything!
Yes folks, a nifty little software termed as the “Breach Remote Console” acts like an on-the-desktop console for changing game-types, password settings etc, much in function like the console in games such as Call of Duty 4, yet more user-friendly.
Moreover there is also another similar but more ‘streamlined’ tool called the Breach DSM, which we shall also have a brief look at. Before we go into how to use these remote consoles, here is a small but helpful little guide to setting up your dedicated game server:
How to Setup Breach (PC) Server
Obviously we know that Breach is steam-based, and hence the servers will run on steam too. The first two and most important steps are to get your router to forward the ports and to allow access to through your firewall, whether it’s Window’s stock firewall or any other. (Unfortunately we can’t really afford to go into basic detail as to how you would forward your port, as the method varies with every router model/brand. However it isn’t rocket science and tutorials for doing so can be found easily on the web).
Breach (PC) Server Port Forwarding
The ports to be forwarded are from 27000-27030. Just to be on the safe side its best to forward on both TCP and UDP protocol.
Once the ports have been forwarded, you can find the dedicated server launcher as followed:
\Steam\steamapps\common\breach dedicated server \BreachServer.exe
Don’t launch the executable file yet, as we have still a few things to do before we can get a clean server up and running.
Breach (PC) Dedicated Server.ini ‘Configuration File’
Now the next step is to basically create a Server.ini. It might sound daunting, but gladly there is an already-present sample Server.ini file located as followed:
\Steam\steamapps\common\breach dedicated server\Server.ini.example
You can edit the parameters of the sample file and use it as your own. Just make sure to name it Server.ini and have it placed in the same folder as the sample file.
Breach (PC) Server Admin Notes
Once its done you might want to look at some notes for administrating the dedicated server. These notes can be found as followed:
\Steam\steamapps\common\breach dedicated server \ReadMe_RemoteConsole.txt
You’re pretty much ready to run the server. Just make sure you start the steam client and login to steam. However, there is a way around this as now a new dedicated server fix has been launched which allows you to run a server without requiring to log into steam.
You can download it from here. Once you’re all set execute the BreachServer.exe and then run Telnet (the Telnet part can be skipped if you wish to use the remote console application mentioned above. However if you do wish to use Telnet make sure it is activated in windows features if you are using Windows Vista or Windows 7).
Make sure to test the server and stress it to maximum to check its stability. Congratulations, you finally have your own dedicated server for Breach!
Now let’s move onto using the Breach Remote Console.
Breach (PC) Remote Console
Before going on to install this tool, make sure you have Microsoft .NET Framework 4 installed on your OS. After that little pre-requisite is taken care of, you can download the remote console from here. Unzip the .zip file in the desired location and run the Setup.exe to install the software.
How to Use Breach (PC) Remote Console
- Start Breach Remote Console.
- Notice the list box on the left side. The context menu for it can be used to add, edit or delete servers.
- Right click on the list box and select ‘New’ and enter your server’s IP address. Press OK in the server dialog box.
- Now select the name of your server and you’ll probably see the list box on the right – fill up with the names of players playing currently on your server. Don’t get too worried if you don’t see any names, as long as the server is recognized all’s cool.
- Try and run the game and see if you can find your server in the game’s server browser. If everything was done correctly, you’ll be able to see it and join it as well.
- From the Players tab in the console you’ll be able to ban a player’s IP or ID and also refresh the list.
- You can add and edit the map rotation by viewing the maps from the Maps tab.
- From the Bans tab you can view the players you have banned and can ban IP addresses, delete IP addresses or IDs and also remove bans enforced on players.
- From the Settings tab you can change the name of your server to whatever you desire.
The Breach DSM is a more user friendly console which performs very similar to the above mentioned Breach Remote Console. You can visit their official site and download the latest version from there.
Breach DSM pretty much gives you a similar user-friendly interface to manage your server. Firstly you have to enter your server’s IP address in the top left area and connect to it. You can configure your Server.ini via the ‘Configurator’ located next to the server address.
There are four tabs – Map Rotation: Which is used to modify the rotation of the maps, Current Players: Which shows you the list of players currently playing in your server (allows you to take necessary actions against them as well), Bans: Which shows the ban-list and Server Dialog: Which shows the on-going dialogues in the server.
There are also quick buttons of ‘Next Map’ and ‘Restart Map’ located next to the ‘Configurator’ to allow instant changing and restarting of the maps.
Well there you have it. That pretty much wraps up everything you need to know about setting up and managing dedicated servers in the easiest possible manner. If there are any questions regarding this matter please let us know.