Splitgate Dev Tracker

(5/5) As always, we want to reiterate this is a BETA, and we really appreciate your patience, feedback, and support ❤️ We will continue to provide you with updates.

- CardinalSoldier (CEO, 1047 Games)

(4/5) This will help us tremendously, as we are currently limited to testing major changes internally before setting it lives to hundreds of thousands. If you choose to participate, expect longer wait times and potential bugs.

(3/5) Before we set everything live, we may do a shorter hour-long "live QA" smoke test tomorrow during the day (pacific time) with support for 10-20k players.

(2/5) What this means for tomorrow:
Our goal for tomorrow is to stably support 100k concurrent users with casual, ranked, and customs and a more robust queue system. We plan to give updates on expected wait times in our discord throughout the day.

(1/5) Message to our Beta Testers:

Olly, Nick, and Michael are working hard and continuing to make progress on server stability and capacity for tomorrow. At the moment, our primary focus is stability over capacity.

I can confirm this is exactly what went down. I was the guy in the back.

-endo

After much internal deliberation we’ve decided to leave servers offline until Friday (PT). This gives us the time needed to implement fixes to matchmaking and backend stability.

Our priority is to get all of you back into a more smooth experience. We appreciate your patience.

We have decided to keep servers offline for the rest of the day and into tomorrow

We want to have matchmaking back online as custom only isn't the experience we want to give our players and the matchmaking fix is going to take a while. Thank you for your understanding & patience

We can't emphasize enough how valuable our BETA continues to be for us to improve servers

We understand it is frustrating. If you want to avoid this frustration we urge you to wait for full release

For those willing to put up with our growing pains, WE APPRECIATE YOU TESTING❤️

I know this is far from ideal. This is why we extended our beta, and we are working our absolute hardest. Money doesn't solve the problem over night, but we are working hard to hire fast and ramp up the new hires.💪

We're taking servers offline at 1:15 pm PT for maintenance.

We're sorry about the short notice and long waits. We're letting you know as soon as we can but we need to get critical bug fixes in for further improved stability/capacity.

We will keep you posted with our progress.

While all our dev team is hard at work, we are LIVE right now on Twitch with our CEO CardinalSoldier doing another Dev Q&A! Come join and ask your questions! We are here to give answers! 🙏❤️

We are committed to being transparent/candid with all of you. If you enjoy these Q&A streams, let us know and we'll keep them up.

Reminder: For now, custom games is the only available way to play. This is to increase overall capacity. We'll inform you when matchmaking returns!

From 1047 Games: We are deeply apologetic to everyone who've waited a long time in the queue. We are continuously working to increase the maximum player count.

We are doing another Dev Q&A Stream on our Twitch in about 2 hours! Join us and ask questions!

Also, for those who waited, the capacity is higher and the queue is near 0 right now! Get in there! 🙏

Despite long queues and a matchmaking bug, today was a HUGE win for us:

- new all time peak concurrent!
- fixed "lost items" bug
- Redis database 30x boost
- server and game crashes way down

Huge progress and proud of our team! Still more to do but we got this💪

#SplitgateBeta

The servers have been rebooted and we are ramping up player intake again. Reminder that it's Custom Games only for now.

For those who just want want to play. We hear you. We want you to be playing Splitgate just as badly as you do. As always, thanks for your unmatched patience❤️

Most importantly, apologies for the long queue times. 🙏 We are blown away by how many of you have been patiently waiting!

As an FYI: We are using a first-in, first-out queue system, which means the players waiting the longest get in first/next.

As a note, limiting to customs should allow us to support more concurrent players (and shorten the queue times!) 🙂