Today marks a turning point in the development of The Riftbreaker Multiplayer. We are finally ready to start testing the networking aspect of the game with people outside our office. That means you - our players!

Starting today, we are going to periodically distribute access keys to The Riftbreaker Multiplayer Beta to volunteers. Let's be clear here - this is not a co-op test. Not yet. The build we're running for the purpose of this test is limited to pure necessities and only runs our deathmatch mode (you can read more about it here). We will use the data gathered during this test, along with your feedback, to improve the netcode of the game and avoid major issues once we move on to the real deal - co-op testing rounds.

For the purpose of clarity and transparency, we have started a semi-public forum on our Discord server devoted to multiplayer development only. Every member of www.discord.gg/exorstudios can see the forum, but only people with access to the Beta can send messages there. You can talk to us anywhere else on the server, but that place is for feedback and on-topic discussions only. By doing it this way, you can always check how the development is going and what we have managed to achieve so far. This also does not mean the end of our 'Co-Op When' articles - we will still summarize everything that's happening behind the scenes for you every couple of months.

If you are not a member of our Discord and would still like to know the details of this testing round, we've also got you covered. You can find the full contents of our onboarding message for our volunteer testers. This message includes most of the details about the test and the current state of the build. Reading it should answer most of your questions, but feel free to comment if something is unclear. It is the first time we're doing something like this and we want to improve anywhere it is possible.

Thank you for joining us in this stage of multiplayer development.

We reserve the right to contact only select participants.





Network play is a much different beast than single-player offline gaming. The number of variables goes up dramatically. Not only does the game and your PC matter but also the type of connection you’re on and your distance from the server. This is why we need help from as many of you as possible. Please read the following information carefully, as it will probably answer most of your questions.

The Riftbreaker Multiplayer Beta is our limited test platform on Steam. It is a hidden product that will unlock after entering our provided key. It is an entirely separate build of the game. You do not need to worry about keeping a backup copy of your files from The Riftbreaker single-player version - we keep all the data for the MP version in a separate folder. Game settings are also separated, so if you have any changes in your game's config, you will need to reapply them here.

The features of this build have been reduced to the bare minimum. Currently, it only allows you to play The Riftbreaker online in Deathmatch mode. Running the game in such a simple configuration will allow us to diagnose problems and issue fixes more quickly. This build does not allow you to play co-op (yet)!

This test aims to study the game’s behavior during online play and discover all the issues and bottlenecks. We will use the information gathered during this test to reduce the data transferred between the server and its clients. We want to find out in which areas we need to improve things and ensure that the game can handle all the different types of connections you might use to play.

This build of the game is highly experimental. It won’t receive thorough testing at all times. It may stop working altogether for lengthy periods. Please bear that in mind.

WHAT WE ARE LOOKING FOR

We do not need you to install software to log gameplay performance or errors. The game itself gives us quite enough information on that. However, if you encounter crashes (and there will be crashes, a lot of them), please send in the crash report, including your nickname and a detailed description of what you were doing at the moment the game crashed. It will help us a lot.

We are looking for your feedback on the technical front. We want to know when connections fail. We want to know how many times you managed to switch the map before the server gave up on you. We want you to test the various connection methods and test with your friends from around the world. Try to break the game in any way you like - that is our current focus.
Gathering general gameplay and balancing information from the online deathmatch mode IS NOT the intended purpose of this closed testing round.

CURRENTLY SUPPORTED ONLINE GAMEPLAY FEATURES

The gameplay of the deathmatch mode is very basic, and we do not plan on making any major adjustments to it. It is primarily a testing tool, not the intended way to play the game. We are aware of the various issues with this game mode, but we do not want to spend too much development time on improving it. You can tweak it yourselves via mods if you wish. We would love to hear any bug reports about gameplay features that are broken, don’t function as intended or behave in unexpected ways. That being said, we do not intend to expand the deathmatch gameplay feature set or spend much time on improving it’s balancing.

There are two main options in the Main Menu: Multiplayer and Mods. Clicking on Multiplayer allows you to either host or join a server.

When hosting a server, you can set up the following options:

• Warmup duration - how long the warmup at the beginning of each map is going to take
  
• Max player count - The maximum number of players allowed to join the server
  
• Max frag count - the number of kills a player has to reach in order to win the game and finish the round
  
• Time limit - The maximum amount of time the round can take
  
• Bot count - how many bots should join the game alongside real players. Bots count towards the maximum player limit. However - if a human player tries to join a full server where some of the players are bots, one of the bots will leave to make room for that player. Please note that the current bot implementation is very simplistic and doesn’t provide enjoyable gameplay. We use bots primarily to stress test the game. They are only slightly smarter than an average rock.
  
• You can select the starting map. We have three simple arena-type maps available at the moment. When players reach the time or frag limit, the map will rotate to the next one.
  
• Public server - If enabled, your server will be visible to everyone who has this version of the game. If disabled, people can join you only by using the Steam Friends list.
  
• Dedicated server - if enabled, the server will run in headless mode. This means you won’t see the game render any images. It will only handle game logic. Turns this option on if you want to use this PC only as a server, and you don’t intend to play on this computer. Hosting the game on a dedicated server machine should improve game performance and stability.

Clicking the Join Game option will take you to the server list screen, where you can see all game servers running at the moment. You can check the server name, current map, number of players, and your ping to that server. You can join any of the visible servers as long as there is room for you.

Clicking Mods will take you to the Mod Management Screen. Mods are very unlikely to be compatible with this game version, but you can still create your own mods and manage them here.

The game will likely receive updates frequently. To ensure you are on the latest version, restart the Steam client before you play. This forces Steam to check for new updates for games you have installed on your system.

You will experience a varying amount of latency while running the game. When running the server yourself, the game is going to run mostly fine, but the more players join the game, the worse it is going to get. This is something we are actively working on and it should improve is going to change drastically as we move from build to build.

WHAT IS ALLOWED…

• modding
  
• discussing the build in an open manner
  
• streaming - we only ask that you make it obvious that this is a very early closed testing build

…AND NOT ALLOWED

• sharing the build without our explicit permission - we want the number of testers to be limited because the beta build is not in a good enough state to be played by people who are not REALLY REALLY REALLY interested in the game - right now it’s probably only usable by our most hardcore players
  
• we don’t want to drown in too much feedback, but don’t worry, we will gradually expand the testing group

Let us know if you need any more information. We’re looking forward to getting all the useful feedback from you!
EXOR Studios

As we stated in our Halloween Update Patch Notes:

During this event, the Tropical and Volcanic Zones of Galatea 37 will be illuminated by a custom-made weather event, with orange haze and a smokey atmosphere, as if you were close to a fire. Delicate ash and ember particles complete the look of a burning planet. Your Energy Connectors will be replaced with skulls and bones. Basic lamps will be decorated with Jack-o-lanterns. Rift portals you place on the ground will change into magical cauldrons filled with a strange substance of an unknown origin. The basic floors will also get an overhaul as we apply a cobweb theme to them in true Halloween fashion.

All the changes that happen during this event are purely cosmetic and can be turned off at any time. Go to the options menu, select ‘gameplay’, and change the ‘seasonal events’ option to on or off, depending on your preference. You can even switch between them back and forth - the change applies in real time!

Please note that due to technical reasons and the way this event works, if you play in the Tropical Zone or the Volcanic Region biomes during Halloween, you will NOT see weather events other than 'smoke and ash Halloween special'. If you turn the seasonal event off, the custom weather effect can take up to 10 minutes to go away. Other than this, the event has no real effect on gameplay.

Enjoy the festivities!
EXOR Studios

If you missed any of our previous Co-Op updates, you can catch up on them here:

https://store.steampowered.com/news/app/780310/view/3381659291157676103
https://store.steampowered.com/news/app/780310/view/3701435238673426124?l=english
https://store.steampowered.com/news/app/780310/view/3657536564724315072?l=english
https://store.steampowered.com/news/app/780310/view/3657539010840327508



Opening bioanomalies is easier with two flamethrowers at the ready!

After the deathmatch mod came into existence, we decided to package it into a separate product and publish it as a hidden item on Steam for internal use only. This special build is stripped of all the single-player functionality and currently only supports the DM mod. We have been using it for the past few months to test connectivity. We decided to prepare a specialized build for two main reasons:

• A separate, much smaller build allows us to test, improve, and iterate on the new game versions much faster. It also ensures that all testers are on the same game version (mismatched versions happen more often than you think!)
  
• Removing the unnecessary elements lets us focus on networking and connectivity issues without the unnecessary overhead cost from the game’s content.

By removing the majority of the game’s logic flow, redundant Lua scripts, and tons of other data, we can focus on what is truly important for us at this moment - improving the online playing experience, and that comes by optimizing transfer rates.

