Zad Archery Troubleshooting: Updates, Symbols, Rings, Save, Input, and UI Fixes

Current update state first

Before deleting saves or rebuilding your route, confirm the game is updated. Patch 1.0.2 is the launch-fix baseline for gems, Guardian, King achievement, and resolution symptoms. The September 4 Mega Update is the current progression baseline for Symbols, Preferred Job, Ring System, Endless, Portal currency, and the removed Level 50 cap.

Patch 1.0.2 lists four fixes that directly affect common troubleshooting reports:

Sources: Steam Patch 1.0.2 announcement, SteamDB Patch 1.0.2 record, the September 4 You Are Right! update, and the Steam Community hub. For ongoing source tracking, open Release Status.

Choose your symptom

• Gems did not count while farming an older level → update to Patch 1.0.2 first.
• A Guardian is missing or King is locked → update and restart before assuming the save is broken.
• A later Guardian, Wave 50, or King route is blocked → use the Guardian Missing and King Guide after the Patch 1.0.2 restart check.
• Defeat the King did not unlock → check Steam connectivity and Patch 1.0.2.
• Mega Update not appearing → verify the Steam build updated before assuming the save is broken.
• Symbols not appearing → check whether the Symbol System has unlocked in your current progression and whether the update is installed.
• Ring System not appearing → remember Portal currency is tied to after level 30 in the September 4 update.
• Level 50 cap still showing → verify the Mega Update first, then record the exact level, screen, and build state.
• Selling feels delayed → check Selling items.
• Equipped-item text runs off-screen → check Clipped tooltips.
• The first click or keypress is ignored on macOS → check macOS input.
• Demo progress did not appear → read Demo to full game before deleting anything.
• Want a fresh Demo save → follow Reset Demo progress below.

Launch-week community reports, September 4-5

The official Patch 1.0.2 note confirms only the gem-counting, Guardian restoration, King achievement, resolution-list, and small-bug fixes named above. The Steam Community hub then showed several September 4-5 player reports. Treat the rows below as triage signals, not as official universal bugs unless a later developer post confirms them.

Sources: Steam Community hub, Patch 1.0.2 announcement, and the September 4 You Are Right! update.

Mega Update systems not appearing

The September 4 update officially names the Symbol System, Preferred Job, Ring System, Portal currency after level 30, Endless farming, and Level 50 cap removal. If those systems do not appear in your build, keep the diagnosis reversible:

Unknown means this wiki does not have enough local evidence to name the cause. Preserve the save, capture the current screen, and avoid reset steps unless a developer confirms they are required.

Guardian not spawning

Patch 1.0.2 directly names a Guardian bug: a Guardian could sometimes never appear, which locked the King route. The patch note also says any missed Guardian is restored on restart.

Use this order before rebuilding a save:

1. Confirm Steam has updated Zad Archery to Patch 1.0.2 or later.
2. Close the game completely instead of only returning to a menu.
3. Relaunch, load the save, and check the Guardian route again.
4. If the Guardian is still missing, record the wave or route state where it should appear and report that exact save state in the Steam Community hub.

Do not invent a spawn formula from this patch note. The confirmed fix is restart restoration after the patch, not a published Guardian schedule.

For the later Guardian, King, Wave 50, achievement, and endgame route, use the Guardian Missing and King Guide. It keeps confirmed Patch 1.0.2 behavior separate from September 4-5 community reports.

Fourth or fifth Guardian missing

Treat a missing fourth or fifth Guardian as the same confirmed Guardian class of issue unless a newer patch separates it. The reliable action is still: update, fully restart, and recheck the route that leads to the King.

If only one later Guardian remains missing after restart, preserve the save. A partial route failure is more useful to report than a deleted or overwritten save, and public notes do not confirm that replaying lower waves forces a specific Guardian to spawn.

King achievement not unlocking

Patch 1.0.2 says Defeat the King was fixed for the case where Steam was unreachable. If you defeated the King but Steam did not show the achievement:

1. Update to Patch 1.0.2 or later.
2. Keep the Steam client online before repeating the fight.
3. Open the Steam achievement page for app 4412000 and refresh the achievement state.
4. If the in-game King defeat happened while Steam was offline, treat the missing unlock as a known launch-window risk and check the Community hub before spending another long run.

The patch confirms a Steam connectivity bug for the achievement. It does not confirm hidden alternate King requirements.

Lower-wave gems farming

