Mog or Die Battles Guide

Battles are the point where a Mog or Die run becomes valuable or vulnerable. The official description says NPCs and real players can enter MOG BATTLES, where Height, Face, Frame, and Bodyfat are compared. A winner then chooses SPARE or MOG. SPARE preserves the defeated player’s run; MOG erases that run progress and awards MogPoints to the winner.

The same public description also names the server’s MOG KING, large player bounties, special NPCs, and bosses. It does not publish the comparison formula, challenge controls, King requirements, bounty payout, boss roster, or exact reset boundary. Approach each as a distinct objective and read the live interface before committing progress.

Battle activity matrix

Special NPCs and bosses belong in the same battle family but need their own record because a named encounter can use routes, phases, or rewards beyond an ordinary comparison.

Prepare all four stats

Milk raises Height, Hammers improve Face, Picture Frames build Frame, and Water lowers Bodyfat. Check each value before accepting a challenge. The public description lists all four in the comparison, so a run that ignores one attribute depends on a formula that has not been confirmed.

Keep Bodyfat direction in mind: lower is the advertised goal. Do not compare profiles by adding four raw numbers unless the result screen explicitly uses a total. Colors, arrows, row wins, or other live indicators are more reliable than a formula copied from another game.

Use the stats guide for controlled comparisons. If you are testing one attribute, choose a low-value run and a willing opponent, change only that field, and record both full profiles. Never use a stranger’s erased run as an unannounced experiment.

Read the challenge before confirming

Identify whether the opponent is an NPC or player and whether the challenge can be declined. Read any warning about the run, MogPoints, bounty, or King status. On a touch screen, avoid tapping through a prompt while moving the camera. On keyboard or controller, use the action label shown by the current game rather than an unverified binding.

Check your current run value: time spent, active 2× Progress, rare Golden collectible, desired Genetics, Ability state, and any reward you have not yet verified. The more you are carrying, the more information you should demand from the comparison before accepting.

If the game starts the battle without showing stats, use an NPC or fresh run to learn the flow. A long run is not the right place to discover that a challenge locks instantly.

Decide between SPARE and MOG

The fate choice is more than a reward button. It affects whether another player keeps the current run. Respect cooperative testing agreements and do not describe SPARE as a loss when the goal was to learn the formula without destroying progress.

MOG KING and bounty decisions

The MOG KING is a server-specific title in the public description. Before pursuing it, find the current holder or marker and read any requirement shown. Do not assume it belongs to the highest single stat, largest total, biggest bounty, most MogPoints, or last battle winner. The MOG KING guide gives a verification route without choosing an unsupported rule.

Bounties identify players as hunt targets, but the creation and settlement rules are not public. Confirm the displayed value, target, server, and action required for credit. A large bounty can attract several players, turn a safe item route into a contested area, and produce disputes about assists. The bounty guide separates target selection from payout evidence.

If both systems point to the same player, do not assume one reward includes the other. Record King status and bounty separately before and after the battle.

Special NPCs and bosses

The official description confirms their existence but gives no public roster. Use the bosses guide as a currently documented encounter index: it explains how to decide whether an entity is an ordinary comparison NPC, special NPC, or boss and which fields to capture.

Do not label a large model as a boss without a nameplate, objective, phase, or reward evidence. Likewise, do not promise a drop because an object appeared nearby. Record the location landmark, entry condition, displayed name, phase change, result screen, and item received.

Prepare a boss attempt differently from a player comparison. Stabilize the four stats, read equipped Ability and Genetics effects, preserve useful rewards, and decide whether leaving or losing affects the run. If the encounter is inside a Risk Zone or event, record that context too.

Recover after being MOGGED

Wait for the reset to complete. Record Height, Face, Frame, Bodyfat, MogPoints, Ability, Genetics, Finisher, bounty, King marker, Daily claim, and Playtime timer. “Erase their progress” does not publicly define every account field, so this before-and-after check is essential.

Rebuild on a safe ordinary-item circuit rather than rushing into revenge. If a high-bounty player or King controls the route, move elsewhere or join another server after checking what leaving preserves. A repeat loss gives little new information when the profiles have not changed.

Battle FAQ

Are NPC and player battles identical?

Both are named MOG BATTLES with four-stat comparisons, but no public source proves identical entry rules, formulas, stakes, or MogPoints payouts.

Does the highest Height always win?

No official formula says that. All four stats are compared, and Bodyfat has a lower-is-better direction.

Can SPARE protect my own run?

SPARE is the winner’s choice for the defeated player. If you lose, the opponent chooses. The live result screen decides the available action.

Source and confidence

MOG BATTLES, four-stat comparisons, SPARE/MOG outcomes, MogPoints, MOG KING, bounties, special NPCs, and bosses are Official, checked August 27, 2026. Their formulas, requirements, lists, and rewards need in-game testing.