Community Safety
Acceptable Use Policy
These rules protect players, project owners, Mudhaven infrastructure, and other services sharing the host.
- Effective
- July 17, 2026
- Contact
- contact@mudhaven.net
Prohibited content
Do not use Mudhaven to publish, distribute, or facilitate unlawful material or activity.
- Malware, ransomware, credential theft, phishing, or deceptive downloads.
- Material that unlawfully exploits children or facilitates sexual abuse.
- Content that infringes copyrights, trademarks, privacy rights, or other legal rights.
- Credible threats, targeted harassment, doxxing, or instructions intended to enable immediate harm.
Security and access
Do not probe, access, alter, or interfere with systems, accounts, ports, files, or networks you are not authorized to use.
- No privilege escalation, sandbox escape, shell restriction bypass, or unauthorized vulnerability scanning.
- No sharing private keys, database passwords, control links, or another member's private project files.
- No mining, botnets, traffic relays, open proxies, or unrelated background services.
Network behavior
Game traffic must remain on assigned endpoints and ports. Do not launch denial-of-service attacks, floods, abusive crawlers, unsolicited bulk email, or traffic intended to evade network controls.
Member communications
Direct messages and other member communication tools must be used for genuine one-to-one community conversation.
- No unsolicited bulk promotion, repeated unwanted contact, threats, harassment, doxxing, impersonation, or attempts to evade a member block.
- Never request or send passwords, API tokens, private keys, recovery codes, or other authentication secrets.
- Use per-message reporting, Report and Block, and the direct-message safety feedback category when contact becomes unwanted or unsafe.
Fair resource use
CPU, memory, storage, file, backup, database, and network limits exist to protect every hosted world. Do not split workloads across duplicate accounts, generate artificial load, or intentionally defeat quotas. Report runaway processes and badly behaving code promptly.
Uploads and code
Uploaded files may be validated, scanned, quarantined, rejected, or removed. Server-side scripts are not accepted through BYOND project uploads. Public resources containing executable code receive staff review before publication.
Enforcement
Mudhaven may stop a process, block traffic, quarantine files, suspend access, or preserve relevant logs when needed to contain harm. Staff may ask for changes before restoring service. Serious or repeated violations may result in permanent removal and appropriate reports to providers or authorities.
Questions or notices
contact@mudhaven.net