When we first started running multiplayer tests, we brute-forced the game to transfer all the gameplay state data from the server to the client. As a result, our data transfer rates reached upwards of 25 megabytes per second. Many people don’t even have access to an internet connection quick enough to transfer that much data consistently. Yet, our first tests demanded the game to send, receive, unpack, and apply all changes to the client’s game world multiple times a second. It barely worked over the local area network. We had a long journey ahead of us.

Most of the work we described in our previous articles about co-op development aimed to reduce the amount of data transferred between the client and the server. With each iteration, we were sending less and less data through the network. The latency was still high, but less data caused the game to run at a tolerable level of performance for much longer, allowing us to collect more information about the problems we were facing. At this point, all our tests were conducted by running a Survival Mode mission with two or more players connected to the same server. Making the server run both the game logic and handle the networking simultaneously was a tall order, given how much happens in each second of The Riftbreaker’s gameplay.


That last blade bounce was totally calculated.

Many of the problems we faced while testing this way resulted from the clients desynchronizing from the server. At some point, the performance overhead for the server was too high to handle all the tasks, and the clients expecting a server update did not receive it in time, resulting in lags, disconnections, and crashes. If only there were a way of stripping the game to the bare minimum, allowing us to focus on fixing the connectivity issues first without worrying about all the overhead costs generated by the Survival Mode mission running in the background…

Enter Deathmatch. A small and simple map, a couple of basic weapons, friendly fire, and no enemy units. Running tests in this environment gave us more insight in a couple of weeks than trying to complete Survival missions in the months before. We could find problems and reach conclusions previously hidden from us underneath all the unnecessary data. Thus, we started conducting daily playtests in a variety of configurations. Sometimes, we ran a dedicated server on a PC with no other tasks. Other times, we used the listen server option to maximize the load on the host PC. Profiling all our game sessions gave our team much insight into what was happening.


Sometimes it is complete, non-stop mayhem.

Using the data gathered during our playtests allowed the programmers to introduce the necessary changes. We started a lengthy back-and-forth process, where they would push a new build to the rest of the team and ask for a playtest while keeping watch on the network stats and ongoing threads. We kept on carving off chunks of data that were not necessary to be transferred. Bit by bit, month by month, hard work started showing its effects. Looking back at the start of the multiplayer refactoring process, we managed to reduce the data transfer rate from 25 megabytes per second to 200 kilobytes per second per client. This is still far from our target (10 to 20 kilobytes would be best), but it is a significant victory overall. The DM build helped us a lot in speeding up our iteration time. Best of all, the work we've done using the PVP build is transferable to the main project.

After we published our article about the PVP mode, many feared we would neglect the Co-Op mode. We want to assure you that this is not the case. Thanks to separating the PVP-only build from the main branch of the game, we built a perfect network testing sandbox for the most basic feature set on online gameplay. It doesn’t include any bells and whistles, just the essential game elements running unobstructed - precisely what we need to focus on the basic feature set.


The significant optimization of the data transfer we described in the previous chapter allowed us to start moving towards playing The Riftbreaker PvP on a PC outside the office network for the first time. To make that dream a reality without a VPN, we needed to add some features first. The list was as follows:

Host game screen with several options:

• The option to run a dedicated server (in headless mode - the host PC does not render the game)
  
• The option to run the game in listen server mode (the server PC also renders the game and allows its owner to play)
  
• Map selector list
  
• Basic game options, such as frag and time limit for any given map

Join game screen:

• Public server browser, listing the server’s name, latency, map name, and player count
  
• Refresh button, forcing the game to retrieve the public server list ahead of a scheduled update
  
• The option to join any public server.

Looking at this list, we realized that The Riftbreaker’s main menu will not be able to accommodate all these options in its current form. Therefore, we reworked the main menu layout to separate the single and multiplayer options from each other in their own submenus (it was already quite dated and cramped, so the facelift was much needed anyway). The layout we’re currently testing looks like this (please bear in mind that it’s not final and will likely change before the public release):


The options included in the current version of the main menu are still quite limited, but given our experience with bloat from earlier, we decided to focus on the bare essentials for now.

The server browser uses the Steam Data Relay Network. Despite the ‘Steam’ name prefix, this library is not limited to the Valve platform only. It can be used to establish connections between players on different platforms without any issues. However, to make things easier for us and take it one step at a time, we limit ourselves to playing with Steam for the time being. Any team member can set up a server with just a few clicks, which will become visible to everyone on the same game version. Then, it’s just a matter of clicking ‘join’ and we’re in the game.


The bots are quite bad, to be honest, but they still get the upper hand on us sometimes!

Not all of us are always available to test how the game behaves during online play. Our jobs generally need us to be focused on things for long periods. Sometimes, it’s challenging to get into that rhythm. Drawing someone away from their current task for a test can significantly disrupt their workflow. As a partial solution to this issue, we programmed very simple bots. VERY simple bots. They know the player’s positioning at all times and simply run forward, shooting as often as possible, as long as they have the ammo. They are useless as opponents but give us the ability to run basic tests with no involvement of more people around the office. Their development took only a few days, which we will quickly get back at a profit, considering our team’s time. With the help of our bot army, we can quickly populate our servers and run automated tests of game rules. As a bonus, whenever a real player wants to join the game, one of the bots is kicked out to make room for that player, so it is still possible to call someone in for help in case you need them.

It’s worth noting that none of this work will be discarded later when we move to more advanced testing. The main menu rework, the server list, game hosting, and joining servers - all these elements are essential, and we would have to make these happen either way. Completing these tasks also allowed us to make our tests more structured and semi-automated.



We've taken these stats from a session hosted by a friend hundreds of kilometers away. Worked pretty well and consistently!

With the new functionality in place, we could finally keep tabs on the multiplayer build. We came up with a set of tests to help us catch bugs and measure the performance of the game. We’d love to tell you that every build that leaves the hands of programmers goes through rigorous testing, but we never lie to you - this is just a set of guidelines. However, we have a short list of basic multiplayer functionality that we try to ensure is operational. The list is as follows (in no particular order):

• Is it possible to name your server using the game’s menu?
  
• Is it possible to name your server using the configuration files?
  
• Does the server name show up correctly on other PCs?
  
• Does setting the warmup time limit work as intended?
  
• Does setting the frag limit work as intended?
  
• Does setting the time limit work as intended?
  
• Does setting the player limit work as intended? Can it be set to zero?
  
• Does the max bot count setting work properly?
  
• What happens if you set all the game rule value sliders to zero?
  
• Does the server keep the settings after loading another map?
  
• Do all the settings work both in the listen server and dedicated server mode?
  
• Can you use the Steam friends list to join the game? Does it break if the friend you’re joining is in the menu, loading the game, their avatar is dead, etc?
  
• Does the server browser display server names or IP addresses?
  
• Does the server browser display the actual number of players on the server?
  
• Does the server browser work with both dedicated and listen servers?
  
• Does the refresh button work correctly?
  
• Does the server browser refresh automatically?
  
• Does the game work as intended when a player joins a game session filled with bots?
  
• Can players still join the server when the maximum player limit is met?
  
• Can you set up a listen server on an external network and connect to it from the office?
  
• Can you set up a dedicated server on an external network and connect to it from the office?
  
• Can you set up a dedicated server on our internal network and connect to it from the outside?
  
• Can you set up a listen server on our internal network and connect to it from the outside?
  
• Can you see all running servers in the server browser menu in all the cases above?
  
• Can you use the ‘Join Friend’ feature in all the cases above?

This list is non-exhaustive. Our testing is often focused on the areas under active development. For example, we’ve recently been trying to figure out how to fix the problem that causes the player to lose weapons permanently on death. It is made worse by the fact that the problem persists when switching maps (on the other hand, it means you won’t lose your inventory during planetary travel in co-op, yay!) Naturally, we will pay more attention to the details surrounding our current area of interest, but keeping track of the basic functionality is paramount. Testing all these things will likely continue way beyond the final release.



Clone wars, Riftbreaker style. Note that the game wasn't running too well during this run.

We still have a lot of work regarding optimizing the data transfer. As mentioned before, we ideally want to get the amount of incoming data down to about 10-20 kilobytes per second per player. We have already greatly reduced the amount of data transferred between the PCs during gameplay. However, we still generate more information than necessary. That is because we have not yet reworked all the in-game systems for multiplayer context. On the other hand, it gives us a couple of clear targets where we are sure to find performance gains.

Special effects are one of the significant areas of the game that still require a rework. More specifically - separating the audiovisual representation of the effects taking place in-game from the logic underneath them. We mentioned it in more detail in the first Co-Op Update article if you want to know more. Here’s the TL;DR: Currently, game logic runs exclusively on the server. For example, if a player shoots a gun, all effects happen on the server first and are then “copied” to clients. Instead of doing the same work twice, the server can command the client to spawn the effects on their end, reducing the overhead for the server. It sounds simple, but it is a monumental task, and its development is an ongoing process, as we need to rework all systems in the game to accommodate that.

