Skip to content

Decide classless dagger damage scaling from STR and LUK

Classless dagger damage has two inherited stat rules and needs an explicit gameplay decision before the client and server can agree.

During client issue #1, the owner requested a separate issue and suggested either scaling from both STR and LUK or from the dominant of the two, while leaving the choice undecided. These are discussion options, not an approved formula.

Current source:

  • Server 24e990382f2cb50e3ece10382506d41b5d3f6658, src/client/MapleCharacter.java, calculateMaxBaseDamage: a dagger switches from the STR-based DAGGER_OTHER formula to DAGGER_THIEVES when Dagger Mastery, Double Stab or Savage Blow is learned. The latter uses LUK with STR+DEX as the secondary term. This learned-skill heuristic was introduced in b078b7663; no owner approval was found for using it as the classless rule.
  • Client production damage selection still uses the compatibility job for daggers. The researched non-dagger correction deliberately leaves this path unchanged: report at 468da07.
  • Original implementations distinguish STR-based non-thief dagger damage and LUK-based thief dagger damage. Those class distinctions do not decide the intended classless behavior. The pinned primary references and version limitations are in the linked report.

Decide whether dagger damage should combine STR/LUK or use the dominant stat, then specify the actual equation: coefficients, secondary contributions (including DEX), ties and any interaction with learned skills. A hybrid must not count a stat twice accidentally. Neither a particular weighting nor an automatic best-of-two-original-formulas rule is approved by this issue.

After that decision, align native displayed/calculated damage and authoritative server validation, retaining separate weapon/stat/level/slot requirements and existing learned-passive stacking. Check STR-dominant, LUK-dominant and tied builds; low/high ranks; equipment swaps; actual attack damage; and the same attributes under different compatibility jobs. Use isolated non-GM fixtures and preserve campaign state.

No dagger production behavior changes as part of opening this issue. Related server #42. This unresolved dagger rule does not block independent, confirmed engine fixes in client #1 (closed).