We are pleased to announce the first playtest leading up to our next stable release!

Posted by Milanium on Apr 9th, 2016

We have finally entered the feature freeze phase of the development cycle, where we stop adding features and focus on fixing bugs found during playtesting. This is where you come into play! We need your help to give this playtest as wide a test coverage as possible to ensure another successful stable release of OpenRA!

We therefore ask you to please report any and all bugs and problems you encounter on our bug tracker, in the OpenRA IRC channel, or here in the comments. We will strive to fix as many bugs as possible before a final release. Thank you for helping to improve OpenRA!

While there are the usual bug fixes and improvements, a big focus over the last six months has been reworking several fundamental parts of the OpenRA game engine, with changes that will be felt foremost by server operators, modders and mappers. In fact, some of these changes are so fundamental that we will address them in-depth in the articles covering future playtests.

But one thing after the other…

Ingame changes

Quite a few long-standing annoyances have been addressed during the last cycle. Just to name a few, players will no longer be kicked from the server after installing a map, walls now stop bullets reliably, and husks can finally be targeted on refineries.

Other changes and new features include:

By popular demand, a tech level without super-powers has been added to the Red Alert mod.

Zooming is now possible by holding CTRL while scrolling your mouse wheel. For spectators and in the map editor, two additional zoom steps are available.

Cancelling an entire build queue at once is now possible by using CTRL + right click.

Static defenses will now stop tracking their targets once it is out of range. This also sometimes prevented camo pillboxes from cloaking.

Line-building of walls can now be disabled by holding the Shift key while placing the wall element.

A couple of issues related to left-click controls have been solved.

Engineers will no longer be selected when you drag-select a group of combat units.

Fragile diplomacy has been removed.

Lots of minor fixes, UI polish and performance improvements.

As usual, both the Tiberian Dawn and Red Alert mod have received some balance changes. Additionally, a number of Red Alert maps have been revised to be more balanced. A complete list of all these changes can be found in the changelog.

Players finally have a restart option after failing a mission or skirmish!

When team colors are enabled in the settings, they will now be used on the radar map.

You can also set health bars to only appear when units are damaged.

This is for the nostalgic ones among us (and who isn't?).

Nod units in missions now show their proper silver colors known from the original game.

Worms have received some polish and now leave a trail similar to the one from the original game.

Mapping and modding changes

The way that the game handles maps has changed significantly since the last release. We will elaborate on the changes and the reasons for them in a future post, but for now you only really need to know three things:

Maps from release-20151224 and earlier must be upgraded before they will work.

Maps are now installed into per-version subdirectories – like replays.

Installing maps ingame and using the map editor works as normal.

The maps currently available on the OpenRA Resource Center are in the process of being updated,

and we have added an option for you to upgrade your maps manually.

Support for third-party mods will significantly improve with the next release. It is now possible to create an archive of your whole mod (called “.oramod”). Installing it on other computers is then just a matter of placing that archive in the “mods” subdirectory of the Support folder.

The news post for the second playtest will detail what changes your mod needs to make it compatible with the upcoming release and to enable the .oramod packaging. All shipped mods have already been converted, so feel free to take a look at those.

In the future, OpenRA will feature an ingame mod browser that will allow you to search for and install mods directly from the Resource Center.

Dedicated server changes

Dedicated servers have been made a lot easier to operate for the next release.

$ ./OpenRA.Server.exe Game.Mod=ra Server.Name="My Server" Server.DisableSinglePlayer=true

[2016-04-02T16:06:10] Starting dedicated server for mod: ra

[2016-04-02T16:06:11] Master server communication established.

[2016-04-02T16:10:08] Antares has joined the game.

[2016-04-02T16:10:56] Player has joined the game.

[2016-04-02T16:11:49] Newbie has joined the game.

[2016-04-02T16:12:16] Antares changed the map to Doughnut.

[2016-04-02T16:13:41] Game started

[2016-04-02T16:37:38] Player has disconnected.

[2016-04-02T16:37:47] Antares has disconnected.

[2016-04-02T16:37:54] Newbie has disconnected.

[2016-04-02T16:37:54] No one is playing, shutting down...

[2016-04-02T16:37:54] Starting a new server instance...

[2016-04-02T16:37:55] Master server communication established.



First and foremost, the biggest change is that dedicated servers no longer need to sync maps with the Resource Center. Especially when you were running multiple servers of different versions, this could quickly become a headache. Another advantage is that the distinction between synced and unsynced servers will go away. That’s right: maps uploaded to the Resource Center will be available immediately, on all servers, without any further action required.

Another change is that there is now a dedicated executable for dedicated servers, OpenRA.Server.exe (and a matching /usr/bin/openra-server on Linux). As a consequence, the old Server.Dedicated and Server.DedicatedLoop command-line arguments no longer exist. If you are using custom scripts to start your server instances, you will need to adapt them accordingly.

One last, unrelated change is that the Server.AllowBots flag has been removed in favor of a Server.DisableSinglePlayer flag, which will allow people to play with bots on servers, but only if there is more than one human player in the game. Server.DisableSinglePlayer defaults to false , so be sure to set it if desired.

So much for a general overview of the upcoming release. For a detailed list of changes, see the full changelog.

At this point we need to mention another thing. As many other open-source projects, we don’t have any clear idea how much our software is actually used. There is a huge discrepancy between the number of downloads (about 50,000 currently for the latest release) and the number of online players (60-75 players concurrently at peak times). In order to get a better idea of this, and also to help with steering the future direction of the project, we decided to add an anonymous, opt-out data gathering facility to OpenRA. When enabled, the game will send us your operating system and .NET framework version, supported OpenGL version of your graphics card, your language settings, as well as the current mod. As already mentioned, this data is sent to us anonymously, using a randomly generated ID. If you are still feeling uncomfortable with this, you can disable this functionality by unchecking the “Send System Information” checkbox in the advanced settings dialog.

With the help of the data gathered, we hope to be able to decide – amongst other things – when we can allow ourselves to drop Windows XP support, and also how much benefit there would be if OpenRA was translated to other languages, and if so, which languages should be prioritized.

You can find the installer for your operating system on our download page.

Thank you very much, and have fun!