In a similar vein, we are reworking the game logic so that not all of it has to be carried out on the server first. Some more minor game logic elements can be handled by the clients and later only verified by the server. However, introducing changes to how game logic unfolds carries huge implications for saving files. We still maintain backward compatibility with all (unmodded) game versions, going back to version 1.0 (PC players did not even have the chance to download it! Version 1.0 only exists in the physical disc console versions of the game. To run it, you need to have no internet connection for the entire gameplay duration. Still - it is officially supported). Even though the number of users that play such old game versions is minimal, we maintain save file compatibility as a rule.

With such a huge rework, touching almost all aspects of the game, you will find a lot of issues, even in the most unexpected places. Music is the best example - what could be so difficult about playing an .ogg file? The problem is that The Riftbreaker features an adaptive music system. When a player is fighting, the music changes to a ‘combat’ playlist. When you’re building the base, we use the ‘building’ playlist. We want to keep that feature for each player individually. However, there are certain moments in the game when the game’s logic forces a certain type of music to be played - during the final attack, for example. We want the server to be able to overrule the clients in this case, which requires reprogramming the system to work in a more complex client/server architecture. This is only one of dozens of problems we encounter, each needing a different treatment.

We discovered many issues when we started running our connection testing gauntlet. The high number of possible ways to connect to a game session and other variables, like the type of network your PC is connected to, cause numerous problems. Sometimes, they become apparent immediately, while others remain hidden for weeks. We carefully examine the causes of these issues on a case-by-case basis. We can’t possibly catch all mistakes on our own - which is also why we want to test the multiplayer portion with you.


Ragequit is one of our moderators and modders of The Riftbreaker. He immediately started modding the multiplayer build. We are not surprised at this point.

Starting this week, we have been allowing access to the multiplayer build of The Riftbreaker to people outside EXOR. Those players are handed keys to the hidden Steam product and are welcome to test the game with us and host their own sessions. This is a major milestone we are very proud of, and we hope that you will join us! The invitations will be handed out via Discord, so if you have not joined www.discord.gg/exorstudios - now is the best time to do so. The deathmatch test will eventually evolve into the real deal - a Co-Op beta test, which makes it even more exciting. We can’t wait!


The basic deathmatch gameplay loop, coupled with the essential interface features for hosting and joining the game, gives us an excellent tool for testing network performance. It has already yielded great results, and we expect it to improve. That said, we don’t want to develop this game mode any further. Any updates we introduce will only be aimed at making the game run better. We plan to invite selected Discord members to test the game with us, slowly opening the Deathmatch demo to more and more people. However, Co-Op remains our primary focus.

We never promised a release date since we knew the development process would be very long. Nobody could predict how long. Yet, you’re here with us, reading the articles, following the latest developments, and sharing your feedback. We would like to express our enormous gratitude for your support and patience. You will be rewarded with the best multiplayer experience we can offer - that’s the only thing we can guarantee.

In the meantime, we’re going back to work. The programmers - back to unspaghettifying The Schmetterling Engine’s code. The designers - to creating a new part of the adventure in the coming World Expansion III. We hope you’ll come on both of these adventures together with us. Join our Discord at www.discord.gg/exorstudios and watch us stream twice a week at www.twitch.tv/exorstudios.

Thank you once again!
EXOR Studios

We have just published a small update for the game, including some new elements and changes necessary for the upcoming Halloween seasonal event. The update also includes a couple of fixes for minor bugs - all of them are listed below.



With this update, the game now supports the new Halloween seasonal event. If you have been with us for a long time, you might remember the Halloween event we held long ago. At that time, we added a couple of decorative buildings - pumpkin lamps and tombstones for walls. However, we did not have the tech to replace those buildings in real time. The event never got the final touch necessary to make it public-worthy, so we shelved it. In the meantime, we produced Winter Holiday-themed and Lunar New Year events. With this experience, we revamped the Halloween event a little.



The new Halloween event is going to be active between October 26th and November 10th. During that time, the Tropical and Volcanic Zones of Galatea 37 will be illuminated by a custom-made weather event, with orange haze and a smokey atmosphere, as if you were close to a fire. Delicate ash and ember particles complete the look of a burning planet. Your Energy Connectors will be replaced with skulls and bones. Basic lamps will be decorated with Jack-o-lanterns. Rift portals you place on the ground will change into magical cauldrons filled with a strange substance of an unknown origin. The basic floors will also get an overhaul as we apply a cobweb theme to them in true Halloween fashion.



All the changes that happen during this event are purely cosmetic and can be turned off at any time. Simply go to the options menu, select ‘gameplay’, and change the ‘seasonal events’ option to on or off, depending on your preference. You can even switch between them back and forth - the change applies in real time!



Last but not least, here’s the full changelog for this update:

• Fixed a bug in one of the attack waves in Volcanic Area survival that caused an unreasonable amount of Magmoths to attack the player's base at a certain point in the game on higher difficulty levels.
  
• Updated the Prologue mission. Unit placement has been improved, a couple of bugs have been fixed, and the lighting has been changed to make use of the volumetric effects.
  
• Fixed a bug with Arachnoid Sentinels not setting their aggro distance properly when spawned randomly by the map generator.
  
• Fixed a bug that caused Artillery Towers to be unavailable in the Prologue mission. The adverse effect of this fix is that Artillery won't be available in custom-made biomes unless the modder manually updates the condition_value "magma,jungle,desert,acid,metallic,legacy_maps,prologue,swamp" with the name of their custom biome. This line can be found in the "buildings/defense/tower_artillery.ent" and all other artillery-related buildings. You can also ignore this for the time being, as we are working on a better, permanent fix.
  
• Halloween event items have been added. This seasonal event will be active between October 26th and November 10th. The event will add a special holiday weather event and replace some of the buildings and props with festive versions. The event is visual only, and it can be turned off at any time via the options menu.
  
• Time windows for other seasonal events have been set. The winter event will last from December 5th to 27th. The Lunar New Year event will last from January 20th, 2024, to February 5th, 2024.

EXOR Studios

Our game engine is the main focus of today's article. It is one of the reasons why we can throw THIS amount of enemies at you and not worry about the game blowing up.

The game development industry has recently gone through an earthquake of a cataclysmic magnitude. A major game engine provider recently announced changes to their pricing model, which caused an upset in the gamedev community. It left many studios wondering about how to proceed with their work in the future. Luckily, we were not affected by that since EXOR Studios’ games are made using our own engine - The Schmetterling. It is one of the advantages of working with your own technology. You are independent but, on the other hand, solely responsible for the state and features of the engine. Still - we enjoy working with our tech and decided to give you our personal view of the pros and cons of working with The Schmetterling.



The humble beginnings of The Schmetterling engine were captured in this making-of video for Zombie Driver.

When we started working on our first standalone project, Zombie Driver, back in 2008, we did not have the means to afford any of the ready-made solutions available on the market. We had no choice but to look for open-source solutions to make our first game a reality. Our plan was not to build an engine but to somehow piece the game together. In the process of Zombie Driver’s development, we learned what kind of tools work for us and which ones don’t quite make the cut. Over time, we started reducing the bloat of the software we were using and forming a semblance of what our engine is today. It was a naturally occurring process, and it shaped The Schmetterling engine to have all the necessary tools and features we need to make our own games in the isometric camera view. It was a set of answers to our needs at that time, which is one of the reasons why we have kept working with it ever since.


Destructible environment was one of the key features of X-Morph: Defense. We don't know if achieving this level of destruction would be possible for us in any other engine at that time.

As the tech in games evolved, The Schmetterling needed to keep up with the times and evolve as well. This is where the second advantage of the engine became apparent. Because we have the entire codebase for the engine and know it in and out, we can expand the engine with any kind of feature that we can develop within reasonable time. Whether it’s a new physics model, like in the case of X-Morph: Defense, or a new rendering technique, such as real-time raytraced shadows introduced in The Riftbreaker - if we want a new feature in our engine, it is only a matter of time and dedication before we get our hands on it. Our programmers get the experience of working with the new tech, and the designers can unleash their vision, not limited by artificial constraints.


The aforementioned "artistic vision not limited by artificial constraints." We're not quite normal.

Many of the features of our engine have been implemented with designers in mind - most files are human-readable and, as a result, can be edited by anyone with access to notepad. Thanks to how easy it is to create entities, prepare logic files, create scripts and edit databases, most developers in the studio can create entirely new game assets from scratch without ever asking programmers for help. This is also thanks to the simple Entity Component System, which works like a set of building blocks. Each component in this system adds a set of functions to a game entity. By picking and choosing the right components, we can give game assets the desired properties and have them function in-game as intended.


