RF455-171 [RF 4.55 v0.6.0] MAU Combat Bugs — Incorrect PvP Damage Display and Hull HP Desynchronization
Game: RF Online 4.55 GameServer: Stock GoMMO v0.6.0
Severity: High Investigation: Read-only static binary analysis Status: Suspected root causes identified; runtime verification and fixes pending Category: PvP Combat / MAU System / Damage Display / HP Synchronization
Bug #1 — Incorrect PvP Damage Display When Attacking MAU
Description
When a player attacks a Bellato MAU, the client displays an incorrect damage number.
For example:
- Displayed damage: Approximately 21,000
- Actual damage to MAU hull: 1
The displayed damage does not correspond to the actual HP deducted from the MAU.
Technical Findings
Static analysis identified a possible incorrect return path in the GameServer.
Relevant functions:
landPvpStrike—0x140B5E880unitHullTakeDamage—0x140C1CFE0- Return path —
0x140B5EC63
When the target is a MAU, landPvpStrike calls unitHullTakeDamage, but the subsequent return path appears to use the rider's vitals() rather than the actual damage applied to the MAU hull.
This may cause rider-related HP information to be interpreted as combat damage in the client display.
Previous Fix Reference
A similar issue was previously corrected in our customized GoMMO v0.4.0 build under the internal fix identifier:
pvp14 — MAU PvP Damage Text Correction
The correction is not present in the stock v0.6.0 build investigated.
Expected Behavior
The damage displayed to the attacker must correspond to the actual damage applied to the MAU hull, following the intended damage-display rules.
For example, if the server applies only 1 damage to the hull, the client should not display 21,000 damage.
Request
Please review the MAU target branch in landPvpStrike and verify whether the actual hull damage is correctly propagated to the combat damage notification.
Consider incorporating the equivalent of the previous pvp14 correction into an official update.
---
Bug #2 — MAU Target HP Bar Displays Rider HP Instead of Hull HP
Description
When attacking a MAU, the target HP bar does not accurately represent the MAU's actual hull HP.
The target HP bar may appear full even when the MAU hull has already lost a significant amount of HP.
Observed Behavior
- MAU target HP bar appears full or nearly full.
- Actual MAU hull HP may already be approximately 25% remaining.
- Attacking players cannot accurately monitor MAU hull durability.
- The displayed HP may correspond to the rider's character HP rather than the MAU hull HP.
Technical Findings
The MAU appears to lack the necessary client-target synchronization of its hull HP.
The hull's maximum HP is associated with:
unitframe.m_nUnit_HP
However, the target HP display appears to use rider-related HP information rather than current hull HP and maximum hull HP.
The precise packet-level mechanism still needs verification.
This issue was also observed as unresolved in our customized v0.4.0 environment.
Expected Behavior
When a MAU is targeted:
- The target HP bar should represent MAU hull HP, not rider HP.
- The displayed maximum HP should correspond to the MAU hull maximum HP.
- HP should decrease as the hull receives damage.
- HP updates should be visible to eligible attackers in real time.
- Rider HP and MAU hull HP must remain separate.
Request
Please investigate the MAU target HP synchronization system, including the source of current and maximum hull HP and the packet updates delivered to attackers.
The intended result is accurate target HP display without changing MAU damage or defense balance.
---
Separate Observation — Normal Attacks Dealing Only 1 Damage to MAU
Description
Normal physical attacks against high-level MAUs sometimes deal only 1 damage.
The available analysis suggests that this is not necessarily a GameServer calculation defect.
Technical Findings
The MAU parts at approximately levels 76–78 have high defense values.
Observed m_nDefFc values range approximately from:
162,000 to 510,000
Under the current defense and damage calculation, some normal attacks are reduced to the minimum damage value of 1.
Similar behavior was previously observed in v0.4.0.
Classification
This is currently considered a combat balance observation, not a confirmed GameServer bug.
Request
Please confirm whether the minimum 1-damage behavior against high-defense MAUs is intended.
No damage formula or MAU defense adjustment is requested as part of the two synchronization fixes.
---
Summary
| Issue | Finding | Requested Action |
|---|---|---|
| Incorrect MAU PvP damage text | Suspected incorrect rider-vitals return path | Correct damage notification |
| MAU hull HP bar inaccurate | Hull HP not correctly reflected on attacker target bar | Synchronize hull current/max HP |
| Normal attack deals 1 damage | High MAU defense and minimum-damage rule | Confirm intended balance |
Additional Notes
- Investigation was performed through read-only static analysis.
- No production files were modified.
- No GameServer patch was applied.
- The reported code addresses correspond to the investigated stock v0.6.0 binary.
- The previously developed
pvp14fix may serve as a reference for the incorrect damage-display issue. - Runtime packet verification is still required for the hull HP synchronization issue.
Request to OldSchoolOps: Please investigate and address the incorrect MAU damage display and MAU target hull HP synchronization in an upcoming GoMMO RF 4.55 update, while preserving existing combat and anti-cheat behavior.
Thank you.