RF455-167 [RF 4.55 v0.6.0] Critical — Legitimate Teleport Recall Triggers Anti-Cheat Teleport Detection and Potential Player Ban
Game: RF Online 4.55 GameServer Version: GoMMO v0.6.0 (Stock) Category: Anti-Cheat / Movement Validation / Teleport System Severity: Critical — False Positive / Potential Player Ban Status: Reproducible — Root Cause Suspected
Bug Description
I discovered a serious issue involving legitimate server-side teleportation and the movement anti-cheat system in GoMMO v0.6.0.
When a player uses Teleport Recall to return to their race headquarters (HQ), the teleport itself completes successfully.
However, immediately after the character re-enters the world, the player's first movement triggers the anti-cheat detection move.teleport.
The server incorrectly interprets the legitimate position change as unauthorized teleportation.
As a result, the player's movement is rejected, and the character is returned to a previous position.
This is particularly concerning because the anti-cheat rule is configured with mode=ban, potentially exposing legitimate players to false-positive enforcement.
Steps to Reproduce
- Log in using a normal player account.
- Move to a location away from the race headquarters.
- Use Teleport Recall to return to HQ.
- Allow the teleport and map loading to complete.
- Attempt to walk normally after re-entering the world.
- Check the GameServer anti-cheat logs.
Actual Result
The legitimate teleport succeeds, but the next movement is rejected by the anti-cheat system.
Observed log indicators:
| Field | Observed Value |
|---|---|
| Anti-cheat detection | move.teleport |
| Observed movement value | 1480 |
| Additional observed value | 1354 |
| Maximum allowed | 641 |
| Enforcement mode | ban |
| Immediate action | reject |
| Repeated detection counts | 1, then 2 |
The server rejects the movement and appears to correct the player's position back to an earlier location.
The issue was observed repeatedly following Teleport Recall.
Expected Result
When a player uses a legitimate server-authorized teleport:
- The GameServer should recognize the teleport as valid.
- The anti-cheat movement baseline should reflect the player's new position.
- Normal movement after teleportation should not be flagged as
move.teleport. - Legitimate players should not accumulate anti-cheat violations.
- Anti-cheat protection against unauthorized teleportation must remain enabled.
Technical Investigation
Read-only investigation identified the following execution path:
Teleport handling:
handleGotoBasePortal → teleportTo → setPosition → beginMapLoad
The server updates the character's position when teleportation occurs.
However, movement validation through guardMove appears to maintain a separate record of the character's previously accepted position.
The investigation found that guardForget is called during disconnect handling, but no corresponding reset was identified after a successful server-authorized teleport.
This suggests that the first movement after teleportation may be compared against the character's location before teleporting.
That would explain why a legitimate teleport produces a movement-distance violation.
Important: This is a suspected root cause based on code tracing. The precise anti-cheat state transition has not yet been fully verified.
Potential Impact
This issue may affect:
- HQ Teleport Recall
- Base portals
- Map transitions
- Other server-authorized teleport operations using the same movement validation path
These additional teleport types have not all been independently tested.
The main concern is the possibility of legitimate players accumulating violations under a rule configured with mode=ban.
No completed player ban has been confirmed from the available evidence.
Recommended Investigation and Fix
Please review the interaction between:
teleportTosetPositionbeginMapLoadendMapLoadguardMoveguardForget- Movement anti-cheat position and timestamp tracking
After a successful server-authorized teleport, the movement anti-cheat should safely synchronize its baseline with the new authorized character position before normal movement validation resumes.
The correction should preserve anti-cheat protection and must not allow arbitrary client-controlled position changes.
Please also verify the behavior across HQ Recall, base portals, and other legitimate map transitions.
Questions for OldSchoolOps
- Is this a known issue in the stock GoMMO v0.6.0 GameServer?
- Should the movement anti-cheat baseline be refreshed after a successful server-authorized teleport?
- Does the current
move.teleportenforcement automatically ban players, or does it require additional violation thresholds? - Could this issue affect other portal and map-transition mechanics?
- Can this be addressed in an upcoming official GameServer update?
Additional Notes
The reported behavior was observed while testing the stock v0.6.0 GameServer.
The investigation did not identify evidence linking the issue to our customized patches.
The available log evidence shows movement rejection and anti-cheat violation counts, but does not establish that an account was actually banned.
Request: Please investigate this as a high-priority false-positive anti-cheat issue, since it may affect normal gameplay and legitimate players using Teleport Recall or other authorized teleportation systems.
Thank you, OldSchoolOps team.