Tweaking sensitive values gets much easier when no baking is necessary. It allows us to fine-tune visual (or physical) effects much easier.

Another aspect of The Schmetterling engine that helps us with development is that there is no baking necessary and most assets, scripts and effects can be edited in real-time. Baking is the common name for the preprocessing of game assets. It is done to make sure that all assets load and function well and do not cause issues in-game. Since our assets are game-ready right away, we can skip this step, drastically reducing iteration time, as all our changes take effect immediately. This allows us to catch mistakes and test new solutions in a very quick manner.


Automated tests won't catch all bugs but they are a great help. We have a feeling this Gnerot will be back.

There is also a bunch of quality-of-life solutions within The Schmetterling that positively affect our workflow. Our automated crash reporter allows users to send us the data necessary to fix many errors with the game. The reporter also gives us basic stats on error occurrences, helping us prioritize the most common crashes. The engine also allows us to automate game tests and performance benchmarks. This helps us identify many issues before anyone has really had a chance to notice them in the first place. Our toolset is also very modular and easily expandable. If we’re missing any features or test setups, it is usually a matter of just a couple of days of work to add them.



You need to know what you're going for and how to achieve it. If something is possible within The Schmetterling, it's usually a matter of adding the proper components. But first, you need to know which ones will do the trick for you.

Naturally, The Schmetterling is not perfect. One of the most difficult aspects of working with the engine is the fact that there is no documentation available. You can’t refer to the manual for a list of the available features or examples of how to use them. We rely on the knowledge we gained working with the engine over the course of all these years. Programmers tell us about the new features they deliver, and designers often refer to their previous work as a makeshift ‘cheat sheet.’ However, for a person without access to any of that knowledge, the entry barrier is very high. Mastering the ways of the Schmetterling requires dedication and some reverse engineering.


When we were implementing raytraced shadows, we had to carve the path and figure out solutions to all the issues ourselves. At times, it was tough, but the end effect was well worth it.

Another thing worth mentioning is that nobody is coming to help if something is broken. You can’t count on an engine update magically being published by the developer because YOU are the developer. When there is a bug in the engine, you have to ask the person responsible for that part of the codebase to fix it for you. This can be seen both as an advantage and a disadvantage. On the one hand, you directly impact the state of the engine and can request a quick fix if you’ve encountered a critical error. However, it also means a lot of additional responsibility for our programmers, which they (probably) wouldn’t be dealing with had we chosen a ready-made solution.



The engine wasn't made with multiplayer in mind. Neither was the game. But it's not going to stop us.

Now, we come to the worst part of working with our engine: it is well optimized for the games that we make. It’s not well-suited for anything else. We have all the tools and features necessary to make single-player games in isometric view. However, if we want to achieve something beyond that scope, we must devote long hours of research and development to build the new features from scratch. This is, unfortunately, why developing online co-op is taking so long. We have to essentially build the entire engine for the multiplayer version of the game from the ground up. While this is probably the most hardcore task we could have taken on, we would face similar challenges if we wanted to introduce other drastic changes to the engine and move the camera to the first-person view, for example.


Testing network play on a small PvP map allows us to progress with the work on the multiplayer portion of the game much faster.

Knowing our situation, we knew going into this that adding co-op mode to The Riftbreaker would be a monumental task. Still, we want to assure you once more that we are indeed working on it. We read all your comments. We know you’re frustrated and angry that you’ve been waiting so long. However, rushing things is not the answer here. In order to develop a good multiplayer mode, we need to make sure all the engine work with each other well. A lot of manhours have gone into assuring that we won’t have problems down the line. There is no going around these things, and the unfortunate thing about that is that more often than not, we do not have much to show our progress.


The next progress report will focus on the network connections and the issues we faced while working on the multiplayer.

We hope that we can give you something playable sooner rather than later. We hope that we can meet your expectations. But until then, we need to ask for your patience. We will publish a full-length Co-Op Progress article in the coming weeks. Stay tuned for that.

If you missed any of our previous co-op progress updates, you can catch up here:

https://store.steampowered.com/news/app/780310/view/3381659291157676103
https://store.steampowered.com/news/app/780310/view/3701435238673426124?l=english
https://store.steampowered.com/news/app/780310/view/3657536564724315072?l=english



The Schmetterling is not very universal, but it's VERY good for our use cases.

Developing our own engine has had a lot of benefits for us. It has given our developers lots of invaluable knowledge. We have benefitted from The Schmetterling’s flexibility and adaptability multiple times. However, maintaining and expanding the engine has been an additional, significant responsibility for our team - a responsibility that does not always show obvious benefits and can get frustrating at times.

There is a lot of craftsmanship involved in working with a custom engine. If we were to use an analogy, it is a bit like brewing your own beer. You can learn all the theory, pick your style and ingredients, and control the entire process. On the other hand, you can go to the supermarket and pick up a bottle of your favorite brand. Both will hit just as good as you wind down after a hard work day, but you won’t feel the extra satisfaction of enjoying the fruit of your work from start to finish.

The bottom line is that there are no silver bullets. Each engine has its strengths and weaknesses. Whether it’s a ready-made solution or a custom-built engine, you will have to face some issues along the way. The most important thing is to make an informed decision in the first place. In our case, we’re glad we have The Schmetterling and don’t think we will switch anytime soon.

EXOR Studios

The development of the third World Expansion for The Riftbreaker is well underway. We stream our progress previews on Twitch from time to time, testing the new survival mode setup and the basics of the new biome’s gameplay - follow www.twitch.tv/exorstudios to catch us live! As you know from one of our previous articles, the development of an update or an expansion is a lengthy process. It’s full of trial and error and involves a lot of iterations over various elements we want to include in the game. Today, we would like to tell you what it looks like in the case of 3D graphics. We will take a look at a couple of new creature models, what they looked like initially, why they were rejected, and what kind of improvements our artists made to make them viable. Today we’re looking at the technical side of things only - these cute little creatures will get a proper introductory article when the time is right. With all that out of the way - let’s see what the process looks like.


Some of the new creatures are quite menacing, but aren't aggressive.

Please note that there is much more to creating new creatures than we can cover with just one article. After designing and modeling the creature, we need to create textures, animation rig, create animations themselves and program the unit’s behavior that will make use of those animations. After that, we add a whole bunch of effects. All blood splats, projectiles, and any other visuals produced by the creature are custom-made for that unit. Same goes for sound effects - they are all created on a per-unit basis. Then, after all the technicalities are done, we can finally playtest the game including the new unit, tweak its behavior and balance it in the context of gameplay as a whole. This article will only cover the process of getting from the concept phase to the final, high-poly model.


...unless you come too close for their comfort.

The work starts with the concept. During the pre-production phase, after we have decided on the general theme of the new biome, we run a series of design meetings where we come up with ideas for the fauna and flora you’re going to find in the area. While plants and other props are designed to support the general theme and serve as decoration, creatures need to fit both thematically and functionally. We gather tons of references, looking at our favorite works of science fiction, other games, and all other media that could be even remotely relevant to the theme of the biome. We come up with several designs and decide what kind of units we need for the new area when it comes to function. We usually need a light ground unit to appear in large numbers, a medium-sized ranged unit, a tank, and a couple of special units with unique mechanics. Our designs for the large tank and the small cannon-fodder came first.


Stickrids are so delicate you can just stomp them.

Fungor is the first of them. The initial design for the creature was to make a tall, menacing hybrid of an animal with a mushroom. Fungor’s design is supposed to make you ask yourself ‘what is going on here?’, as the creature tries to rip the mecha-suit apart and consume you with its giant jaws. Our artists came up with several propositions, trying to solve the issues of Fungor’s proportions, anatomy, movement, and attack mechanics. These are the first concepts they came up with.



Ahhh, sweet man-made horrors beyond comprehension. Everything immediately fell into place after these concepts were presented to the team. We chose elements that we liked from each version. What we wanted was a fungal abomination that moves in an upright position using massive tentacles. We also decided to add another tentacle to the back of the creature that it can use as a weird whip/hammer hybrid. With these assumptions, the artists got back to work. A couple of days later we got this beauty:


Fungor in its ‘rigging pose’ - all the appendages are extended as far as they go and add the animation rig to the model. Essentially, Fungor is T-posing here.



Designing Fungor was rather straightforward. There was no need to go back and do a couple of redesigns - when a clear vision clicked in our heads, it was only a matter of time before our art team could make it a reality. The scale, anatomy and form all match the desired function of the creature. However, things do not always go so smoothly. This little guy is called a Stickrid:



Hey, this is a Stickrid, too…



And this one as well…


The notes next to the arrow say: [top] the tail fin is helpful when living in a swamp. and [lower, next to the hand] fangs so that the creature can climb.

