Answer three questions about your account and this session, and get the planning order Divine Battlegrounds' documented rewards support — codes first, then the goal you picked.
Claim listed codes first, then spend rewards only after you know which upgrade path stays useful.
Use exact game rates when they are available. Until then, treat this as a conservative planning helper.
Divine Battlegrounds is a PvP battlegrounds game: up to 15 players per server, melee strings on left click, block on F, dash on Q, ultimate on G. The developer publishes no damage or health numbers, so any calculator promising "your exact build damage" would be inventing inputs. What the game does document — and what this calculator is built on — is a set of one-time free gains and a dated promotion rhythm: character codes, emote codes, rotating title-tag windows, and a combat system whose inputs are written into the official description. Those facts are enough to plan a session properly: claim the free gains, spend the boost window on the goal you picked, and practice the two or three inputs that goal depends on.
The planner applies a fixed decision table: stage filters which advice applies, goal picks the branch, and the boost toggle decides timing.
Early-game accounts get the codes-and-basics branch, because the documented free gains (KJ via code, emotes via code) are stage-independent — a new account claims them on minute one. Mid and late game shift weight to repeatable goals, where your existing roster and practice matter more than one-time rewards.
Four branches: codes-first (claim and verify), farm (repeatable value before rare choices), boss (ultimate practice windows), and PvP (compare mobility, burst, and cooldown control rather than copying a farming build). Each branch names the inputs from the official control table that the goal depends on.
The toggle represents a live title-tag promotion or event (like the September [WORLD EVENT] or FREE INVINCIBLE windows). Boost-active moves major attempts into the window; boost-off schedules them behind preparation, because a window that closes mid-attempt is the classic wasted grind.
Rewards in this example are tracker-documented, checked 2026-10-03.
| Step | Input state | Planner output and why |
|---|---|---|
| 1. Claim before anything else | Early game, codes-first, no boost | Redeem the reported set from the codes page via the Twitter-icon box: FREEKJ grants the KJ character, FREEEMOTES grants emotes, FREEMARK grants a Mark. Three documented unlocks in about two minutes of menu work. |
| 2. Learn the inputs on the new character | Early game, farm goal | The planner's farm branch says repeatable value first: run the control table in order (double-tap W, Q dash, F block, Q-while-ragdolled evasive) until each is reflexive, then left-click strings on a training target. |
| 3. Save ultimates for a window | Mid game, boss goal, boost toggled on | With a promotion window active, the planner moves ultimate attempts into it: G-ultimate practice on your claimed KJ while the window pays extra. Without a window, it says prepare first — the same attempt costs more outside a promotion. |
Interpretation: the outputs are an ordering, not a promise. If a tracker dispute means a token fails in-game (the codes page flags SORRYFORDELAY and FUN as disputed), the plan loses nothing — step 1 simply ends and steps 2–3 still apply. That is the property a planning order should have: robust to any single code expiring.
Per-code rewards as documented by Roblox Den, checked 2026-10-03. Full status history lives on the codes page.
| Code | Documented reward | Status |
|---|---|---|
| FREEKJ | KJ character | Reported active |
| FREEEMOTES | Emotes | Reported active |
| FREEMARK | Mark | Reported active |
| ZOMBIEMAN | Rewards (unlabeled) | Reported active |
| ZOMBIEMANULTIMATEWHEN | Rewards (unlabeled) | Reported active |
The remaining reported tokens, their dispute status, and the four-tracker comparison are on the codes page.
It is a decision helper, not a payout predictor. You tell it your progress stage, your current goal (claiming codes, farming, boss-style ultimate practice, or PvP), and whether a boost window is active, and it returns the planning order that matches those inputs. Every recommendation is built from documented game facts — code rewards, the official controls, and the dated update record — never from invented rates.
Because codes are the only documented free-character channel. The FREEKJ code is reported by Roblox Den as granting the KJ character outright, and FREEEMOTES grants emotes — both checked 2026-10-03. In a PvP battlegrounds game, a free character unlock is the cheapest power gain available, so any plan that starts elsewhere wastes the head start.
The developer advertises promotions by rotating the experience title — [WORLD EVENT], [BIG UPDATE], [MONSTER, COSMIC, JK & KJ] have all appeared — and FREE INVINCIBLE ran as a title promotion in September 2026. If the current title advertises a free character, form, or event, treat that window as active and set the toggle accordingly.
No. The developer publishes no stat table and no rank thresholds, so no tool on this site can compute them honestly. The calculator plans the order of your work; your own match record is the only source for performance numbers.
The planning logic is stable, but the facts under it are dated. After every titled update, re-check the codes page for new or expired tokens and the updates page for new title promotions — a new code can reorder the codes-first recommendation for your account.
Claim and verify the free gains before any grind.
Repeatable value before rare choices, on a session clock.
Ultimate practice windows and mobility comparisons.
