SUPPORT
Entropy Protocol is in early alpha. That is not a marketing label. The game is actively being built, torn apart, rebuilt, and patched on a regular basis. Systems get overhauled. Content gets reworked. Databases get wiped when a major structural change requires it. That is the reality of what early alpha means.
Your characters, items, gear, progress, buildings, and anything else you have built or collected can and will be lost during this phase of development. Wipes happen. Sometimes they are planned, sometimes a breaking change forces my hand. Either way, it is part of the process. If losing your stuff is going to ruin your day, alpha testing might not be for you right now, and that is completely fine. The game will still be here when it is more stable.
I do not restore lost items, characters, or progress during alpha. Not because I do not care, but because the data is constantly in flux. Restoring something from a backup that is already two patches behind would cause more problems than it solves. When a wipe happens, everyone starts fresh. That is the deal.
The people testing right now are helping shape what this game becomes. Every bug you find, every crash you report, every weird interaction you stumble into is making the final product better. That is what alpha testing actually is. Not early access to a finished game, but getting your hands dirty while the thing is still being welded together.
There is no ticket system. No "your request is #48,291 in the queue" nonsense. You talk to me directly. This game is built by one developer. All support runs through our Discord, and the person reading your message is the same person who wrote the code you are having trouble with.
Not in the Discord yet? Join here first, then head to the support channel.
Crashes, connection issues, bugs, account problems, weird behavior, someone being a jerk in-game, whatever it is. Drop it in the support channel. If you can include a screenshot or describe what you were doing when it happened, even better. Most things get a response within a few hours because it is literally just me checking it.
When reporting bugs, tell me what happened and what you expected to happen. Tell me what you were doing right before it went sideways. If there was an error message, grab a screenshot. If you can make it happen again on purpose, that is gold. Do not worry about formatting. I would rather have a messy message with good details than a clean one that says "the game broke."
Minimum hardware requirements are not set in stone. As the game gets built out, systems get added, optimized, reworked, and sometimes completely replaced. What runs fine today might need a tweak tomorrow, and what struggles now might run smooth after the next optimization pass. That is just the reality of active development.
The goal is simple: I want as many people as possible to be able to play this game. That is not lip service. I am actively working to make sure Entropy Protocol runs on hardware that most developers would not even bother targeting. If your machine can open a browser and not catch fire, I want it to run this game. Low-end rigs, older hardware, the laptop you bought six years ago. Performance optimization is not an afterthought here, it is a core priority throughout development.
ENTROPY PROTOCOL © 2026 • Solo developer. All support handled directly.
