WuWa Config Patcher

1. Symptom: Shizuku is Running, but App Shows "NONE" or Requests Access

Likely Cause: Shizuku binder service connection dropped or permission prompt was not granted to WuWa Config Patcher.

Access Method: Shizuku (Wireless ADB)

Fix Procedure:

1. Go to the Settings tab and check the Elevated Access Status card.
2. Tap Grant Access or the refresh button next to the Shizuku setup wizard.
3. If it fails, open the Shizuku app, revoke permissions for WuWa Config Patcher, force stop the patcher, and reopen it to re-trigger the permission binder prompt (via rikka.shizuku.api).
4. Run App Doctor in Utilities > Common (AppDoctorDialog.kt) to auto-verify permissions.

2. Symptom: Game Stuttering, Black Screen, or Crashing After Patching

Likely Cause: Unstable CVar combination, unsafe Garbage Collection (gc.*) tweaks, or incompatible shader cache.

Access Method: Shizuku / Root / Manual

Fix Procedure:

1. Navigate to Utilities → Common Subtab.
2. Tap the primary red Revert to Vanilla button.
3. Confirm the 3-step triple guard prompt. This deletes modified Engine.ini, DeviceProfiles.ini, and Scalability.ini files so Wuthering Waves regenerates factory defaults upon next launch.
4. To clear corrupted compiled shaders, go to Settings > Danger Zone > Delete Shaders and clear Vulkan/OpenGL shader caches.

3. Symptom: Access Badges Explained

• ROOT — Red badge (#E35D6A): Direct elevated libsu shell execution.
• SHIZUKU — Green badge (#47D764): Primary wireless debugging ADB backend.
• AXMANAGER — Blue badge (#38BDF8): Axeron community manager service binder integration for elevated IPC execution.
• SHIZUKU_UNAUTHORIZED — Orange badge (#F7C948): Shizuku binder running, permission pending.
• NONE — Gray badge (#A8B4AF): No elevated backend available.

4. Symptom: Editor Lines Flagged in Vibrant Red (#FF2222)

Likely Cause: Misplaced CVars (e.g., placing r.* rendering settings under incorrect section headers) or illegal CVars= prefixes in Engine.ini.

Fix Procedure:

1. In the Live Config Editor, tap Save.
2. Select Auto-Fix Sections in the warning prompt.
3. The app automatically routes variables to canonical section headers (e.g. s.* to [/Script/Engine.StreamingSettings]) and strips invalid CVars= prefixes via CVarSectionGuard.kt.

5. Symptom: How to Verify If Applied CVars Executed in Game

Access Method: Shizuku / Root

Fix Procedure:

1. Go to Utilities > Decrypted Log Explorer and decrypt your active game log.
2. Go to the Advanced Subtab and tap Analyze Config (CVar Analyzer).
3. The ConfigAnalysisDialog.kt cross-checks your INI parameters with decrypted Client.log output to report exact status: APPLIED, FAILED, or DELETED BY GAME.

6. Symptom: Patches Fail to Apply or Repository Presets Disappeared

Likely Cause: Missing elevated permission, orphaned cache ZIPs, or corrupt preset repository data.

Fix Procedure:

1. Go to Utilities → Common Subtab.
2. Tap App Doctor (Self-Diagnose & Repair).
3. App Doctor runs a 7-point audit (elevated access, game installation, config path reachability, repository validity, download cache health, storage files, and recent error logs).
4. Tap Auto-Repair to fix safe issues automatically, or tap Report a Bug to attach diagnostic logs.