DUNGEONBOX PORTABLE PATCH - game build 0.19

1. Install DungeonBox Demo on the destination Windows PC. Close the game.
2. Check the ORIGINAL DungeonBox_Data/Managed/Foxtail.dll SHA-256 before replacing it:
   c0ed4e86be5bc1bbcda3ae60a63f47180a61f63dce87c25fb238fe531e879e9e
   In PowerShell: Get-FileHash -Algorithm SHA256 -LiteralPath "FULL PATH TO Foxtail.dll"
   A different hash means this exact build is unverified. Do not blindly replace a newer DLL.
3. Back up the original DLL, any existing DungeonBox.local.json, and the six quest files being replaced.
4. Extract DungeonBox Patch.zip INTO the game folder beside DungeonBox.exe.
   The included DungeonBox_Data folder must merge with the existing one.
   Keep patch-manifest.json as a record; the game does not require it.
5. Edit DungeonBox.local.json with a text editor, while the game is closed.
   It contains the current source PC settings. isDemo controls the central client demo check;
   other enable... switches have independent effects. Achievements stay disabled.
6. Start the game. Steam updates or Verify Files can overwrite the patch.

CUSTOM QUESTS

Each archive in Custom Quests contains one user.* folder with quest.dbquest.json.
Run the game once on the destination PC, then close it and find its active save folder:
  %USERPROFILE%/AppData/LocalLow/Foxtail Games LLC/DungeonBox/
    SaveDataSteamUsers/<DESTINATION STEAM ID>/UserQuests/
Extract the quest archives INTO that UserQuests folder. Create UserQuests if missing.
Do not reuse the source PC's Steam ID or replace existing user save directories.
For non-Steam sessions, confirm whether the game is using its shared UserQuests fallback.
Restart, enable Creator Content, select that pack, and keep drawing enabled.
Both quests contain native drawing/voting rounds and use installed game scenery.

DEPENDENCIES AND LIMITS

The installed game's existing dependencies are sufficient for the patch itself.
Python, ILSpy, Mono.Cecil, Codex, patch-building scripts and the authoring skill are NOT required.
Local AI separately requires compatible GGUF files and a functioning native runtime.
Enabling local AI does not make the game's Firebase multiplayer system offline.
Steam Workshop requires Steam/backend support; a client flag does not guarantee availability.
The systemPrompt field affects local narration, not the remote server's system prompt.
Previously disabled shipped quests have known incomplete backdrop/skill references.
Validated custom quests have not completed a full live playthrough.
Cross-PC operation is untested. This package targets the matching Windows build.

ROLLBACK

Close the game and restore your own backups. Steam Verify Files can restore shipped files,
but does not necessarily remove the extra JSON file or custom quests.