Patch 1.0.2 says monster gems now count when farming a level below your highest. If lower-wave farming still looks wrong:

1. Update first.
2. Run one lower wave where monster gems should be visible.
3. Compare the gem counter before and after the run.
4. If the value still does not move, capture the current highest level, the lower level farmed, and the counter result.

Use Mining and Gathering for progression context, but avoid unverified gem-rate tables until a source or repeatable sample supports them.

Resolution problem

Patch 1.0.2 added your screen's own resolution as the first settings option. If the UI is clipped, text is off-screen, or the equipped-item panel is hard to read, reopen settings after updating and choose that native option before trying broader display workarounds.

If the native resolution still clips the interface, switch fullscreen/windowed mode once, take a screenshot, and report the resolution, display scaling, and platform. The patch confirms an option-list fix, not that every clipping report has the same cause.

Selling and equipment controls

For selling, equipping, or comparing gear, follow the control hint shown in your current build. A Demo-era player report mentions Ctrl + Shift + right-click for selling and says it can feel delayed, but this wiki does not promote that as a universal full-release shortcut.

Before reporting an equipment-control issue:

1. Confirm the selected item is not equipped or locked by the current screen.
2. Send the sell or equip input once and wait for the inventory to update.
3. Check Controls and Inventory for the Demo versus release boundary.
4. Include the item state, platform, and exact input when posting a bug report.

Demo save question

Demo reset evidence is stronger than Demo transfer evidence. The developer-confirmed Demo action is deleting zad.su from Unity's persistent data path to reset Demo progress. The official material reviewed here does not confirm that a Demo save transfers into the paid Steam release.

Keep the Demo save backed up, launch the full Steam app separately, and do not rename or move zad.su as a migration step unless the developer publishes a transfer method for your platform.

Known-issue evidence matrix

This table separates Demo-era instructions from full-release reports. “Community report” means the symptom is documented by a player but is not presented here as a developer-confirmed universal bug.

Do not apply a Demo file workaround to the full release unless the developer confirms that the same file and behavior are used in your build.

Selling items feels delayed

A player describes the Demo control as Ctrl + Shift + right-click and reports that it can feel delayed. If the input does not work:

1. Read the control hint shown for the selected item in your build.
2. Confirm the item is not equipped.
3. Send the input once and wait for the inventory to update.
4. If the game still ignores it, record the platform, item state, and exact input before reporting the issue.

For a fuller controls boundary, open Controls and Inventory. This wiki does not treat the Demo selling report as a confirmed full-release shortcut unless the live build or developer confirms it.

Equipped-item tooltip is clipped

Current Steam topics mention equipped armor tooltips extending beyond the screen edge. Try these steps:

1. Update to Patch 1.0.2 and check whether your screen's own resolution appears at the top of the settings list.
2. Switch out of fullscreen or choose a different supported resolution.
3. Reopen the inventory and move the cursor to compare the item again.
4. Capture the resolution and the clipped panel in a screenshot.
5. Report the display mode and resolution in the Steam discussion if the problem remains.

macOS first input is ignored

A launch-day topic reports the first click or keypress being ignored in the full macOS version while the Demo worked normally.

1. Click once inside the game window to give it focus.
2. Repeat the intended input after focus is established.
3. Note whether the issue happens after every window switch or only after launch.
4. Include macOS version, input device, fullscreen state, and reproduction steps in a report.

Demo progress and the full game

Players asked whether Demo progression carries into the definitive version. The captured developer replies do not provide a clear yes-or-no transfer rule.

Before changing files:

1. Confirm that you launched the full app rather than the web or Steam Demo.
2. Check whether the full game created its own save after the first launch.
3. Do not move or rename zad.su unless the developer gives a transfer path for your platform.
4. Keep the old Demo save backed up while checking official announcements or the Steam discussion.

Deleting the Demo file is a reset action, not a transfer method.

Reset Demo progress

The developer gave one concrete reset method for the Demo: delete the zad.su file from Unity's persistent data location.

1. Close Zad Archery completely.
2. Open the platform-specific folder returned by Unity's persistentDataPath.
3. Find zad.su.
4. Back up the file if you may want the save again.
5. Delete zad.su, then relaunch the Demo.

Unity uses different locations on Windows, macOS, and Linux. Use the Unity persistent data path documentation to identify the correct location for your platform. The original developer reply is in the Steam reset discussion.

For release availability and the difference between Demo and full game, open Release Status.