<\/p>\n
Good FiveM server rules define observable conduct, examples, exceptions, evidence and proportionate consequences.<\/strong> A short rulebook applied consistently is more useful than a long list of vague labels that staff interpret differently.<\/p>\n Reviewed 9 August 2026 against the current Cfx.re terms<\/a> and official server-reporting instructions<\/a>. This operational template is not legal advice.<\/em><\/p>\n State who the rules cover, which server\/Discord\/store surfaces are included, when they take effect and which platform terms take precedence. Identify the official published version. Do not claim that a community convention is a Cfx.re rule unless the current official policy says so.<\/p>\n Rule:<\/strong> [specific prohibited or required act] Example: \u201cDo not use information your character could not reasonably know.\u201d Then distinguish an out-of-character stream, a dispatch message and an in-character witness report. The label \u201cmetagaming\u201d alone does not explain that boundary.<\/p>\n Define acceptable server logs, full clips, timestamps, witness statements and staff observations. Preserve enough context before and after an incident. Never ask players to publish personal data or credentials. State retention and access limits for evidence.<\/p>\n Publish normal consequence ranges but allow documented exceptions for severe safety risks, cheating, evasion or repeated conduct. Avoid rigid automatic ladders that ignore evidence, and avoid undisclosed punishments invented after the event. Expired prior incidents should be treated according to a stated retention policy.<\/p>\n Server staff can enforce community rules. Suspected platform-policy violations should be documented and submitted through the current official reporting route. Report observable behavior, URLs, server identifiers, dates and evidence; do not turn rumor or an unpopular server theme into a claim of a platform violation.<\/p>\n Keep a dated change log showing the rule, old wording, new wording, reason and effective date. Announce material changes before enforcement where safety does not require immediate action. Review recurring appeals and moderator disagreement: they usually reveal an unclear rule or missing example.<\/p>\n","protected":false},"excerpt":{"rendered":" Establezca FiveM reglas claras con ejemplos, est\u00e1ndares de evidencia, consecuencias proporcionales, moderaci\u00f3n consistente, apelaciones y un registro de cambios.<\/p>","protected":false},"author":1,"featured_media":185862,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1899],"tags":[],"class_list":["post-55091","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials"],"_links":{"self":[{"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/posts\/55091","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/comments?post=55091"}],"version-history":[{"count":4,"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/posts\/55091\/revisions"}],"predecessor-version":[{"id":215553,"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/posts\/55091\/revisions\/215553"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/media\/185862"}],"wp:attachment":[{"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/media?parent=55091"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/categories?post=55091"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fivemx.com\/es\/wp-json\/wp\/v2\/tags?post=55091"}],"curies":[{"name":"gracias","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Define scope and precedence<\/h2>\n
Cover the core categories<\/h2>\n
\n
Use one rule template<\/h2>\n
\n
Examples:<\/strong> [two observable examples]
Exceptions:<\/strong> [documented edge cases]
Evidence:<\/strong> [logs\/clips\/context required]
Consequence band:<\/strong> [warning, temporary restriction, suspension or ban range]
Appeal:<\/strong> [channel, deadline and reviewer]<\/p>\n<\/blockquote>\nSet evidence standards<\/h2>\n
Run a consistent moderation workflow<\/h2>\n
\n
Use proportionate escalation<\/h2>\n
Separate server enforcement from platform reporting<\/h2>\n
Publish changes transparently<\/h2>\n