Here, we got three wildly different concepts. After some discussions and looking deep into the beautiful googly eyes of number 1 and number 3, we decided that number 2 was the only one we wanted to kill. However, number 2 had its fair share of problems. First of all - it resembled a spider a little bit too much and we are aware that not everyone would jam with this idea. Second - the spider-like anatomy meant that the creature’s body would be very low to the ground. In the case of the swamp biome, that’s not really what we wanted, as the critter would not be visible to the player most of the time. We decided to merge some ideas from number 1 and number 2 into one model and lengthen the legs. This way the creature would resemble a grasshopper more and its body would stick over the surface of the water.


Stickrids' design allows us to place them directly in bodies of water.

Another thing is the creature’s function. Even though it falls into the ‘cannon fodder’ category - it’s small and always comes at the player in relatively large numbers - it is different from the other small creatures in the game. Instead of melee attacks, Stickrid prefers ranged combat. It will run away from its target to a safe distance and try to take it down with a barrage of small projectiles. If you try to come closer, the creatures will scatter around, trying to keep their distance from you. This feature means that the creature needs to look like it’s able to launch projectiles. Unfortunately, this eliminates the cute number 3. Goodbye, Frogozaurus Rex.



This was the first attempt at merging the first two concepts. The legs have changed significantly, but we were still not very happy with the overall body shape. We decided that the abdomen, also known professionally as the ‘spider butt’ should be slimmed down. We thought that the creature would look beter in a ‘cigar’ shape.



After all of these changes we arrived at this concept. All our goals have been met:

1. It has an elongated body and no longer resembles a spider
   
2. Long legs ensure that the creature will not hide beneath the surface of the swamp
   
3. The gaping mouth is ready to shoot projectiles at you and your base
   
4. It’s not cute anymore and we have no problems killing it.

All that’s left is to add some detail and final polish to the model. Here’s the final version:



If you compare the last two versions of the Stickrid we presented, you will easily see the difference between the sketch and the final hi-poly model. When going for the ‘final quality’ model, artists pay a lot more attention to the anatomical details of the creatures they model. The legs have been beefed up, and their joints have been moved slightly to make the model more lifelike. The legs themselves no longer stick out of the abdomen. Now, both these elements flow naturally from one to another. Stickrid’s body has also become more compact, ensuring it behaves as intended in large groups, which is the intended use case. Apart from these touch-ups, the creature also received a lot more details. Ribbed carapace, sharp feet, and striped antennae on the head - we have to skip all these things when coming up with low-poly concepts.


One Stickrid is not that threatening...

Artists at EXOR have complete freedom when choosing references and style for their models. The design team only gives them broad descriptions of what kind of creature they think will work well gameplay-wise. Everything else is up to the artist. Our way of creating game art is not for everyone. Some people prefer to make models based on concept art, since that more-or-less guarantees that nothing they create goes unused. However, we believe that when artists can interpret the creature description freely and create something from the ground up is our strength. It always leads to interesting results and gives them a chance to put a personal touch on their work.


...but there is never just one!

So there we have it - an overview of the first steps that our models take, from the humble beginnings to the final hi-poly model. Let us know if you would like to hear about all the other stages of creature development - texturing, animations, particles, sounds, and everything else! We’ll gladly share more info on this. Remember to join our Discord at www.discord.gg/exorstudios for more news and daily changelogs. Also join our streams at www.twitch.tv/exorstudios - we haven’t streamed our co-op progress for a while, so it might happen soon…

See you next time!
EXOR Studios

Last week, we showed you what our organization of work looks like when it comes to larger-scale projects, like expansions or major patches. It takes hundreds of hours of work from individual people to eventually create something that is much more than just a sum of its elements. Today, we would like to tell you what kind of tools and technologies we use daily to make our jobs a) possible and b) easier. Some of the tools we use are quite specialized and unpopular. Others - you might very well have them installed on your PC. Let’s take a closer look, going from team to team.



Blender. Throughout this article, you will see what we're working on at the moment. Pay attention to details!

Blender - This open-source 3D modeling software is the bread and butter of the graphics department at EXOR Studios. The vast majority of the hard-surface objects are modeled in this program. It is used for all stages of asset production, from basic sketches through detailed high-poly models to simplified low-poly versions ready for use in-game. We make animations in Blender as well! Thanks to Blender’s open nature and plugin-based expandability, our designers always have the freedom to look for new tools and add-ons to help them with their work. The best part is that the software is completely free, and with a large number of courses available online, anyone can learn it and start their journey with graphics design!


Zbrush. New creatures are coming to life right as you're reading this!

Zbrush - As good as Blender is, it is not perfect for all tasks. When it comes to modeling organics, such as creatures or plants, Zbrush is the tool of choice for our team. This program allows the artists to sculpt models with fine details as if they were working with a real-life material such as clay. Using a range of virtual brushes, our designers can intuitively create lifelike models with relative ease.


Substance Painter is where all models get their colors. And materials. And basically, everything else that makes them not look like an unpainted Warhammer mini.

Substance Painter and Designer - We use Painter to create textures for our models. It allows our artists to create highly detailed textures using a range of smart tools. It simplifies the texturing process by automatically wrapping the model and allowing the artist to observe the effects of their work in real-time. Designer, on the other hand, allows us to create materials for our in-game models using procedural generation.


Photoshop. Layers, keyboard shortcuts, 20 gigs of RAM usage. Photoshop in a nutshell.

Photoshop - When it comes to creating 2D graphics, nothing beats good old Photoshop. Apart from the more obvious use cases, such as creating concept art and loading screen art, we also use Photoshop to create the elements of the Graphical User Interface, or GUI. All buttons, frames, and menus have started their lives in Photoshop. They are later cut into individual elements for the engine to use across all the different screens in the game.


After Effects. Even the animations you can see in the game's main menu were born in After Effects.

After Effects - the layered 2D graphics created using Photoshop can also be used to create basic animations. By applying simple movements to some elements of the artwork made by our team, additional particle effects, and a dash of post-processing, we can prepare in-game animatics on our own. Of course, they may not be as spectacular as fully-rendered 3D movies, but they serve the purpose of conveying story elements quite well. Additionally, we can make changes to them quickly and avoid the need to rent costly render-farm hardware.





Visual Studio and Visual Studios Code. For non-programmers out there: spot 5 differences.

Visual Studio and Visual Studio Code - our programmers’ weapons of choice. The Riftbreaker’s game and engine code is written using C++. Our Programmers use Visual Studio as their development environment and debugger. However, the code is only a part of the game and works in tandem with the game’s content. This is where Visual Studio Code comes in. Our programmers use it to navigate the game’s scripts and content. It also gives us a LUA debugger that we can attach to the game’s process. Additionally, there is a number of different shader languages (depending on the platform), various tools written in Python, Powershell, C#, or whatever new tech the programming team finds useful at the time.


SVN keeps track of all changes ever made to a file. You can't hide your mistakes, even if you really want to!

SVN - A free and open content versioning system that can be integrated with the Windows interface through e.g. TortoiseSVN. It allows us to distribute the working copy of the game to all developers in the studio, keep track of changes made by each user, and fall back to any revision of The Riftbreaker in the history of the project. It serves both as a tool for organizing our work, as well as one of our many backups.


TeamCity. This list goes on and on, as we have multiple configurations for all platforms and all our games there.

TeamCity - This piece of software allows us to automate a lot of things around the office. It directly controls our four dedicated build machines - the main job of these computers is to compile game code quickly. TeamCity maintains the building queue, distributes tasks between the build machines, as well as helps us automate some tedious tasks, like deploying new game builds to the repository, running benchmarks, and automated game tests.



REAPER. After a little while you stop seeing weird shapes and start seeing sounds. Is this synesthesia?

REAPER - We choose to work with this Digital Audio Workstation because it is simple, robust and lightweight. Its functionality can easily be expanded with VST plugins, as well as plenty of free JavaScript addons created by users. REAPER offers a huge amount of customization and has never let us down in our day-to-day work. We use it mostly for working with dialogues - cutting long recordings into samples, and applying post-processing effects. You can read more about how we work with audio here.



Notepad++. You can edit the majority of the game's files in this program. Very much recommended.

Notepad++ - the #1 most popular computer program in EXOR Studios. Used for editing LUA scripts, editing entity files, and, of course - taking notes. It has a multitude of features that help us with our daily jobs, such as finding all instances of a phrase in multiple files at once, the ability to open many text files in several tabs, and saving your work regardless of not clicking the ‘save’ button yourself. Much recommended.


Paint dot net. Photoshop for people without talent or skills. Or both!

paint [dot] net - For those of us who do not need or can’t use Photoshop, paint [dot] net is a sufficient alternative. The programmers and designers use it to quickly edit textures and mark them as temporary - something that is often needed when creating prototypes of new game features. It has a simple interface and offers just a bit more functionality than regular Paint, with layers and transparency support, for example. Also - sorry for the weird spelling. Steam recognized the name of this program as a link, and the link did not lead anywhere we would want to lead you.

