Changelog

0.1.3 candidate

Fixed host-biased hauling: the host could use its larger native hauling total to bypass the per-item limit applied to guests. Everyone now uses the same locally measured extraction contribution, with the same limits.
Removed host-only native support totals from scoring. Measured death-head rescue and host-confirmed healing remain separate scoring sources for everyone.
Ignore zero/non-finite extraction samples without consuming their object IDs; duplicate valid samples remain limited to one credit per object per level.
Add one host-log line per player at level end with raw contributions and every category's points, to make future scoring discrepancies diagnosable.
Added host/guest input-policy regression tests and 1,000 generated 2–16-player host-role permutations. The scoring suite now passes 60 checks.
Bumped the scoring protocol to v7 to avoid mixing old and corrected collectors. All multiplayer players must update to 0.1.3 for a complete ranking.
No result UI or DeathCounter dependency change. This candidate has not yet been retested in a real multi-account session; do not replace DLLs mid-game.

Fixed multiplayer reports and results never reaching other players: Photon rejects application event codes 200 and above, but 0.1.1 used 229/230. Both messages now use valid, distinct event codes, with a protocol bump and a regression test.
Log failed report/result sends and missing participant reports so an outdated or absent client build can be distinguished from a scoring problem.
Show MVP total points, the top three scored categories, up to two runners-up, and the OOPS setback points; the shared DeathCounter panel carries the same detail when both mods are installed.
Let F8 (configurable) show or hide the translucent standalone results panel; DeathCounter owns the toggle when the mods share a panel.
Extended the result packet and optional display bridge (protocol v6).
All multiplayer players must update to 0.1.2 for a complete ranking.

Renamed the second award to OOPS CHAMP (やらかし王) in the UI and package art.
Expanded its measured inputs to level deaths, actual health lost, damaging-hit count, heavy-hit count, critical-health entries, time downed, ending down, and a substantial deficit in the level MVP score. Minor scratches or close score gaps alone do not force an award.
The MVP is excluded from OOPS CHAMP selection; the award is NONE if no other player clears the meaningful-setback threshold.
Scores apply only to data from the current level. There is no special late-join exclusion.
Changed the owner report protocol to v4; all multiplayer participants must use the same MVP build.
Reduced results UI checks to twice per second. With DeathCounter installed, MVP sends its award only when the result revision changes and uses the shared truck panel.
Added the existing bug-report/request survey to the English and Japanese description.

Added per-level MVP scoring across hauling, room exploration, valuable discovery, death-head rescue, healing others, actual enemy HP damage, confirmed stuns, survival, and a small versatility bonus. Unclassified native scouting/support totals remain as fallbacks without double-counting the specific sources.
Added per-client extraction contribution capture so guest hauling/rescue are not lost when the base game increments those progression values only on the host.
Added the original separate setback-award foundation based on per-level deaths, actual health lost, and time spent downed; 0.1.1 expands and renames it to OOPS CHAMP.
Reports are bound to the sending player's avatar ViewID; the host computes and broadcasts the result. Missing player reports are marked incomplete rather than counted as zero.
Displays results in the following truck. RepoDeathCounter 1.4.4 or newer owns the shared scoreboard when present; otherwise MVP displays a small standalone results panel.
Added large-lobby-safe scoring and deterministic tie-breaking.

This is a test candidate, not yet a multiplayer-verified public release.