Troubleshooting and Best Practices

When Things Go Wrong (And How to Make Them Right)

The Troubleshooter's Mindset

Every GM faces technical hiccups - it's not about avoiding problems, it's about handling them with grace. Think of troubleshooting like a detective story where you're both Sherlock Holmes and Watson. Each error message is a clue, each glitch a puzzle to solve. The difference between panic and confidence is preparation and knowledge.

Remember: Foundry is robust, your players are understanding, and every problem has a solution. Sometimes that solution is as simple as a refresh, sometimes it requires detective work, but you're never truly stuck. This lesson is your emergency toolkit, your troubleshooting encyclopedia, and your guide to preventing problems before they start.

The Troubleshooting Framework

graph TB A[Problem Occurs] --> B{Identify Type} B --> C[Connection Issues] B --> D[Performance Problems] B --> E[Module Conflicts] B --> F[Data Corruption] B --> G[User Errors] C --> C1[Check network] C --> C2[Verify ports] C --> C3[Test locally] C --> C4[Check firewall] D --> D1[Monitor resources] D --> D2[Reduce complexity] D --> D3[Clear cache] D --> D4[Update drivers] E --> E1[Safe mode] E --> E2[Binary search] E --> E3[Check versions] E --> E4[Read logs] F --> F1[Backup first] F --> F2[Validate data] F --> F3[Repair tools] F --> F4[Restore backup] G --> G1[Check permissions] G --> G2[Verify steps] G --> G3[Read documentation] G --> G4[Ask community] style A fill:#e74c3c,stroke:#c0392b,stroke-width:3px,color:#fff style B fill:#f39c12,stroke:#d68910,stroke-width:2px,color:#fff style C fill:#3498db,stroke:#2980b9,stroke-width:2px,color:#fff style D fill:#27ae60,stroke:#229954,stroke-width:2px,color:#fff style E fill:#9b59b6,stroke:#8e44ad,stroke-width:2px,color:#fff style F fill:#e74c3c,stroke:#c0392b,stroke-width:2px,color:#fff style G fill:#1abc9c,stroke:#16a085,stroke-width:2px,color:#fff

Common Problems and Solutions

The Debug Detective Toolkit

Learn to read the clues Foundry leaves behind!

Best Practices for Stability

flowchart TD A[Foundry Best Practices] --> B[Regular Maintenance] A --> C[Smart Organization] A --> D[Performance Care] A --> E[Player Communication] B --> B1[Weekly backups] B --> B2[Update carefully] B --> B3[Clean unused files] B --> B4[Monitor logs] C --> C1[Folder structure] C --> C2[Naming conventions] C --> C3[Asset management] C --> C4[Documentation] D --> D1[Scene optimization] D --> D2[Module curation] D --> D3[Resource monitoring] D --> D4[Cache management] E --> E1[Tech requirements] E --> E2[Troubleshooting guide] E --> E3[Backup plans] E --> E4[Support channels] style A fill:#27ae60,stroke:#229954,stroke-width:3px,color:#fff style B fill:#3498db,stroke:#2980b9,stroke-width:2px,color:#fff style C fill:#f39c12,stroke:#d68910,stroke-width:2px,color:#fff style D fill:#e74c3c,stroke:#c0392b,stroke-width:2px,color:#fff style E fill:#9b59b6,stroke:#8e44ad,stroke-width:2px,color:#fff

Backup and Recovery Strategies

Module Management Best Practices

Keep your modules under control!

The Module Hygiene Checklist

📋 Regular Audits

  • ☐ Review installed modules monthly
  • ☐ Remove unused modules
  • ☐ Check for updates (but test first!)
  • ☐ Document which modules are essential
  • ☐ Note module settings that work

🔄 Update Protocol

  1. Backup your world first
  2. Read module update notes
  3. Update one module at a time
  4. Test in a test world
  5. Check for conflicts
  6. Document any issues

