1. Respect the people playing
Do not harass, stalk, threaten or intimidate another player. Do not use slurs, hate speech or dehumanising content targeting a person or group based on race, ethnicity, nationality, religion, disability, sex, gender identity, sexual orientation or another protected characteristic.
Do not encourage self-harm or real-world violence, sexualise minors, impersonate another person, or repeatedly target someone after they ask you to stop. In-game crime between consenting adult players is part of the design; real abuse is not.
2. Protect privacy
Do not share or threaten to share another person’s real name, address, workplace, phone number, private messages, exact location, account credentials or other sensitive information. Never put the shared beta access code into an in-game name or room communication.
Player names and live room events are visible to others in that room. Pick a name that does not reveal private information. Screen recording is possible, so act as if anything visible in a room can be captured.
3. Play fairly and do not disrupt the service
- Do not use automation, modified clients, injected scripts or network tools to gain an unfair advantage or corrupt another player’s room.
- Do not deliberately overload Cloudflare, Supabase, the Worker gate or another player’s connection.
- Do not bypass or help others bypass the beta gate, rate limits or security controls.
- Do not distribute a downloaded mirror of the game or republish source obtained from an earlier public repository.
- Do not use bugs to destroy a room, trap players outside normal game rules or cause persistent crashes.
Friendly fire, robbery, ambushes and competition can be legitimate game actions in modes that allow them. The line is whether you are playing the designed game or attacking the service or person behind it.
4. Report severe bugs and exploits privately
Send security issues, gate bypasses, crash loops or exploits that affect other players to support@hardblocklife.com. Include what happened, the browser/device, approximate time and safe reproduction steps. Do not include the beta code, session cookie or another person’s private information.
Give STOIC a reasonable opportunity to investigate before public disclosure. Good-faith testing that avoids harm, privacy invasion, persistence and service disruption will be treated differently from exploitation.
5. Keep room access sensible
A five-letter room code is easy to share and easy to guess; it is not a private, authenticated lobby. Share it only with people you intend to play with. Leave a room if someone arrives who makes it unsafe. The beta currently has no player account, block list, moderator chat console or persistent server history.
6. What STOIC may do
STOIC may warn a participant, revoke beta access, rotate the shared code, end a room feature, preserve limited evidence, contact service providers or report serious conduct to authorities where reasonably necessary and lawful. We may act without first warning when there is an urgent safety, security or legal risk.
Because the first beta has no player accounts, enforcement tools are limited. Access control is not a promise that every participant can be identified or removed instantly. Reports are assessed using available evidence and context.
These rules form part of the Beta Terms. Questions or reports: support@hardblocklife.com.