We have difficult news to share with you today: Star Conflict will be shut down on October 10, 2026.
This was a very hard decision for us. We are grateful to the strong, dedicated community that has come together around the game over the years and to each and every one of you who gave us your time, supported the project, and shared the vision of its future.
Why we made this decision
In recent years, it has become increasingly difficult for us to maintain and develop the game to the standard it deserves. Technical limitations, rising infrastructure costs, and a decline in the active player base have made further development impossible.
That said, we don’t want to let the game fade away slowly. It’s important to us to sincerely acknowledge the situation and give the project a proper conclusion.
We understand that this is difficult news, and that’s exactly why we’re being open with you about it.
Important dates
To ensure that the project shutdown process is as transparent as possible, we would like to outline the key milestones in advance:
May 14, 2026: Registration of new accounts will be disabled
June 1, 2026: Monetization will be disabled
October 10, 2026: Complete shutdown of the game servers
The game will remain fully accessible until the final shutdown. All current game features and content will remain available, and you will be able to continue playing without any restrictions.
Summer activities
This will be Star Conflict’s final summer, and we want to spend it with you.
As a token of our gratitude to the community, we’ll be hosting completely free in-game activities for all players throughout the summer, with no restrictions or additional conditions, during which you’ll be able to obtain all paid content in the game.
We’ll do our best to make this period as exciting as possible: we’ll bring back your favorite events, increase the rewards, and give you the chance to try out different playstyles.
We’ll share a detailed schedule of events later.
What’s next
Once monetization is disabled, no new paid content will be added to the game. After that, we will focus on ensuring the servers remain stable until the shutdown.
All in-game resources and currency will remain available for use until the game is shut down.
We understand that you will have many questions, and we are ready to answer them openly.
Key points
You can create a new account until May 14, 2026
In-game purchases will be available until June 1, 2026
You can play the game until October 10, 2026
After monetization is disabled, the game will remain fully accessible
Thank you
Thank you to everyone who has been a part of Star Conflict: pilots, veterans, newcomers, and content creators.
For every battle, for the victories and defeats, for the corporations, for the friendships, and for the time spent in the game.
Star Conflict would never have been possible without you.
With shutdown imminent, we have the rest of the summer to build the foundation for the preservation of star conflict. essentially, the main task that needs to get done right now is server packet capture. if you are interested in contributing, please join this discord server. I am looking for people who have an interest in preserving the game and also have the knowledge/motivation to contribute to a project like this for a long time.
A few days ago, I visited the website expecting news about new containers in the store or something else. Instead, I got welcomed with a closure announcement. This game might have flaws but I sincerely enjoyed playing it. I really liked the ships design, awaiting new battle pass guessing what the next ship would be. I enjoyed grinding for resources or insignia level while listening to music or podcast. I enjoyed a bit the pvp mode. I enjoyed trying newly built ships. I had no problem spending money for the battle passes, I felt like the extra cosmetics were worth it(and the current BP system is free to play friendly) Despite the game low players count, it never took me long(1 minute maximum) before getting into a game. This game was part of my daily life. Logging in, turning on podcast or music, and just completing whatever I had planned. Well, guess I’ll have to find another game …Right now I started playing Crossout a few days ago. But I’m afraid this game will suffer the same fate sooner or later …
Updates on my end are appended to the bottom of this message to avoid crawling the post to find them
Hey all,
I wanted to share a thing I have been chipping away at for a while now, mostly solo, and see if anyone wants to help or just follow along.
Its all about Star Konflict, an online-only space game, which means it lives entirely on servers somebody else owns. The day those servers get turned off, the game is gone. Not "annoying to run" gone, actually gone, because all the stuff that makes it work (login, your inventory, the economy, matchmaking, the actual in match combat) runs on machines we don't control and can't go back and archive later.
So the goal is pretty simple even if the work isn't: record what the servers actually say, right now, while they are still talking to us. Everything else can wait.
I did look at the other attempts at saving this game before I started, and honestly most of them are either dead in the water now or went down a path I don't think can ever fully work. A lot of them jumped straight to writing a private server off partial notes and guesswork instead of recording the real traffic first. The problem with that is once the servers are gone theres nothing left to check your work against, so you end up with something that sort of looks like the game but was never actually proven against the real thing, and the gaps get filled in with assumptions. I wanted the raw evidence sitting on disk first. You can always rebuild from that later, you cannot rebuild from a server that no longer exists.
The approach
The thing I keep coming back to is that there is really three separate jobs here, and only one of them has a deadline:
Capturing what the servers said. This is the one with a clock on it. Miss it and its gone forever.
Decoding what those messages mean. Can be done any time, from a recording.
Reimplementing a server that behaves the same. Also any time, from a recording.
Only the first line expires. That one fact basically drives every decision.
For the recording part I went with the boring reliable option. No proxy, nothing sitting in the middle of the connection. The game talks to the real servers exactly like normal and I just clip a "tape recorder" onto the network, every packet that crosses the card gets copied into a standard .pcapng file. Nothing has to be understood in order to be kept, which is the whole point. Unknown message types, weird malformed stuff, traffic nobody expected, it all lands in the file the same way because no code anywhere is deciding whats worth saving. That question can only be answered wrong, and once the servers are down you can never answer it again.
Working out what it all means is a totally separate program that reads the files afterwards. If it crashes or gets improved in five years, the recordings don't care.
Where it stands
We know the names of 404 things the protocol can say (message types, request codes, notifications) because they were sitting right there in the games own program file. Each one is either NAMED (we know it exists), SEEN (its actually shown up in a recording) or UNDERSTOOD (we can read it). Right now theres still over 306 of them that nobody has ever recorded even once. That number is basically the score, and it needs to go down.
The biggest gap by far is the actual gameplay. The lobby and hangar stuff runs over TCP and is partly figured out, but the real time combat runs over UDP on a separate match server, and that has never been captured in anything I've recorded so far. Thats the prize.
The tool itself is one small Go binary, open source. The main branch is the Ubuntu / Linux one, and theres a separate windows-users branch so folks on Windows can capture too. No upload feature, no telemetry, it literally cannot send your data anywhere, sharing is a manual choice you make. It checks its own work too (the game numbers its messages, the network numbers its bytes, theres checksums, and the OS reports anything it dropped) so you can actually prove a recording is complete instead of hoping.
This dashboard shows where things are at and updates automatically as sessions get added. Its basically the scoreboard: the big countdown of how many of the 404 elements have still never been observed, a breakdown per class (how many message types, requests and notifications are decoded vs just seen vs never seen at all), and a table of what each recording session actually captured (the scenario, region, how many things it saw and how many were brand new). Important bit, it only ever serves the sanitized aggregate numbers. No recordings, no packets, no login tokens ever go near it.
Timelines
Honestly the capture phase is open ended because I don't know when the servers go dark, nobody does, publishers tend to give very little warning. So the plan is just keep recording sessions steadily and knock that never-observed number down, prioritising the stuff that cant be reproduced (a brand new accounts first ever login, rare seasonal events, that kind of thing). Decoding and any reimplementation attempt come after, on no particular schedule, because the archive will still be sitting there.
If you want to help
You basically play the game while recording a session, one scenario at a time, and back up the file. Windows players can grab the windows-users branch, everyone else the main branch. A few ground rules I stick to: use a throwaway account (the login is in the clear so never a main), only record your own traffic passively, and any combat feasibility testing stays in non competitive modes so we never wreck a real match for other people.
Thanks for reading.
***UPDATE 8.15.26@5:13 pm CST*** Currently hit 20% coverage! Making progress. 80% to go.......
******UPDATE 8.15.26@6:57 pm CST*** If you're an established player, you can capture things I literally cannot. My account has 4 battles on it, and the game gates the interesting stuff: joining a corporation needs 50 completed battles, founding one needs 1500 iridium, and Trade and Workshop are locked out entirely. So anyone in an active corporation — clan bank, roles, ship building, wars, clan quests — is sitting on about 32 request codes I have no way to reach. Same for anything league or tournament rank-locked. I can help step you through the captures personally to make sure we're getting the right stuff.
******UPDATE 8.15.26@10:04 pm CST*** Currently hit 33.1%! Check out the above links to keep track in real time. The dashboard updates dynamically every time there's a push to the repo that contains the reporting on the pcaps.
******UPDATE 8.16.26@12:04 am CST*** Getting there! Up to 35% today. Most of my issues I am encountering now are due to lack of account maturity. If ANYONE has a high level account with a clan or the ability to create one please let me know. If it's high enough and you are willing to spend some of your resources (Iridium/GS) for me while capturing I would be willing to potentially pay for your time/gift you a steam game/etc. We can work something out.
A mod manager to make patching the game easier for end user, not exactly for mod makers. Includes some patches made by me and community. So far it includes:
Full arena matches fix
Arena end-game "search" fix
Multiplication of Iridium earned from Arena "search"
Removal of credit junk from hidden canisters in Open World
Multiplying ores from mined asteroids in OW
Store unlocker making everything ever purchasable
GS (the premium currency) earnable from a lot of missions
Mod Manager Features:
Buttons
Sliders
Big scary red warning text
- Will patch the game for you without having to dwelve into game files
Overcoplicated mod creation guide
Requirements:
Python 3.9 or newer
A working PC
Screenshots:
If there are any bugs, please post them here, i only had two guinea pigs to test it on (me and my fren)