Paint - the most legendary and classic tool available. Used by those who can’t grasp the complexities of paint [dot] net (wait, what!?). You might think this is a joke, but it was even used to create EPIC cutscene mockups:

You know what? EPIC doesn't even cut it for this video.

The Riftbreaker World Editor Suite - last but not least important. All the props, creatures, items, and all the other game pieces that we create using the tools mentioned above are put together into one using our editors. We use the map editor to create map tiles for all the game’s biomes. The model editor allows us to attach particle effects to models and add events to specific points in the animations of those models. The Riftbreaker Editor gives us access to all the databases of the game - loot tables, damage values, and many others. Mission Editor allows us to create campaigns, missions and in-game events using a simple, block-based setup. These programs, combined with some of the ones we mentioned earlier, give you everything you need to create great mods for The Riftbreaker.

You can read about these tools here:
https://store.steampowered.com/news/app/780310/view/3109170041988719336?l=english

That’s probably not all the individual pieces of software we use daily, but we have certainly covered the most important ones. Are you surprised by some of our choices? Did you expect to see something different? Or perhaps there are some omissions that you’d like to ask us about? et us know here in the comments! You can also get in touch with us on our Discord at www.discord.gg/exorstudios - we’re always happy to share our insights!

See you soon!
EXOR Studios

One of the goals of the articles we share with you every week is to bridge the gap between us, the developers, and you, our community. We love showing you what goes into making new features a reality and explaining why we do certain things. Today, instead of taking a detailed look at one feature (like last week’s article about Volumetric Lighting, which you should totally read), we are going to take a step back and show you what the production process looks like for The Riftbreaker when it comes to larger pieces of content. Here’s the story of how Into the Dark came to be.



Fun Fact #1: The promo art for this biome featuring Drilgor arrived when we were quite deep into the development process, when we had the creature's appearance finalized.

After we finished work on the Metal Terror expansion, we gave our design team a task to come up with several concepts of new biomes for Galatea 37. We didn’t want these designs to be too specific. Instead, we asked for a general overview of the look and feel these biomes could have - the color palette, types of props we could expect there, and some ideas for plants and creatures that would inhabit the biome. Designers compiled all that info in the form of a presentation for each biome concept that all members of EXOR could read and form an opinion. Then, we held a vote to see which ideas resonated with us best. Crystal Caverns dominated the vote, and we got to work.



Fun fact #2: the first destructible rocks were reused props from the Metallic Valley biome.

The first thing that came to our minds when brainstorming ideas for this biome was digging tunnels. We had no plans for such a feature before this, but it seemed interesting enough to try out. One of our programmers, Łukasz, decided to make a quick prototype of the feature. He took a couple of regular rocks that the artists made for other biomes and allowed the player to destroy those rocks with regular weapons. This solution was far from optimal and didn’t feel great just yet, but the potential was there. We decided to greenlight this feature and make it a key point of this biome.

We began iterating on the digging mechanics, moving away from using weapons to carve your way through the limestone (leaving it only as an option) in favor of using Mr. Riggs’ drilling arm. It quickly became apparent that filling the map with thousands of physical, destructible elements was a performance nightmare for our engine. The programmers decided to drastically reduce the number of destructibles by only spawning the rocks that the players could interact with - essentially, just the edges of the removable masses of limestone. The empty space behind the face of the wall would be covered with a texture that gives you the impression that you’re facing a solid wall. Sounds quite simple, but we kept tweaking this aspect of the game until release. You can read more about it here.



Survival gameplay is never an afterthought - in fact, we have survival ready before the campaign starts to take shape.

Simultaneously, we started designing the flora and fauna of the Crystal Caverns. Given that creatures living underground often take weird and, frankly, disgusting forms, we took some liberties when it came to the design of their appearance and abilities. The goal was to make them eerie and almost unnatural. So, we got Crawlogs who can traverse walls and ceilings and come back from the dead. Gulgors spit shards of razor-sharp crystals. Crystaroses siege your defenses with incredible efficiency. However, there was a problem - if the map was filled with rocks the player had to dig through, how would the creatures get to your base? We created Drilgor to solve this problem. This monstrous creature has just one purpose - it will find the shortest path to your base and dig a tunnel for other creatures to follow.


Even playing with a limited and prototypical creature set can give us valuable insight into what we want the biome to look like.

This set of creatures, along with the cave-digging mechanics, gave us just enough elements to set up a simple survival mode setting that would serve as the base of the gameplay moving forward. The level designers created a couple of test map tiles using props from the other biomes in the game. This allowed us to get a feeling of what the gameplay would look like with the cave-digging mechanic. We also realized what kind of problems players would face, energy production being the main one. Before we started introducing new elements, we decided to start doing preview streams to gather some initial feedback from the community.


At this stage we also learn how to build new map tiles.

One example of a lesson learned from this early gameplay prototype was the need to handle attack waves in a different manner than we’re used to. Since there were few solid obstacles in Crystal Caverns, players would have problems setting up proper defenses, as they did not know where to put up walls and limit the expansion of their bases. We solved that by letting them know where the attack would come from ahead of time. Thanks to this early bit of information, they knew which parts of the base they should focus on and prepare for the incoming attack.



There's always going to be a massive battle at some point during the campaign. The big question is - how do we get there?

With some conclusions from the survival playtesting, the campaign started to take shape. The initial draft is always written in paper form (not really; we use a doc for that, but you get the idea). The campaign designer comes up with a number of missions, their objectives, and how they are connected with each other. Only after the paper design is approved we move on to work on it in-game. We always start by creating a ‘skeleton’ - a series of very simple missions you can progress through in a few minutes. We mean REALLY simple: go to point A, go to the next map. Load into the next map, wait 30 seconds, and go to the next map. This logic structure is a foundation we can later fill with actual content.


We design and test various objectives. The ones that are potentially problematic are discarded to make place for better ones.

Naturally, it’s not as straightforward as we might like. As the missions take shape, we often discover that we lack the necessary logic blocks in the engine or other features that require help from the programmers. It must be noted, however, that we try to bother them as little as possible not to drag them away from their work on co-op, which runs parallel to the content creation. We also often work with placeholder assets while we’re waiting for the graphics team to finish the final models or animations. This is also the part when the story starts to take shape. There is no denying that The Riftbreaker does not rely on a strong narrative to drive players forward. However, we still like our story to be coherent and sensible. Iterating on the story often involves recording placeholder dialogues multiple times, which can sometimes be pretty funny.



Some new tech items have to wait for the proper treatment a little longer than others. Here you can see the Acid Spewer Towers in their final form. However, the traps around the base are just recolored Acid traps.

While the campaign is being developed, another part of our team starts working on all the tech items that we want to include with the expansion. As usual, we try to build working prototypes with the elements we already have in the game. We build new weapons using the existing meshes, sounds, and particle effects. The same applies to buildings. We do all this prototyping work to check whether the new tech we’re planning makes sense and if it’s fun gameplay-wise. That’s the thing with designing things on paper - sometimes things might sound good at first but turn out to be complete duds when it comes to playing with them. Testing things early allows us to correct our mistakes before investing precious production hours into something unusable.


Fun Fact #3: Drilgor had a bug that rendered it unable to hit more than one target at a time. It became a killing machine that wrecks your walls only after it was described as 'weak' in playtesting.

We tend to create way more prototypes than the final number of technology items that actually end up in the final release version. There are two main reasons for that. The first is time - we simply do not have enough time to implement everything we want properly. Items that did not receive the final polish are archived so that we can try to use them again when an opportunity arises. The second reason that new items are cut is that they do not feel right or do not fare well in gameplay of the new biome. Then, they will simply have to wait for a more opportune moment.



Fun Fact #4: The 'Brittle' achievement used to be possible only with Level 1 Crystal Walls. Luckily, we caught that pretty quickly.

Needless to say, testing is a huge part of the development process, and it’s not a “one and done” deal. Neither is it a one-person job. All developers report problems with the new features and new missions as they work on their parts of the expansion. We try to fix our bugs the moment they are reported, but some slip through the cracks. This is where the QA department comes in. Our testers complete the game on all platforms in many configurations of equipment/game progress for several weeks leading up to the release. This part of development also continues way past the release date as we fix problems reported by you.



The Riftbreaker is available on a lot of various platforms - many PC storefronts and the two next-gen consoles. Each platform we develop the game for has different requirements and rules we must comply with. These generate unique problems that we need to iron out for each platform individually. Unfortunately, this means that sometimes we need to delay things. Into the Dark was not released simultaneously on all storefronts, as we needed some extra time to deal with memory, performance, and save file size issues that plagued some of the builds.


No bugs in this GIF, only a lot of explosions.

