Help shape the release

Testers & Bug Reports

Take test missions, report bugs, climb the tester ranks, and fix Discord tab-back crashes.

Missions & bug reporting

How to test and report bugs

Every test we need done is a mission. Complete a mission, tell us how it went, and earn XP. Find and report a bug for even more XP.

Taking a tester mission

  1. In game, type /browser on once so links can open.
  2. Hail Pip Ledgerwick in Jaggedpine and click Missions.
  3. Pick a mission, click Take this mission, and follow the steps down to the Pass line.
  4. Back on the board, pick I did it or I could not do it, add a short note, and click Send result.

Pip's links carry your character's name automatically. Open the board from Pip each time. Tick Show my character name on the leaderboard to be listed, or leave it off to stay private.

Reporting a bug

  1. Hail Pip Ledgerwick and click Report a bug (the form already knows where you are standing), or use the web bug reporter.
  2. Type /loc in game if reporting from outside Pip, write down your location, what you did, and what you expected.

What to report

  • Anything that stops you entering Jaggedpine, or crashes when changing zones.
  • Buildings or doors that are missing or invisible, or items showing the wrong model.
  • NPCs you cannot find with the Find window.

Tester XP, ranks and limits

What you doXP
A featured mission (top of the board)50
A bug you reported that we confirm50
A Last Fire raid mission40
Monster Missions from Tessaly30
Aurevaine missions25
Gear, crafting and trophy missions20
Town and Game Cabinet missions15
Castle and card missions10
  • XP counts once a team member checks your result. Top three ranks: Legend of the Clipboard (800), Pip's Right Hand (1200), and Keeper of the Great Ledger (1800), plus badges like Castle Walker and Fire Keeper.
  • Limits: one claim per mission per character, up to 10 results a day count for XP, and sending many at once asks you to slow down for an hour.

Online tester leaderboard and checklist links: Coming soon.

Crash fix

Crashes when tabbing back: block Discord's game hook

Discord loads a small file called DiscordHook.dll into every game you play even when its overlay is turned off. On some PCs this closes the game when you tab back in or after a screen saver or monitor change.

Blocking it only stops Discord's in-game overlay. Discord chat, voice and screen share keep working.

Script download (Toggle_Discord_Game_Hook.cmd) and SHA-256 hash: Coming soon.

Check back once the download file is published, or ask in tester chat.

How to use it

  1. Close the game.
  2. Double-click Toggle_Discord_Game_Hook.cmd (if Windows SmartScreen appears, click More info then Run anyway; no admin rights needed).
  3. It shows whether the hook is ON or OFF. Type Y and press Enter to switch it, or N to leave it as is.
  4. Start the game again.
  • What it changes: renames DiscordHook.dll and DiscordHook64.dll to .blocked inside your own user Discord folders (Discord, PTB, Canary) and changes no settings. You can read every line in Notepad first.
  • Undo / updates: run it again and type Y to re-enable, or re-run after a Discord update if crashes return.
  • Status check only: run Toggle_Discord_Game_Hook.cmd /status from a command window.
  • Verify hash (optional): run Get-FileHash .\Toggle_Discord_Game_Hook.cmd in PowerShell.

If the game still closes with Discord blocked, please report a bug and mention you tried this.