|
| 1 | +--- |
| 2 | +label: Bot Detection |
| 3 | +description: Mitigate malicious bot accounts joining public Realms by automatically detecting and removing suspicious connections. Includes an Experimental mode for advanced detection. |
| 4 | +order: 22 |
| 5 | +author: |
| 6 | + name: Frazer |
| 7 | + avatar: https://avatars.githubusercontent.com/u/136254012?s=96&v=4 |
| 8 | +--- |
| 9 | + |
| 10 | +### What is Bot Detection? |
| 11 | + |
| 12 | +Bot Detection is a protective feature designed to mitigate malicious **bot accounts** that join Realms to cause **latency**, **performance degradation**, or **gameplay disruption**. It is primarily intended for Realms that use **public invite codes**, where automated join attempts are more likely to occur. |
| 13 | + |
| 14 | +{{ badge text="Beta Feature" type="warning" }} |
| 15 | + |
| 16 | +> **Important:** Bot Detection reduces risk and disruption, but it cannot guarantee absolute prevention. Minecraft Realms are subject to platform constraints, and detection is based on observable behaviour at join-time. |
| 17 | +
|
| 18 | +### When Bot Detection is Recommended |
| 19 | + |
| 20 | +Bot Detection is best suited to: |
| 21 | +- **Public-code Realms** (open access, frequently shared codes) |
| 22 | +- Realms experiencing repeated **join floods**, **lag spikes**, or **suspicious new accounts** |
| 23 | +- Communities that require better stability during peak activity or events |
| 24 | + |
| 25 | +For private invite-only Realms, Bot Detection may be unnecessary unless you are actively experiencing suspicious join patterns. |
| 26 | + |
| 27 | +### How Bot Detection Works |
| 28 | + |
| 29 | +When enabled, Bot Detection observes join activity and applies automated mitigation to accounts that appear to be malicious or automated. This is intended to keep your Realm stable by reducing disruptive join behaviour commonly associated with bot activity. |
| 30 | + |
| 31 | +Bot Detection requires a **Relay Account to be in-game** to function. If the Relay Account is not online in the Realm, Bot Detection cannot execute its mitigation actions. |
| 32 | + |
| 33 | +### Detection Modes |
| 34 | + |
| 35 | +Bot Detection currently includes two detection modes: |
| 36 | + |
| 37 | +- **Regular Bot Detection** |
| 38 | + The standard detection mode. This is the recommended default and is generally sufficient for most public Realms. |
| 39 | + |
| 40 | +- **Experimental Bot Detection (Beta)** |
| 41 | + A more aggressive detection mode intended to identify more sophisticated bot behaviour. |
| 42 | + **This mode may occasionally flag legitimate player accounts.** Enable with caution and only when necessary. |
| 43 | + |
| 44 | +> **Caution:** If you enable Experimental Bot Detection, ensure staff are prepared to respond quickly to reports of legitimate players being affected. |
| 45 | +
|
| 46 | +### Requirements |
| 47 | + |
| 48 | +To use Bot Detection, you must have: |
| 49 | + |
| 50 | +- A configured **Relay Account** that is actively **in-game**. |
| 51 | +- Bot Detection enabled within the Realm Bot Dashboard. |
| 52 | + |
| 53 | +### How to Set Up |
| 54 | + |
| 55 | +1. Open the **Bot Detection** module in the Realm Bot Dashboard.<br/> |
| 56 | +  |
| 57 | +2. Enable **Bot Detection** using the main toggle. |
| 58 | +3. Under **Detection Settings**, choose one of the following: |
| 59 | + - By default, **Regular Bot Detection** is enabled |
| 60 | + - Optionally enable **Experimental Bot Detection (Beta)** if your Realm continues to experience bot activity |
| 61 | +4. Confirm your Relay Account is **online in the Realm**, as Bot Detection requires an in-game executor to operate. |
| 62 | + |
| 63 | +### Recommended Configuration |
| 64 | + |
| 65 | +For most public Realms: |
| 66 | +- Enable **Regular Bot Detection** |
| 67 | +- Leave **Experimental Bot Detection** disabled unless bot activity persists |
| 68 | + |
| 69 | +Enable **Experimental Bot Detection** only when: |
| 70 | +- Regular mode is insufficient against repeated bot activity |
| 71 | +- You can tolerate the risk of occasional false positives |
| 72 | +- Staff are available to handle disputes quickly and professionally |
| 73 | + |
| 74 | +### Best Practices |
| 75 | + |
| 76 | +- Restrict access to public codes where possible (rotate codes if abuse is ongoing). |
| 77 | +- Keep the Relay Account reliably online during high-risk periods (peak times, events, after a code is shared publicly). |
| 78 | +- Treat Experimental detection as an escalation tool, not a default setting. |
| 79 | +- Maintain a clear staff procedure for handling reports of false positives (collect the player name, time of join, and what they observed). |
| 80 | + |
| 81 | +### Common Issues |
| 82 | + |
| 83 | +**Bot Detection is enabled, but nothing happens** |
| 84 | +- Confirm the Relay Account is **in-game**. |
| 85 | +- Verify the correct Realm is selected in the dashboard. |
| 86 | +- Ensure the module toggles are saved and remain enabled. |
| 87 | + |
| 88 | +**Legitimate players are being flagged** |
| 89 | +- Disable **Experimental Bot Detection** immediately. |
| 90 | +- Continue using **Regular Bot Detection** while monitoring join behaviour. |
| 91 | +- If false positives persist, keep the feature in Regular mode and consider additional access controls (e.g., limiting code distribution). |
| 92 | + |
0 commit comments