Mog or Die compares Height, Face, Frame, and Bodyfat in MOG BATTLES. The developerās public description names all four and assigns one growth item to each. It does not publish a battle formula, stat cap, tie rule, or universal ranking, so the reliable strategy is to understand direction, keep the profile balanced, and read the live comparison before risking a long run.
Official stat directions
Do not normalize Bodyfat into the same ālargest number winsā assumption used for the visual growth stats. The official verb is lower. The comparison screen may present direction clearly, but only the current game UI can establish how the result is scored.
Read the live stat panel
Before collecting, record the four values and any labels, bars, arrows, colors, or rank markers beside them. Take one ordinary growth item and compare only its named attribute. If several values change, a timed boost, Genetics choice, Ability, event, or zone effect may be involved.
Repeat the same pickup twice in the same server before writing down an increment. If the changes differ, check for a Golden variant, active 2Ć Progress timer, server event, or visible multiplier. Exact increments should always include the build date and conditions; they should not be copied from a different simulator.
The avatar can be a helpful visual reminder, but a larger model does not prove that Face or Frame moved by the same amount. Trust the labeled values and the battle comparison over appearance alone.
Balance versus specialization
Balanced progression is the safest default because every official battle description names all four attributes. If one stat is far behind, raise or lower it in the advertised direction before accepting a close challenge. This reduces dependence on an unknown weighting formula.
Specialization becomes reasonable only when the live comparison repeatedly shows how separate wins are counted. For example, a result screen might reveal individual categories, a combined score, or another rule. One victory is not enough to identify the rule because the opponent may differ in several stats at once.
Run controlled comparisons with a willing player only if both accounts accept the risk. Change one stat while keeping the other three stable, use the same server, and record the displayed result. Never ask another player to sacrifice a valuable run without clear agreement.
How stats meet MOG BATTLES
Open the comparison and read every row before confirming when the UI permits. Note which values belong to you, which belong to the opponent, and whether lower Bodyfat is visually marked as favorable. If a challenge begins instantly, inspect a low-stakes NPC or fresh run first.
After the result, the winner chooses SPARE or MOG. The result itself and the fate choice are separate decisions. A stat advantage determines the winner under the gameās current rule; SPARE or MOG determines what happens to the defeated run and whether the winner takes MogPoints.
Use the battle guide for the complete flow. When reporting a surprising result, include all four values, any modifiers shown, opponent type, server date, and outcome. āMy Height was higherā is not enough to prove the game ignored the other three attributes.
Effects that can confuse a comparison
2Ć Progress
The current code advertises a timed multiplier. Confirm which pickups change during the timer rather than assuming battle rewards or every stat action are doubled.
Genetics
Genetics are chosen for every run. Read their visible effect text and record the choice because it may change how two otherwise similar runs behave.
Abilities
Abilities can be unlocked and rolled. Do not attribute an unusual battle result to base stats until you have checked equipped effects.
Risk and world systems
Risk Zones promise better rewards, and weather or world events change. Record the location and event state when measuring pickups.
Golden collectibles may also behave differently from ordinary items, but the public description does not list their values. Separate a Golden pickup from your ordinary-stat test.
Diagnose a stat that does not move
First verify that the object is the advertised item and that the pickup completed. Wait for the UI, then compare the correct attribute: Milk with Height, Hammer with Face, Picture Frame with Frame, Water with Bodyfat. Check whether Bodyfat moved downward rather than upward.
If nothing changes, look for a cap message, cooldown, inventory state, active prompt, or server lag. Rejoin a fresh server and repeat with a starting screenshot. Do not declare a new cap from one failed pickup, because another player may have collected it or the client may have shown a stale model.
What still needs live measurement
The exact starting values, increments, caps, tie resolution, combined battle formula, effect of Golden variants, interaction with 2Ć Progress, Genetics modifiers, Ability modifiers, and reset behavior are not published in the official description. They should be treated as current-build observations when reliable evidence becomes available.
You can still progress effectively without those numbers: learn the four mappings, keep the profile readable, correct the obvious weak attribute, and avoid high-stakes battles whose comparison you cannot interpret.
Source and confidence
Stat names, item mappings, and their participation in MOG BATTLES are Official, checked August 27, 2026. Formula and value details need in-game testing.