In addition to manual testing, we run automated tests several times a day. These tests run the latest available build of the game, and load saves that we prepared beforehand. In total, we run more than 150 saves - a collection made at different points of The Riftbreaker’s story campaign in various versions of the game. Each time we release a new patch, we add a couple of saved states to the test list to ensure compatibility. Not only does the test load save files, but it also saves the game again and checks whether the newly saved game still works. Automated testing allows us to catch a lot of problems before they have even had time to affect us, let alone any users.


If you make a good game, but nobody hears about it, did it really happen? Marketing is another ongoing process that has no clear endpoint. It begins with the moment we announce we’re working on the expansion and lasts for the entire production cycle. The entire point is to make gamers aware of the new content coming to the game - a difficult task considering how many new games and updates are released weekly. In our case, each marketing campaign has a pretty slow start as we usually have very little to show - some promotional artwork, a couple of screenshots, and a vague description based on the features we’re planning to include. The tempo ramps up as more features reach their final levels of polish, culminating with the release of the trailer on the launch day.

The work on the trailer video begins when the first gameplay prototype is available. We write a screenplay with a detailed description of the scenes and what new features they show. We also choose a suitable soundtrack for the trailer at this point, since it’s much easier to edit your video to match the music, not the other way around. Then, it’s time to record sample scenes. These are recorded using whatever is available at that time, even if some of the features are incomplete. Thanks to this approach, we can approve the initial edit of the video early on and replace the placeholder scenes with actual footage, drastically reducing the workload at launch. Here’s an example: an early placeholder version of the trailer for Into the Dark:


Do you recognize the big guy at the end?

And the final version, for comparison:



Another important part of getting the attention of the players is trying to get media coverage. We try to get in contact with game journalists, bloggers, and influencers - but again, so does every developer on the planet. At this point, it is a numbers game - you reach out to as many people as possible. At least ninety percent will not respond to you, and seven percent won’t be interested or won’t have the time. You have to do as much as you can with the remaining three percent of people willing to work with you. This is why it’s really important to start early.



The addition of Volumetric Lighting came in the final weeks of the project. It added a lot of character to the biome.

As we near the release date, more and more features reach their final form. Bugs are fixed. Models are finalized. Sound effects take shape. Dialogue lines are improved and recorded by voice actors. Everyone starts to feel the pressure of the release date drawing near, and we begin the mad dash to the finish line. All placeholders must be removed and substituted for the final assets. At this point, every placeholder that is noticed by the QA is marked as a bug and fixed immediately. Trailer scenes are rerecorded, and the video is edited into the final cut.


A LOT of character. We even rerecorded the entire trailer, even though some scenes were good already.

Sometime before day zero, we release an experimental update for volunteers. The truth is that you can test the game for months, but the moment you release it to the public, you are going to find bugs that you had no idea could even happen. This is due to the differences in hardware, system software, drivers, and even individual playstyle. Releasing an experimental build helps us catch a lot of things that would otherwise greatly impact the final quality of the game. If you take part in our beta periods and report bugs - thank you from the bottom of our hearts!


We usually have a release candidate build locked in when the release day approaches. It’s a build of the game that is well-tested and good enough for public scrutiny. However, we always plan ahead and usually schedule a couple of patches ahead of time. We also actively monitor the community channels and our crash reporter dashboard in search of the most common problems that we have to prioritize. We include fixes for those with the scheduled patch releases and start over. This loop usually continues for the next couple of weeks. When the number of reported errors dies down, we gradually reduce the hours spent on the project and focus on the next milestone.


The cycle started anew, with World Expansion III now in the works. You can help us by dropping a wishlist here:

https://store.steampowered.com/app/2506610/The_Riftbreaker_World_Expansion_III/

The milestones we currently have in our sights are World Expansion III which you can add to your wishlist now, and, of course, the co-op multiplayer mode. As we stated before, the work on these two runs in parallel and we try to give the programmers as much freedom as they need in order to get this feature to you. As always, if you want to be ahead on the news on The Riftbreaker and all other things related to EXOR Studios, follow us here and join our Discord: www.discord.gg/exorstudios. We also started streaming previews of WE III on www.twitch.tv/exorstudios. See you there!

EXOR Studios

As you might already know, The Riftbreaker runs on our own game engine, which we call the Schmetterling. Although working with your own tech is not always easy, it gives us the freedom to implement any number of new features and techniques to make the game look and feel better. During the development of the Into the Dark expansion, we realized we needed one key rendering feature to significantly improve the biome’s atmosphere. The effect in question is volumetric lighting. Today, we will tell you what role volumetric lighting plays in graphics, how games tried to emulate its effect in the past, and how we implemented this new feature in The Schmetterling engine.

Light scattering phenomenon

Atmospheric scattering is a phenomenon that affects everything we see around us. Even though we don’t often think about it, the air around us is a mixture of various particles that can interact with one another. They are also large enough to interact with photons - particles (and waves, but let’s not get too deep here) that carry electromagnetic radiation, including light. As a result of these interactions, some light gets scattered, some is absorbed and transformed into kinetic energy, and some passes through. Thanks to this, we can observe the blue sky above us and atmospheric fog when looking into the distance and many other beautiful effects.



The same principles apply on a smaller scale. Imagine entering an old, dusty house on a sunny day. As you enter, the microscopic dust particles covering the floor are set in motion and suspended in the air for a while. You look up to the window and see a beam of light cutting through the mix of air and dust. The light illuminates the room, but you can see that it is dispersed unevenly, as the varying density of the air-dust mixture creates a mesmerizing spectacle of light and shadow. The same thing happens during concerts when spotlights cut through the thick smoke. Or when a single beam of light cuts through a hole in the clouds. Or when your car’s headlights create a ‘wall of light’ effect when driving through fog.



The point is - it is rare for light to get from its source to the final point of its journey without encountering any obstacles. Each interaction with other particles along its way will change the light’s color, direction, or intensity. The result would look ‘flat’ and artificial without considering all this when rendering computer graphics. However, when appropriately implemented, the light and objects on the scene work together to create a cohesive and natural-looking image.

How it's emulated in computer graphics

Several techniques have been developed to replicate the scattering effect and achieve realistic results at an acceptable performance cost. Some developers used particle effects to emulate this (we do this too). Still, it was a very tedious process - the particle had to be created with a specific, static scene in mind and didn’t work in any other circumstances. Other developers used post-processing shaders that added lighting effects based on screen-space information. Those could adapt in real-time, but only as long as the light source was on the screen. In The Riftbreaker, we limited ourselves to exponential distance fog - a simple algorithm that created a fog that got denser the further it was from the camera. We could change its color to adapt it to the time of day. It worked okay in open areas, but we needed something better in Crystal Caverns.



The technique we decided to use is called Volumetric Lighting. It can emulate the previously mentioned effects based on a couple of relatively simple steps. Instead of painstakingly calculating light scattering for individual pixels by casting rays, the scene is simplified by dividing it into larger volumes. We conduct calculations for all of these volumes individually and later combine the results into the final rendering output for the visible scene. This dramatically reduces the workload while giving us an approximation that is good enough for in-game use.

Volumetric Lighting explained

The scene is sliced up into cubical volumes calculated from the camera frustum perspective. Their exact number depends on the game’s rendering resolution, which we divide by 8. If we take 1440p as an example, we get 320 volumes by width and 240 volumes by height. When it comes to depth, the resolution is fixed - it’s always 64 layers, which, given The Riftbreaker’s isometric camera placement, gives us roughly 300 meters of depth to work with.



At this point, the volumes are empty, and the light would travel through them unobstructed, like through a vacuum. We must add a transfer medium to the equation for the desired result. As we mentioned earlier, the air serves that function in the real world, along with all the suspended particles. We generate a 3D texture to simulate this phenomenon. It uses the exponential height fog at its core, generating a dense mist at the deepest points of the scene that becomes thinner as the distance from the ground increases. The texture carries information about density, which varies slightly from point to point. A new texture with different values is generated every frame. We can control its density and variability using a set of parameters to get the desired artistic effect.



We can now move on to the next stage of the process. Using the density volume grid from the previous step, we can calculate how light would behave while traveling through each volume. When we combine the air density data and the light parameters, we approximate how the light would scatter in that area. We perform these calculations for the entire grid, creating a 3D map of light scattering on the visible graphics scene.


A sample scene we used for development. It features multiple sources of light, which sets a good benchmark for us.


64 layers of the light scattering model data generated from the sample scene. They are presented one by one, going from the bottom to top.

To present these results to the player, we need to perform one more step called light scattering transmittance accumulation. During this operation, we sum up how much light is transmitted through each of our 64 layers of volumes and what the final result should look like from the perspective of our game camera. Starting from the camera’s position, we take the light scattering values for the first volume and add them to the layer beneath it. Then, we add the sum of our first two layers to the third one, considering the air transmittance value. Rinse and repeat until we reach the bottom of our 64-layer grid.


