DevEngine
Terms Privacy Back to register

Community and moderation policy

This page exists so the rules are not vague and not absurd. It explains what kind of content is welcome, what gets removed, and how moderation should act with actual judgment.

Predictable moderation Proportionate action No witch hunts Safety over noise

What is welcome

  • Games, builds, guides, devlogs, engine discussion, design, UX, screenshots, and reasonable feedback.
  • Clear project descriptions, transparent download links, and honest labeling of what the user is downloading.
  • Criticism, even harsh criticism, as long as it does not become harassment, humiliation, or spam.
The idea is simple: the community should help development and project sharing, not turn into a dump full of fights, malware, and stolen content.

What counts as a violation

  • Malicious files, phishing pages, deceptive download buttons, cryptominers, stealers, and similar garbage.
  • Fraud, impersonation, and false statements made on behalf of the administration or the project.
  • Doxxing, threats, blackmail, stalking, mass insults, and targeted harassment.
  • Spam, manipulation, flood posting, meaningless repeated posts, and deliberate section pollution.
  • Publishing content without rights or without the author’s consent, as well as clear legal violations.
For severe violations — especially security threats, fraud, and illegal content — sanctions may be immediate and firm, without a long ceremony first.

How moderation works

  • If a violation is minor and fixable, editing, warning, or hiding a specific item is preferred when possible.
  • If the risk is high, content may be removed from publication immediately and the account may be temporarily limited pending review.
  • Repeated violations, ban evasion, and creating throwaway alts to continue abusing the rules increase the severity of sanctions.
  • Moderators should rely on the publication, attachment, event log, or clear context whenever possible, not tea-leaf divination.
Moderation is not the court of last resort, but it is not a roulette wheel either. Mistakes can happen, so the rules allow review of clearly disputed cases.

Sanctions and review

  • Escalation path: warning → content removal → temporary restriction → permanent block.
  • The chosen measure depends on severity, repetition, risk to people, risk to the service, and the user’s good faith after a warning.
  • If a decision appears mistaken, it may be reviewed manually through the site administrator or a future support channel.
A good policy is one where people can roughly predict the consequences of their actions, instead of living in fear of being nuked for a random sneeze.
These rules complement the Terms of Use and the Privacy Policy. Their job is to reduce absurd decisions and make the platform calmer and safer for normal users.