Gameye Case Studies

Double the numbers, zero downtime

Chivalry II / Tripwire Interactive

Launch day can make or break a game. This medieval melee hack-and-slash brings together 64 players into a single battle to swing swords at one another. But on the day they had twice as many players as they expected. Despite this, we kept their servers up with zero downtime and handled the surge.

Read the case study

How Gameye got Clone Drone out of the Danger Zone

Doborog / Clone Drone in the Danger Zone

Clone Drone in the Danger Zone is a laser sword-fighting action game where any part of your robot body can be sliced off. With around 19,000 “overwhelmingly positive” reviews on Steam, it’s fair to say that it has an engaged and enthusiastic following. But the game itself was fast approaching a danger zone of its own.

Read the case study

Marrying mobile and VR game sessions

Space Team VR / Cooperative Innovations

Not everyone has a VR headset. So that meant Space Team wanted to make sure players could play through their smartphones as well.

Read the case study

Keeping up with competitive players on a tight budget

Project Xandata / Secret 6

When Secret 6 created their intense competitive 3v3 FPS, their old servers couldn’t handle the strain at a reasonable cost. So they chose Gameye to cut costs and improve their lag issues.

Read the case study

Helping indie studios stay in control

Ascendants Rising / Limitless Games

Working together, players fight their way across a multiverse in this co-op action-RPG. Ascendants Rising needed our help to make sure that their PvE experience was smooth for everybody playing.

Read the case study

Some of our other clients

Warhammer Age of Sigmar: Storm Ground

While strategy games don’t need the same immediate feedback as a first-person shooter, they can have a lot more computing behind the scenes. We’ve all played games where – as the turns go on – the game runs slower and slower. Each turn taking longer and longer. This is simply because there’s too much to calculate behind the scenes. And it’s even worse if the players host the game themselves – sometimes on budget computers. Storm Ground needed solid, reliable computers that could scale with the game.

We give each game room to grow. We host the sessions on servers with huge capacity reserves. As the skirmish builds up, with more and more units needing calculations, we automatically allocate more and more computing power. So the players get back into the action as fast as possible.

Pacer

In racing games, every second counts. It’s important that nobody can sneak ahead, just because they’ve got a slightly faster connection. If the server is off, then the whole race is going to be ruined. Whether that’s for the photo-finish or whether a shot lands.

Our platform can work with Pacer’s matchmaker to make sure that the matches are fair, and then orchestrate those matches so that we host them in the most fair location possible. We balance their latency needs and spin up the session on a server that’s as close to all the players as we can. And, by using servers with large capacity, we can do the heavy lifting so the player’s computer doesn’t have to.

Slapshot: Rebound

As with all sports, it’s important that every player is synchronized. Just like a first-person shooter, the players need to know exactly where they are. And every player needs a consistent latency. (Otherwise, the puck might end up in different places for different players.)

We choose locations based on low jitter. We not only make sure that the session is automatically hosted in a location that suits every player, but also change server locations and providers if there are any lag issues. So there’s zero interruption to the match itself.

Block n Load

First-person shooters need low-latency connections to make sure that every bullet is registered and that players can see one another, without snapping around the map. But there was an extra difficulty here: the players could change the map itself and build and destroy bases. That’s a lot of underlying physics (and a lot more data to send). A single mistake and a player could walk through a wall someone else had built.

For the matches themselves, we needed to make sure that players had low-latency connections. Otherwise, the players wouldn’t be able to hit one another. So our orchestration finds servers that are perfect for the match at hand. But we make sure to allocate enough capacity to memorize – and then synchronize – all the bases and defenses that players are putting down. And we do it all without significantly raising the cost for the studio.

Latest News

by Andrew Walker

September 19, 2023

Don't just take our word for it

Double the numbers, zero downtime

How Gameye got Clone Drone out of the Danger Zone

Marrying mobile and VR game sessions

Keeping up with competitive players on a tight budget

Helping indie studios stay in control