The same data presented after the light scattering transmittance accumulation step. You can see the influence that the underlying layers have on their neighbors.

The simplification we applied earlier, treating the scene as a lower-resolution grid, now causes some issues. Since we have taken average values for larger areas, the resulting image would be full of solid-color squares with sharp edges visible where different volumes meet. This image artifact is called banding. The unpleasant phenomenon can be fixed by applying temporal techniques. First, we add a slight jitter to our calculations. For every frame, the lighting for each volume is calculated at a different point within its bounds. This guarantees that the result will be different in every frame. Then, we can use a couple of frames of data to get an average of volumetric lighting within a time period. This allows us to achieve a soft image without aliasing, banding, or other artifacts, apart from slight ghosting, which is unfortunate but far better than the alternatives.





A sample scene before and after the temporal techniques are applied. You can clearly see the lighting artifacts on the light shafts, which disappear completely after introducing jitter into our calculations.

Performance results

We conducted some performance tests to see what kind of impact Volumetric Lighting has on The Riftbreaker at various points of the day and night cycle. We chose sample scenes in various biomes and measured the performance results at 0:00, 8:00, 16:00, and 21:00 in-game time. We conducted these tests on a Ryzen 5 5600X CPU, 32 GB DDR4 RAM, and RTX 3080 GPU machine running Windows 11. The game was running at 4K resolution, with all settings at maximum, raytracing enabled, and no upsampling or resolution scaling.


Sample scene from the Jungle biome.



Sample scene from the Magma biome.



Sample scene from the Caverns biome.



Sample scene from the Acid biome.

Conclusion

Volumetric Lighting is not a new technique. It has been used in games for years, and you have most likely seen it in dozens of them. The introduction of the Crystal Caverns biome into The Riftbreaker seemed like a perfect opportunity to add this feature to The Schmetterling Engine. It makes the graphics scene more realistic and adds significance to what used to be empty space. It also gives our artists additional tools to create atmospheric ambiances, with delicate fog and lights playing a significant role in creating the game’s mood.

We hope you enjoyed learning about this technique as much as we enjoyed the R&D process behind it. What other aspects of game development would you like to learn about? Let us know in the comments and on our Discord at www.discord.gg/exorstudios. Volumetric Lighting is undoubtedly not the last feature we will expand our engine with. When we decide to add something new, you will certainly hear about this on our Discord first. You will also see the previews during our Twitch streams at www.twitch.tv/exorstudios every Tuesday and Thursday. See you there!

EXOR Studios

When discussing game development, people often gloss over the audio side a little bit. It is quite natural, to be completely honest. New graphical developments are immediately noticeable. Beautiful shadows, reflections, and other effects make modern games a visual feast. At the same time, revolutionary gameplay mechanics and rich storylines ensure that we remember what we played for years. The sound is an outlier here. Since we can replicate and create almost any sound on most audio devices, we got used to its high quality and tend not to notice it most of the time. Still, it is a big part of a game’s presentation layer, and we want to tell you a little bit about it today.

Most of the media in this article are videos, which you should watch with sound on.



Whenever we add something to The Riftbreaker, be it a new weapon, building, or creature, we need to think about the sounds it is going to make. Over the course of our lifetime, our brains develop a subconscious expectation of what kind of sounds we can expect from any given object or phenomenon. Small creatures make squeaky, high-pitched sounds, hiss and snarl. Large monsters with gaping maws make your insides tremble with their mighty roar and shake their surroundings with their footsteps. You can always hear clanging and rumbling from inside a factory… The list goes on and on.



Even though most of the things we design sounds for in the Riftbreaker do not exist in the real world, the game's visual aspect is often quite enough for us to know what kind of sounds we are looking for. We briefly describe our ‘expectations’ for our sound designer. Then, he scours thousands of sound samples from various libraries in search of the perfect one for the occasion. More often than not, the perfect sound does not exist - finding a perfect sample for the effect you want to achieve is hard. Then, the sound designer has to get creative and mix a couple of samples to get the effect he wants.



We’re going to use a simple example here. When we were looking for a good sound for our rocket launchers, we wanted the sound they make to be both punchy and booming with bass. We found a sample that cut through the chaos of battle pretty okay but was lacking in the low end of the sound spectrum. Luckily, there is an entire “genre” of sound samples called textures. They are not meant to be used on their own. Instead, you can use them to beef up other samples. We found a couple that worked well but couldn’t decide on just one… So we used all of them instead! The result is what you know as the rocket launcher shot sound in the game today.



Other times, creating a sound effect is not that easy. One of the most complex sounds in the game is the one tied to Mr. Riggs’ movement. It has a lot of layers - the servomotors moving the mech’s body parts, the clanging metal from all the parts of armor, and the footsteps themselves. We wanted to cover all the bases with just one sample at first. You can hear our early attempts in the video below. Safe to say, we were not happy with the results for two reasons. First of all - it didn’t sound good enough. That could be fixed with a bit more work. However, the second problem lay a lot deeper. Due to the free movement of the mech in the game, the sample often got cut in the middle of playback. That had to be solved with the help of programmers.





We decided that combining the samples of the mech's entire ‘walk’ cycle into one sound was not the way to go. Instead, we separated all the portions of the sound we told you about earlier. Then, we attached all those individual sounds to various moments in the ‘running’ animation. Once the game detects that the mech is moving, it plays a short loop of servomotor sounds that sound good, even if stopped abruptly. Footsteps are played back only when the mech’s foot touches the ground. This also allows us to detect what kind of a surface you’re walking on and play a sample prepared for that type of terrain. That allowed us to finally solve all the problems. And that was just the walking sound!



At some point, we realized that the scope of The Riftbreaker was so large that we wouldn’t have the time to do all of the sound effects justice. We decided to give the job to Marcin Pukaluk, our music composer. As a professional musician, he has the necessary experience, skills, and tools that are needed to pull this kind of job off. He is the author of the vast majority of The Riftbreaker’s soundscape. The next time you don’t notice a sound because it blends with the environment well, you know who to thank for that!

Speaking of Marcin, he was also responsible for The Riftbreaker’s entire soundtrack. When we started our collaboration, we told him that we wanted the game’s soundtrack to feature a recurring theme that could ‘come back’ in various songs featured in the game. When you think of it, many popular pieces of media have a music theme. We decided to learn from the best: Star Wars, Indiana Jones, James Bond, Uncharted, and even Doom. Other than that, Marcin had complete creative freedom when it came to the composition of the tracks. We are really pleased with how it turned out. If you haven’t done it yet, give the soundtrack a listen. We put it up on YouTube. You can find it right here:



The portion of the audio that was left for us to prepare on our own was the dialogues. We have already told you a little bit about what working with dialogues looks like in our article about Mr. Riggs’ voice. We have worked with three voice actors on The Riftbreaker so far: Francesca Meaux as Ashley, Ryan Laughton as Mr. Riggs, and Tori Kamal as Colonel Norstrom from the prologue mission and the X-Morph consciousness. Audio technology is so good and affordable these days that we can collaborate with our actors fully remotely. We send them dialogue lists with all the lines we need them to read. The actors record the lines on their home audio equipment and send us a WAV file. We cut the file into samples and put it in the game - simple as that!

The “Into the Dark” DLC added a new difficulty modifier to this model. We added another character with dialog lines in the form of the Anoryx Worm. However, we decided to experiment a little. We knew we wanted the creature’s voice distorted and otherworldly. This allowed us to ignore the fact that none of us are native speakers of English and record the audio ourselves, as all the minute details in pronunciation would not be nearly as noticeable. Our volunteer for the task was voidreaver. He waited until everyone left the office to come up with the silliest voice he could muster. This is the raw result:



Obviously, this was not ready to be put into the game. We have done some research on how we can make void sound like a monster and discovered a sound-processing plugin that was quite promising. The plugin could transform any sound in a couple of ways with just a few turns of a virtual knob. Here’s a short presentation of how it works:



After we dialed in a sound that we liked, we added a couple of additional effects to make the sound a bit more ‘ethereal’ and ‘otherworldly’ (a very specific set of qualities, isn’t it?). We think that the end result was pretty okay for a first attempt - let’s see if we repeat this in the future!



We could talk about a million more things, but let’s leave some content for the future! We hope you learned something new today about the often underappreciated world of game audio. Let us know what other aspects of game development you’d like to read about! We’re waiting for your comments here and on our Discord at www.discord.gg/exorstudios. We’d also like to invite you to our streams at www.twitch.tv/exorstudios every Tuesday and Thursday - we’re going to start previewing the new biome from World Expansion III next week (hopefully), along with our regular co-op progress previews.

See you soon!
EXOR Studios