RF455-166 [RF 4.55 / GoMMO v0.6.0] FireGuard Registration Fails at Character Selection — "Request Dropped: Not in the World"
Game: RF Online 4.55 Server Version: GoMMO v0.6.0 (Stock GameServer) Previous Working Version: GoMMO v0.4.0 Component: GameServer / FireGuard / Character Selection Category: Bug / Regression Severity: High — Blocks Character Access Status: Reproducible in Testing
Bug Description
I discovered a FireGuard registration issue in the stock GoMMO v0.6.0 GameServer.
When a player attempts to register or set a FireGuard password from the character selection screen, the GameServer rejects the registration request with the following message:
request dropped: not in the world
As a result, the FireGuard password cannot be registered, preventing affected players from proceeding through character selection.
This functionality previously worked in GoMMO v0.4.0, where FireGuard registration requests were accepted during character selection.
Server Log Evidence
Timestamp: 18:58:45
FireGuard Request: 0D/7F
Packet Size: 44 bytes
Observed sequence:
- The client sends a FireGuard registration request (
0D/7F) while at the character selection screen. - The GameServer receives the request.
- The server immediately rejects it with
request dropped: not in the world. - FireGuard registration does not complete.
- The player cannot proceed normally through character selection.
Steps to Reproduce
- Start the stock GoMMO v0.6.0 GameServer with FireGuard enabled.
- Log in using an account that needs to register a FireGuard password.
- Navigate to the character selection screen.
- Attempt to register a FireGuard password.
- Observe that registration does not complete.
- Check the GameServer logs for the rejected
0D/7Frequest.
Expected Behavior
The GameServer should accept and process valid FireGuard registration requests while the player is at the character selection screen.
FireGuard registration must work before the character enters the game world, because the player may be required to complete FireGuard authentication before proceeding.
The server should still enforce the appropriate account, session, and character selection validation.
Actual Behavior
The stock GoMMO v0.6.0 GameServer rejects the FireGuard registration packet because the player is not yet in the game world.
This appears to be an incorrect session-state restriction applied to the FireGuard registration handler.
Version Comparison
GoMMO v0.4.0
- FireGuard registration is accepted at character selection.
- Players can register their FireGuard password.
GoMMO v0.6.0
- FireGuard registration packet is received.
- The server rejects the request with
not in the world. - Players cannot complete FireGuard registration.
Technical Findings
Initial log analysis suggests that the FireGuard registration handler is being blocked by a world-entry or player-session-state validation check.
Since FireGuard registration occurs during character selection, requiring the player to already be inside the game world appears inconsistent with the intended authentication workflow.
The issue was observed using the stock v0.6.0 GameServer executable.
Current findings do not indicate that this is caused by gamedata, database modifications, or our existing custom FireGuard verification patch.
The exact internal condition has not yet been confirmed through disassembly or source-code analysis.
Requested Fix
Please investigate the FireGuard registration handler for packet 0D/7F in GoMMO v0.6.0.
Specifically:
- Verify whether FireGuard registration requests are incorrectly restricted to players who have already entered the game world.
- Allow valid FireGuard registration requests during the character selection phase, as supported in v0.4.0.
- Preserve proper authentication and session-state validation.
- Ensure that the change does not affect FireGuard password verification or other FireGuard security checks.
- Confirm that new players can register their FireGuard passwords and proceed normally through character selection.
Additional Information
We are currently testing an upgrade from our customized GoMMO v0.4.0 environment to the stock v0.6.0 release.
Our v0.4.0 environment previously had a separate custom patch addressing FireGuard re-verification behavior. That patch addresses a different issue and should not be confused with this registration failure.
We would prefer an official GameServer fix rather than introducing another custom executable patch.
Please review this as a potential regression in GoMMO v0.6.0.