01
Server plugin
Observe gameplay
Start with the actions reaching your server.
The plugin reads movement, combat, block interactions and protocol events. It builds structured observations so checks can work with the same player context.
From gameplay to a decision
Every signal.
Connected to its context.
A clear path from server observations to recorded evidence and staff review. Explore the systems behind FanumAC, and where judgement still matters.
How it fits together
Built around the evidence.
The local plugin and Cloud workspace have distinct jobs. Both contribute context to the same review workflow.
02
Player & world state
Reconstruct the context
An action only makes sense in its surroundings.
Player tracking and world information support the checks. Teleports, velocity, game modes, network conditions and server load affect which checks can safely run. Unsupported or unstable context limits the verdicts available.
03
Local detection
Run configured checks
Apply the checks your server enables.
Movement, combat, interaction and protocol checks evaluate the state they can substantiate. Operators can enable, disable or shadow individual checks. Some statistical and incomplete checks remain measurements for review rather than independent cheating verdicts.
04
Cloud workspace
Connect the evidence
Give each flag a place in the investigation.
Connected servers report evidence to Cloud. The workspace links flags, player history, available replay details and moderation records. What staff can view follows their account and server permissions.
05
Advisory learning
Add review informed analysis
Use patterns to guide attention, with safeguards.
Statistical models build personal behaviour baselines and assess multiple signals. Confirmed legitimate staff reviews can drive bounded confidence reductions for checks that over-report. Readiness and safe mode controls limit uncertain output; a statistical anomaly is not proof of cheating.
06
Staff & operator controls
Review and respond
Keep the decision connected to its evidence.
Staff investigate the available context and record review outcomes. Operators configure local enforcement and escalation policies. Corroboration and eligibility safeguards constrain automatic actions; advisory evidence alone is insufficient for automatic punishment.
Designed for careful decisions
Strong play deserves
the full context.
Skill, unusual hardware, latency and incomplete information can change what a signal means. FanumAC uses guards and review tools to reduce unsupported conclusions.
- Context before accusation
Checks are constrained by the player and server state they can model.
- Learning with human feedback
Review informed adjustment is bounded and visible to staff.
- Honest coverage
No claim to detect every cheat or guarantee zero false positives. Real-client validation remains essential.
- Operator control
Enable checks, use shadow mode, and configure enforcement for your server.
A few useful details
Questions about the pipeline.
Does Cloud replace the checks on my server?
No. The plugin runs local checks. Cloud connects evidence and adds longer-window analysis and review tools. A Cloud outage affects connected workflows while local checking continues.
Is the learning layer a guarantee of cheating?
No. It is statistical analysis using observed behaviour and staff feedback. Unusual play can be legitimate. Advisory output is reviewed alongside other evidence.
Can I inspect a check before enabling enforcement?
Shadow mode lets operators observe a configured check without its normal enforcement. Staff can review what the check reports before adjusting the server configuration.
Why are some measurements used for review only?
Timing, rotation patterns and rejected interaction attempts can have legitimate explanations. When sufficient causal evidence is unavailable, those measurements cannot establish a cheating verdict.
See the whole workflow