REPO Level MVP (test candidate)

After a gameplay level, the next truck shows an MVP and an OOPS CHAMP (the playful "やらかし王" award). This is a separate mod and needs only BepInEx. All players should install it for a complete multiplayer result; the host calculates the ranking and broadcasts it. If a player does not report, the result says DATA INCOMPLETE instead of treating them as zero. The result shows the winner's total points, their three strongest score categories, up to two runners-up with points, and the OOPS CHAMP's separate setback score.

The MVP combines measured contributions and survival across these categories:

Each active contribution category is normalized against the strongest eligible player, with diminishing returns. A category with no observed activity is omitted and the other weights are rescaled. Survival alone cannot earn MVP.

OOPS CHAMP is calculated separately from eight measured viewpoints: deaths, actual health lost, damaging-hit count, heavy hits (25+ health lost in one hit), entries into critical health (25% or less), time spent downed, ending the level down, and a large gap below the level MVP's score. Each input is capped. A small scratch or a close score gap alone is not enough; the setback score must reach 15 points. The MVP cannot also receive OOPS CHAMP. If nobody else qualifies, the display says NONE. This is a lighthearted summary of measured setbacks, not a judgment about why they happened. Solo play has no winner/loser ranking. Only the current level's records are used; there is no special late-join filter. Deaths in the shop do not enter the level score.

Results appear in the next truck, not over the action during a level. With RepoDeathCounter 1.4.4 or newer, both awards and death counts share one compact scoreboard Canvas. Without DeathCounter, MVP uses a small standalone results-only Canvas. Older DeathCounter versions do not support the shared panel bridge and will show separate panels. The standalone MVP panel is moderately translucent and can be shown or hidden with F8 (configurable under Display / ToggleKey). When both mods are installed, DeathCounter's F8 setting controls the one shared panel instead. The expanded points and category lines in the shared panel require RepoDeathCounter 1.4.6 or newer; 1.4.4–1.4.5 show the shorter award text.

The game updates some default hauling/support points only on the host. Version 0.1.3 no longer uses those host-only totals as scoring fallbacks. Every player, including the host, uses the same local extraction measurements: up to 10,000 raw contribution units per valuable/death head and 100,000 per source per level. These raw input limits are not the displayed 0–100 MVP points. The host measures healing, combat and stuns for all players. Combat excludes environmental and unattributable damage. Some weapon or enemy mods may deal damage without a traceable player-attributed collider; this is not guessed. The mod does not provide anti-cheat against a modified client.

Version 0.1.2 fixed the invalid Photon event codes used by 0.1.1 for guest reports and result broadcasts. Version 0.1.3 fixes a host-only hauling cap bypass and removes the unequal native support fallback. The host log identifies missing reports and now records every player's raw inputs and category points once per level. Every player needs RepoLevelMVP 0.1.3 for a complete multiplayer ranking; installing it only on the host cannot collect the guests' local hauling, damage, or survival data.

This 0.1.3 candidate has passed 60 scoring/measurement checks, including 1,000 generated 2–16-player host-role comparisons, and builds against the installed game assemblies. These are automated input-policy tests, not a live multiplayer playtest. The earlier 0.1.2 solo/UI test does not certify this new build. Real multi-account play, host migration, and a live 7+ player lobby still need testing. All players must update together because the scoring protocol changed. Quit the game before replacing a DLL; this candidate is not installed automatically.

日本語

各レベル終了後、次のトラックでMVPと「やらかし王（OOPS CHAMP）」を表示します。 MVPの合計点、高得点の項目を最大3つ、次点を最大2人、やらかし王の別計算の点数も表示します。 単体で使う場合の依存MODは BepInExだけです。全員の結果を正しく出すには、ホストと参加者全員に導入してください。 報告が届かない参加者を0点扱いせず、結果を「DATA INCOMPLETE」とします。

運搬、部屋の発見、価値品の発見、死体の救助、仲間の回復、敵への実ダメージ、 敵のスタン、生存の8種類の行動・状態を区別します。さらに複数の役割を果たした人には 小さな汎用性ボーナスを付けます。参加者の運搬・救助は本人の記録から取得し、 回復・戦闘・スタンはホスト側で確認します。活動がなかった項目は除外して重みを 再配分し、生存しているだけではMVPになりません。

0.1.3では、ホストだけ運搬点の上限を迂回できていた問題を修正しました。 ホスト専用のゲーム内運搬・支援点を補完に使わず、全員に同じ測定方法と上限を適用します。 救助や仲間の回復は引き続き採点します。運搬・救助の測定値の上限は1個10,000、 各項目1レベル100,000で、画面に出る0〜100のMVP点数とは別の値です。 レベル終了時、ホストのログに全員の行動記録と項目別の点数を1人1行で残します。

やらかし王はMVPとは別計算です。レベル中の死亡、実際に失った体力、被弾回数、 大きな一撃の回数、残りHP25%以下への突入、倒れていた時間、終了時に倒れていたか、 そのレベルのMVP点数との差を使います。各項目に上限を設け、軽い一撃や僅差の 最下位だけでは選びません。MVP本人はやらかし王の候補から外し、ほかに十分な 該当者がいなければ「NONE」です。これは測定できた出来事の冗談めいた表彰で、 原因や責任を断定するものではありません。途中参加による特別な除外はなく、 そのレベル中の記録だけで判定します。ショップでの死亡は対象外です。 ソロでは順位を付けません。

DeathCounter 1.4.4以降と併用すると、同じトラック内パネルにまとめて表示します。 DeathCounterなしでも半透明の単独パネルで動作し、F8キーで表示を切り替えられます。 両方導入した場合はDeathCounter側のF8設定で共通パネルを切り替えます。 この版は候補版です。 0.1.2の通信修正を含みます。正確な順位を出すには、ホストと参加者全員が RepoLevelMVP 0.1.3を導入してください。旧版との混在を防ぐため通信の版も更新しています。 60項目の自動テストとビルドは通っていますが、新版の実際の友達とのプレイ、 ホスト交代、7人以上の実ロビーはまだ未検証です。プレイ中のDLLは差し替えず、 ゲームを終了してから全員で更新してください。

Bug reports & requests / 不具合・要望

Please use the REPO Mods – Bug Reports & Requests survey and identify RepoLevelMVP in the details. 不具合・要望はREPO Mods – Bug Reports & Requests アンケートを使い、内容欄に RepoLevelMVP と記載してください。

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.

0.1.2 candidate

• 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.

0.1.1 candidate

• 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.

0.1.0 candidate

• 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.