1. Getting Started
After your application is accepted, you'll receive:
- TestFlight invite (iOS) or Internal testing track (Android) — install the beta build
- Discord invite — join the private beta server
- Welcome email — with your tester ID and first week's testing focus
Install the app, create an account, and introduce yourself in #general on Discord.
2. Testing Schedule
The program runs for 4 weeks. Each week focuses on specific areas of the app:
Week 1 — Compendium, Dice & Characters
- Search and browse spells, monsters, items, races, feats, backgrounds
- Test filters, full-text search, and offline access (airplane mode)
- Roll dice: standard, advantage/disadvantage, complex notation (2d6+1d8+4)
- Try shake-to-roll and different dice skins
- Create a character from scratch (try different classes and races)
- Level up to at least level 5, try multiclassing
- Use the class grimoire spellcasting UI to prepare and cast spells
- Import a character from D&D Beyond, Roll20, or Fight Club 5e
- Export to PDF and CSV
Week 2 — Campaigns, Multiplayer & Combat
- Create a campaign and invite another tester via room code
- Test real-time sync between DM and player devices
- DM: use controlled leveling to level a player's character
- Create shared notes and private (DM-only) notes
- Check audit logs for session activity
- Build an encounter using the encounter builder + CR calculator
- Run initiative — test real-time sync between devices
- Apply conditions to combatants and verify tracking
- Roll NPC actions and try batch NPC actions
Week 3 — Battle Maps, Vision & Lighting
- Create a map with fog of war
- Place tokens and test size auto-detection
- Try hex grid mode
- Set up darkvision on tokens and verify visibility
- Place light sources and verify fog interactions
- Test real-time map sync between DM and players
Week 4 — Full End-to-End
- Run a full campaign session using all features together
- Coordinate with other testers for multiplayer stress testing
- Revisit any areas where you found issues earlier
- Submit your final feedback and overall experience report
3. How to Report Bugs
Report bugs in the #bug-reports channel on Discord using this format:
Summary: [One-line description]
Device: [e.g. iPhone 15 Pro, iOS 18.3]
Steps to Reproduce:
1. ...
2. ...
3. ...
Expected: [What should happen]
Actual: [What actually happens]
Screenshot/Recording: [Attach if possible]
For critical/blocking bugs, tag @dev in your report. We aim to respond to all reports within 24 hours.
4. Weekly Check-ins
Every week you'll receive an email with a link to the check-in form. The form takes about 5 minutes and asks:
- What features did you test this week?
- How many hours did you spend testing?
- Any bugs found? (brief summary — details go in Discord)
- Overall experience rating (1–5)
- Any feature requests or suggestions?
Check-ins are due by Sunday each week. Missing 2 or more check-ins will result in removal from the program to make room for active testers.
5. Discord Channels
#announcements— Weekly testing focus, new builds, program updates#bug-reports— Structured bug reports using the template above#general— General discussion, questions, and feedback#nat20-testing— Feature-specific discussion and testing coordination
6. Confidentiality
As a beta tester, you've agreed to:
- Not share screenshots, screen recordings, or beta builds with anyone outside the program
- Not discuss unreleased features on social media, Reddit, Discord servers, or any public forum
- Keep all feedback within official channels (our private Discord and email)
- Not submit public App Store or Play Store reviews during the beta period
This isn't a legal NDA — it's a trust agreement. We're sharing early, unfinished software with you because we trust your feedback. Please respect that trust.
7. FAQ
What if I miss a week?
Life happens. If you know you'll miss a week, let us know in Discord. One missed check-in is fine. Two missed check-ins without notice will result in removal.
Can I test on multiple devices?
Yes! Testing on multiple devices is encouraged. Just list all your devices in your application.
Do I need a D&D group to test multiplayer?
No. We'll coordinate multiplayer testing sessions in Discord so you can pair up with other testers.
What happens after the beta?
Beta testers who complete the program get their name in the app credits and a free Premium Player upgrade. The app moves to public release on the App Store and Play Store.
How do I leave the beta?
Just let us know in Discord or email. No hard feelings — we appreciate any time you contributed.