If a Diablo IV War Plan is not updating, first verify the selected plan, read its current objective literally, and complete that objective in the displayed order. Then confirm that your character is in the same Seasonal/Eternal, Hardcore/Non-Hardcore, and Normal/Solo Self-Found partition as the progress you expect to see, and make sure the game is patched. Blizzard has documented real failures involving reward claims, missing activity credit, and achievement progress, so a run that looked valid can still leave the chain stuck. The checks below separate an order or display mistake from a reward-state or backend progression problem and show what information to collect if support is needed.
What are War Plans supposed to track?
War Plans are ordered playlists of up to five activities selected from six endgame modes: The Pit, Infernal Hordes, Helltides, Nightmare Dungeons, Lair Bosses, and Kurast Undercity. You arrange the order and play the chain to earn progression toward a dedicated activity tree. Blizzard’s description is: “Setup the activity order for War Plans and play through them seamlessly in a single chain.”
That “single chain” wording is the key to troubleshooting. Completing a familiar activity is not enough if it is not the currently required node, if it was done before an earlier node, or if the objective includes a condition that was not met. The War Plan screen, the activity objective, and the reward state must all agree before the next node advances.
What should I check first when a War Plan will not move?
Work through these checks in order. They distinguish an incorrect plan or objective from a genuine registration failure without spending resources on blind retries.
- Confirm the active plan. Open the War Plans screen and identify the plan marked as selected. A community report describes a display-only or “false” plan that appeared not to update while another selected plan was progressing. Treat that report as anecdotal: use the selected-plan indicator and the current objective, not a stale-looking list entry, as your reference.
- Read the objective word for word. Look for requirements such as a particular mode, dungeon type, boss, modifier, wave count, cinder spend, or another completion condition. “Run a Nightmare Dungeon” and “complete a Nightmare Dungeon with a specified condition” are different tasks; ordinary completion may not satisfy the latter.
- Follow the sequence shown. The order is part of the requirement. Blizzard’s FAQ gives the example of a plan listing Helltide followed by a Nightmare Dungeon: completing the Nightmare Dungeon first does not award that plan’s credit.
- Finish the activity and its reward flow. Stay in the completion screen long enough for rewards and progression to register. Do not disconnect, close the client, or otherwise interrupt reward claiming; Diablo IV patch notes 3.0 identify a disconnect during that step as a possible progression blocker.
- Check the character partition. Shared progress is limited to characters matching all three current partitions: Seasonal or Eternal, Hardcore or Non-Hardcore, and Normal or Solo Self-Found. A character can be in the same season as another character and still be in a different partition.
- Update the game client. Patch 3.1 notes include fixes for activities that failed to grant rewards or progress achievements, plus several War Plan, party, modifier, and teleport issues. Test only after the installed client is current so an already-fixed defect is not being reproduced on an old build.
Why can a completed activity fail to count?
The symptom “I finished the run, but the node did not change” can come from different layers. Use the comparison below to decide what to inspect rather than assuming every case is the same bug.
| What you see | Most useful distinction | What to verify | What the evidence establishes |
|---|---|---|---|
| Activity ends with no node progress | Order versus objective | Selected plan, current node, exact condition, and whether an earlier node was skipped | Blizzard explicitly documents order-sensitive credit, including Helltide before Nightmare Dungeon. |
| Rewards or the next node are missing | Completion flow versus gameplay | Whether the client disconnected or closed while rewards were being claimed | Patch 3.0 records a progression blocker tied to disconnecting during reward claims. |
| Rewards appear absent and achievements do not advance | Activity registration | Client version, activity type, party state, and before/after screenshots | Patch 3.1 says War Plan activities could fail to grant rewards or achievement progress and lists subsequent fixes. |
| Only one character appears stuck | Partition versus planner display | Season, Hardcore status, Normal/SSF status, and the character’s own planner | Shared progress requires matching all three partitions; point allocation remains character-specific. |
| Plan appears unchanged while another screen moves | Visible UI state versus active plan | Which plan is selected and whether the displayed entry is stale | A community report describes this pattern, but it is not an official diagnosis or universal fix. |
When the activity is valid but the objective is not
A mode can be correct while the node’s condition is not. For example, a boss kill may need a listed boss, a Helltide may require a cinder spend, or an Infernal Hordes node may require a specified wave or modifier. The objective text is the authority; do not infer that any run in the same mode qualifies.
When the run was completed out of order
War Plans are not a checklist that awards credit whenever each activity is eventually done. The chain evaluates the currently required step. If you complete a later activity first, doing the earlier one afterward does not necessarily retroactively credit the skipped step.
When party play changes the state
Record whether the run was solo or in a party. Patch 3.1 includes a fix involving party completion experience, and its broader activity fixes show that multiplayer state can be relevant to registration. This does not prove that every party-related report has one cause, but it makes party status important when documenting a failure.
What if War Plan rank is stuck at 9/10?
A 9/10 display is a report, not proof of a universal 9/10 bug. Before treating it as a permanent block, verify that every activity tree is actually complete, that no points remain unallocated, and that the plan you are viewing is the selected plan rather than a stale display entry.
Also separate rank progression from planner allocation. Reputation or shared progress can carry between characters in the same partition, while each character has a separate planner for assigning points. An apparent shortfall on one character may therefore be an allocation or display mismatch rather than missing account progress.
Why are rewards missing or is the next activity locked?
Reward registration is a known failure point. Blizzard’s Diablo IV patch 3.0 notes say War Plan progression could be blocked when a player disconnected while claiming rewards. Later, patch 3.1 notes state that War Plan activities could fail to correctly grant rewards or progress achievements. Those entries confirm that downstream progression can depend on a successful reward transaction, not merely on reaching the end of the activity.
If the reward never appeared, note whether the activity completion screen was shown, whether the client disconnected or crashed, and whether the next node unlocked. Do not present a community workaround as guaranteed recovery: the published material does not provide one universal restoration procedure for every account-specific reward-state failure.
Why does an alt character show different War Plan progress?
Compare the three partition fields, not just the season label. The current sharing rules are:
| Partition | Must match for shared progress | Example mismatch |
|---|---|---|
| Season state | Seasonal with Seasonal, or Eternal with Eternal | A Seasonal character will not share this progress with an Eternal character. |
| Mode | Hardcore with Hardcore, or Non-Hardcore with Non-Hardcore | A Hardcore alt is separate from a Non-Hardcore character. |
| Self-Found status | Normal with Normal, or Solo Self-Found with Solo Self-Found | A Normal character does not share the same partition as an SSF character. |
Characters that match all three partitions can share the relevant reputation or progression, but the planner used to allocate points is character-specific. Seeing different allocated nodes on an alt is therefore expected even when the underlying shared progress is available.
Which War Plans bugs did Blizzard fix?
The official patch history confirms that tracking failures have existed as software defects, while also showing why an old report should not be treated as a diagnosis for every current case.
- Patch 3.0: progression could be blocked after a disconnect during reward claiming.
- Patch 3.1: fixed an issue where War Plan activities did not correctly grant rewards or progress achievements.
- Patch 3.1 activity fixes: the notes also list corrections for incorrect chests, modifiers persisting after an activity, party completion experience, Infernal Hordes entry and voting, Nightmare Dungeon seasonal-affix behavior, and several activity-specific interactions.
These fixes are the reason to update before deeper troubleshooting. They do not establish that every current stuck-plan report has the same cause, nor do they guarantee that every account-specific state can be repaired automatically.
How should I report a War Plan that remains stuck?
If the active plan, objective, order, partition, and client version all check out, make a precise record before changing the plan or repeating content. Include:
- platform and launcher;
- season, character name and class, and Seasonal/Eternal, Hardcore/Non-Hardcore, and Normal/SSF status;
- the exact War Plan sequence and current objective text;
- activity name, difficulty, party or solo status, and completion time;
- whether the game disconnected, crashed, or was closed during reward claiming;
- screenshots or video of the objective before and after the run;
- whether the reward appeared and whether the next node unlocked.
This information lets a support or bug-report reader distinguish an order mismatch from a partition mismatch, a visual error, and a reward/backend failure. Keep the original wording of the objective and the sequence; paraphrasing can hide the condition that matters.
Which suggested fixes should I treat cautiously?
Players may suggest creating an alt, abandoning a plan, resetting a dungeon, or repeating the same activity. Those actions can be useful diagnostic experiments, but none is an official universal recovery method in the available guidance. Resetting or abandoning can consume reset currency or alter the current plan, so preserve screenshots and the exact state before trying an irreversible change.
Do not assume that a run is invalid merely because the display is stale, and do not assume that repeating a valid run will repair a backend reward state. First identify whether the failure is in selection, objective completion, sequence, partition, client version, or reward registration.
Frequently Asked Questions
Can I tell whether the War Plan problem is only a display error?
A display problem is more plausible when the selected plan, objective, reward receipt, and next-node state disagree with what one list entry shows. Capture both the War Plans screen and the completion result before changing anything; a community report of a “false” plan is anecdotal and cannot establish that every stale display has the same cause.
Do all characters in the same season use the same planner?
No. Shared progress depends on matching the season state, Hardcore state, and Normal/SSF state, but point allocation is kept in each character’s planner. Two qualifying characters can therefore share underlying progress while showing different allocated activity-tree nodes.
Is repeating the activity the safest way to recover a stuck node?
Not necessarily. If the failure occurred during reward registration, repetition may not repair the missing state, and abandoning or resetting a plan can change progress or consume reset currency. Preserve the objective, sequence, and reward evidence first, then treat any repeat as a diagnostic attempt rather than a guaranteed fix.
What should I save if the game disconnects during rewards?
Write down the activity, difficulty, character partition, approximate completion time, and whether a reward appeared before the disconnect. Screenshots or video showing the objective before the run and the node afterward give a clearer account of a reward-state failure than a message that the plan was simply “stuck.”