Mog or Die Progression Guide

Progression in 🔥HELL🔥Mog or Die is a run-based loop: begin as a small SUB5, collect items that change four visible attributes, challenge an NPC or player in a MOG BATTLE, and decide how much risk to take before the run is erased. The official description names the loop and each item-to-stat pairing, which gives you a dependable route even though exact increments and battle weights are not publicly documented.

Start by learning where your four attributes appear and taking a screenshot or note of the initial values. Collect one item at a time until you can connect the pickup to its result. Build a balanced run before gambling progress against another player, then use MogPoints and claimable rewards only after confirming what the current server says they do.

The four-stat progression map

The Bodyfat direction matters: the public description specifically says Water lowers it. Do not read all four rows as “bigger is automatically better.” A battle compares the attributes, but the public text does not disclose how ties, totals, or unequal advantages resolve. Use the stats guide to interpret the comparison without inventing a formula.

A safe first-run route

Spend the opening minute locating the stat display, nearby growth items, the boundary of any obvious danger area, and the control that starts a battle. Do not accept the first player challenge while you are still reading the interface. NPC battles can also matter, but the official description does not state whether every NPC uses the same stakes as a player.

Collect one Milk, one Hammer, one Picture Frame, and one Water when they are safely available. Check the corresponding stat after each pickup. This confirms that the server build matches the advertised mapping and helps you recognize the pickup model later. Continue with whichever stat is furthest behind in a visible comparison, while keeping enough awareness to avoid a contested Mog Drop or Risk Zone you did not intend to enter.

Before a battle, pause and ask three questions: can you see all four values, do you understand whether the opponent is an NPC or player, and are you willing to lose the current run if the winner chooses MOG? If any answer is no, keep collecting or choose another target. The beginner guide turns that route into a complete first-session checklist.

Decide when to battle

A stronger run is not only a high-looking number. It is a profile you can compare, a route you can repeat, and a risk you have chosen deliberately. Take an early low-investment battle to learn the result screen only when losing the run would be acceptable. Save a longer farming session for after you know how challenges begin and what the winner sees.

SPARE lets the defeated player keep the run. MOG erases the defeated player’s progress and gives the winner MogPoints. Those outcomes are official, but the amount of MogPoints and the exact scope of “progress” require a live check. Cosmetics, account currency, codes, or separately claimed rewards may not follow the same reset rule.

If you are holding a valuable timed boost, rare Golden collectible, or hard-earned run, the expected information from a random battle may not justify the downside. Move toward safer collections, use an NPC comparison if its stakes are clear, or wait until the boost ends. Progression speed means little if repeated avoidable resets consume the whole session.

MogPoints and permanent decisions

The two confirmed MogPoints sources are choosing MOG after a win and redeeming the currently listed code. The code offers 2,500 MogPoints; battle amounts are not public. Read how to get MogPoints for a source-by-source plan and a spending check.

Before purchasing or rolling anything, record the current balance, item name, stated effect, price, and whether the result says it lasts for the run or account. Abilities, Genetics, and Finishers are different systems in the official description, so do not assume a button in one menu changes another. Preserve a screenshot of the confirmation screen when a purchase is expensive or irreversible.

Daily, Playtime, code, and battle rewards

Use the rewards guide to keep these sources separate. A daily claim should not be described as a code reward, and a code timer should not be assumed to pause because a playtime panel does.

Recover from a reset

After being MOGGED, first determine what actually returned to its starting state. Check all four stats, MogPoints, equipped ability, current Genetics, Finisher, claimed rewards, and any visible collection record. Do not immediately spend currency or redeem another reward; establish the new baseline first.

Rebuild with the shortest known safe circuit. Take one of each ordinary growth item, then focus on the weakest visible stat. Avoid rushing back to the same opponent without understanding the comparison. If a bounty, King marker, weather event, or Risk Zone changed the situation, move to a quieter route until the run is stable.

Progression mistakes to avoid

Do not chase a single stat because its number is easiest to raise; all four are named in the battle comparison. Do not carry “higher is better” over to Bodyfat when the official action is to lower it. Do not redeem a timed code before navigating menus. Do not assume every glowing item is Golden, every risky area is a named Risk Zone, or every NPC battle has player stakes.

Most importantly, do not treat an unverified tier list or copied formula as a reason to erase a healthy run. The current public evidence supports a balanced collection route and deliberate battle timing. Exact optimization should follow what your current server displays.

Continue your route

• New player: follow the Mog or Die beginner guide.
• Comparing attributes: use the stats guide.
• Looking for the right pickup: open the growth items guide.
• Building currency: read how to get MogPoints.
• Sorting claim panels: use the rewards guide.

Source and confidence

The item mappings, four attributes, battle outcomes, MogPoints, Daily Rewards, and Playtime Rewards are Official, taken from the Roblox Experience description checked August 27, 2026. Exact values, caps, reset boundaries, menu paths, and reward schedules still need in-game testing.