Yeah, this is the reason why most modern sites implement CSRF protection with tokens instead of referers :/ There's a more thorough option that would keep us safe while still allowing all clients: find the specific actions we need to protect (like adventuring), rewrite all pages to include the pwd token on that action, and then reject requests that don't include it. That doesn't sound incredibly feasible, though…