# Chat Behavior Policy

The CFL community — including the in-app global chat and Discord — is an important part of the overall experience. To keep these spaces healthy, welcoming, and fair for everyone, CFL enforces the following conduct standards and moderation process.

This policy defines unacceptable behavior, how CFL handles harmful or disruptive communication, and the strike system used for enforcement.

***

### **1. Definition of FUD (Misinformation & Harmful Claims)**

To avoid ambiguity, CFL defines FUD as:

> **The intentional spread of misleading, unfounded, or harmful claims that create fear, distrust, or damage to the community or the platform.**

Examples include:

* claiming the game is “rigged” or “manipulated” without evidence
* spreading rumors or accusations publicly instead of reporting privately
* making statements designed to harm CFL or cause panic within the community
* encouraging others to distrust the platform without factual basis

**Not considered FUD:**

* questions
* confusion
* constructive criticism
* suggestions
* genuine concerns brought up respectfully

***

### **2. Verbal Abuse & Harassment**

The following behavior is not permitted:

* insulting, attacking, or targeting other players
* hostile, aggressive, or abusive language
* personal harassment or repeated negative targeting
* hate speech or discriminatory remarks
* provoking arguments, taunting, or escalating drama

CFL encourages competitive spirit but requires respectful communication.

***

### **3. Disruptive Behavior**

These actions are also considered violations:

* spamming or flooding the chat
* impersonating staff or pretending to have official information
* derailing conversations or attempting to create conflict
* encouraging others to target, isolate, or attack another player
* repeated public call-outs instead of using the reporting system

Disruption reduces the overall quality of the community experience.

***

### **4. Strike System**

CFL uses a transparent, progressive moderation system.

#### **Strike 1 — Formal Warning**

* player receives a private message describing the violation
* no restriction is applied
* intended as a chance to correct behavior

#### **Strike 2 — Temporary Chat or Community Restriction**

* player may be muted in global chat
* player may be removed temporarily from Discord channels
* severity and duration depend on the violation

#### **Strike 3 — Final Action**

Depending on the situation, this may include:

* permanent chat ban
* permanent Discord ban

CFL may skip directly to Strike 3 for extreme behavior (e.g., hate speech, doxing, malicious threats).

***

### **5. Reporting Process**

Players should report issues **privately**.\
This ensures:

* accurate evaluation
* no escalation in public channels
* protection for the reporting player

Reports may include:

* cheating suspicions
* harassment
* misinformation
* targeted hostility
* abusive behavior

Public accusations in chat are not permitted.

***

### **6. Why This Policy Exists**

This policy exists to protect:

* new players from hostility
* regular players from harassment
* the integrity of community spaces
* the long-term health of the CFL environment

A respectful, drama-free community benefits everyone.

***

### **7. Final Notes**

CFL encourages open discussion, suggestions, and feedback.\
This policy is not designed to silence players — only to ensure communication remains respectful, truthful, and healthy for the entire community.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://crypto-fantasy-league-1.gitbook.io/crypto-fantasy-league-docs/rules-and-enforcement/chat-behavior-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
