One of the most persistent questions in any idle RPG is whether what you see is actually what the game is doing. When your character sheet shows +16% item find, is that the exact value used when the game rolls a rare drop? In IdleWorlds, the answer is now unambiguously yes.
Before this update, the game computed bonuses like gold find, item find, and 2x gather chance in several different places across the engine — once for the character sheet display, and then again (sometimes slightly differently) inside each activity type. Gathering loops had their own inline multiplier calculations. Combat had its own. Zone control had its own. While they all read from the same item stats, there was no single source of truth that both the display and the engine were provably pulling from.
The refactor introduces a unified computeEquipmentBonuses function that aggregates every stat-carrying item you have equipped — weapon, ring, amulet, belt, trinket, helmet, chest, gloves, legs, boots, and shield — into one stat object. Every bonus (gold find %, item find %, XP per task, 2x gather chance %) is summed once, enchant buffs are applied on top, and the resulting object is what both your character sheet and every activity loop reads from.
A secondary fix in this update: weapon items can now carry non-attack stats. Previously, the engine only read attack bonus from equipped weapons and ignored any other stat fields. If you had a weapon with gold find on it, that bonus existed in the item definition but contributed nothing to your actual totals. That slot is now a full participant in every stat calculation.
The practical result is that if a stat appears on your character sheet, it is active. No backend discrepancy, no hidden rounding in a different code path, no secondary calculation that might drift from the display. What you see is what runs. Beta testers who have been manually verifying drop rates and gold accumulation against their displayed bonuses should now find that the numbers match cleanly.
This also sets the foundation for more complex future systems. Set bonuses, for example, can now be implemented as a bonus layer added into the same stat object — meaning they will automatically flow through to every activity that reads equipment stats, without any per-system wiring. New item stats added to any slot in the future will work the same way.