⚡ Performance Monitoring

  • Track load times before/after modules
  • Monitor FPS with modules enabled/disabled
  • Watch for console errors
  • Ask players about performance

Emergency Procedures

Preventive Maintenance Schedule

An ounce of prevention is worth a pound of cure!

gantt title Foundry Maintenance Calendar dateFormat YYYY-MM-DD section Daily Check console logs :a1, 2024-01-01, 1d Clear browser cache :a2, 2024-01-01, 1d section Weekly Backup worlds :b1, 2024-01-07, 1d Review performance :b2, 2024-01-07, 1d Clean temp files :b3, 2024-01-07, 1d section Monthly Module audit :c1, 2024-01-31, 1d Update documentation :c2, 2024-01-31, 1d Test backup restore :c3, 2024-01-31, 1d section Quarterly Major updates :d1, 2024-03-31, 1d Full system backup :d2, 2024-03-31, 1d Performance baseline :d3, 2024-03-31, 1d

Community Wisdom: Collected Best Practices

From the Foundry Veterans

The Sacred Laws of Foundry

  1. Backup Before You Tinker: Always, no exceptions
  2. One Change at a Time: Easier to identify problems
  3. Read the Room (Logs): Console tells you everything
  4. Community is Your Friend: Someone faced your problem before
  5. Story Over Systems: Tech serves the game, not vice versa

Practice Exercise: Disaster Recovery Drill

The "Everything is on Fire" Drill

Practice these scenarios when things are calm:

  1. The Crash Recovery (5 minutes):
    • Force-close Foundry
    • Restart and load world
    • Check for data integrity
    • Resume from last good point
  2. The Module Conflict Hunt (10 minutes):
    • Start in safe mode
    • Enable half your modules
    • Test for the issue
    • Binary search to find culprit
  3. The Backup Restore (15 minutes):
    • Rename current world folder
    • Restore from backup
    • Verify everything works
    • Document what was lost
  4. The Emergency Simplification (5 minutes):
    • Disable all visual modules
    • Switch to basic scene
    • Turn off automation
    • Run session "theater of mind"

Real GM Crisis Stories

The Great Module Meltdown

"Mid-boss fight, everything froze. Turns out two modules were fighting over token control. I announced 'The wizard's spell goes wild!' and narrated a time freeze. Restarted in safe mode, disabled the problem module, and continued. Players thought it was planned!" - GM Alex

The Backup Hero

"Power outage corrupted my world data. But I had automated daily backups to Google Drive. Lost 20 minutes of prep, not 2 years of campaign. Now I preach the backup gospel to everyone!" - GM Priya

The Performance Pivot

"New player's old laptop couldn't handle my effect-heavy boss fight. I quickly made a 'tactical view' version - simple tokens, no effects, just the essentials. They could play, and it actually looked pretty cool!" - GM Jordan

Your Troubleshooting Toolkit

Essential Tools to Bookmark

  • 🔧 Foundry Console: F12 → Console tab
  • 📊 Performance Monitor: F12 → Performance tab
  • 🚪 Safe Configuration: Hold Shift on startup
  • 📁 Data Location: %localappdata%/FoundryVTT (Windows)
  • 💬 Discord Help: discord.gg/foundryvtt
  • 📚 KB Articles: foundryvtt.com/kb
  • 🎥 Video Guides: YouTube Foundry tutorials
  • 🔍 Reddit Community: r/FoundryVTT

Conclusion: Confidence Through Preparation

You now have the knowledge to handle any technical challenge Foundry might throw at you. Remember: every GM faces these issues, and every problem has been solved before. The difference between panic and confidence is preparation and knowing where to look for help.

Keep this guide handy, practice the emergency procedures when you're not under pressure, and remember that your players care more about the story than perfect technology. When issues arise - and they will - you'll handle them with the calm confidence of a true Foundry master.

May your servers be stable, your backups be current, and your games be legendary!