Candy Kingdom Defense Infinite Problems: Entry, Waves and Results
Quick answer
- Entry issue: Read the condition shown by the actual entry rather than assuming a campaign clear and Infinite share the same access rules.
- Run issue: Separate a defense ending at a wave from a missing result or reward; each needs a different description.
Identify when Infinite stops working
A Candy Kingdom Defense Infinite problem can happen before entry, during the defense or after the run.
The overview below provides the game and mode context for describing the problem clearly.
Name that moment first. A button that will not start the activity is different from enemies defeating a squad, and both are different from a result that does not appear as expected.
Read the entry condition before changing development
If you cannot enter, inspect the condition or message shown by the mode's actual entry. Confirm you are selecting Infinite rather than a campaign stage or Dungeon Train Challenge. Buying a trait roll or leveling an unrelated hero is not a direct response to an entry message.
If the activity begins but the defense ends, treat that as a squad problem first. Review the opening, coverage and the point enemies survived. A run ending at a wave is compatible with an endless-wave mode; it does not by itself show that the entry system failed.
Keep score and rewards as separate questions
For a result problem, describe the wave reached, which display is missing and which reward balance you expected to change. Do not assume the score is simply the gem reward or that every campaign result rule also applies to Infinite.
The Infinite Mode guide explains the endless structure and documented reward context. For a persistent interface issue, a concise description through the verified developer community is more useful than repeatedly changing the collection. Keep the failing action and the displayed message together so the report identifies what needs attention.