Contact & Support
Contact Us
This page should centralize general support, access questions, download issues and business inquiries so users do not have to guess where to write first.
Use it as a clean routing layer: send common questions toward the FAQ and only ask for a message when the user actually needs human help.
The current public site already exposes contact, login and Patreon paths. This version should make those paths clearer and more intentional.
Best use of this page
Route people before they write a long message.
Keep the page direct and practical. Route people to self-serve answers first, but make business and licensing contact impossible to miss.
Start by choosing the type of question.
These route cards should cut down misdirected requests and give business inquiries a clear lane without burying everyday support.
Support
Account & access
Patreon connection issues, locked content, login problems or questions about what a membership unlocks on-site.
Library
Downloads & content
Missing files, gallery issues, requests for help finding a pack, or questions about assets, tokens and battlemaps.
Business
Commercial & licensing
Commercial use questions, approvals, business terms and where a creator should start before publishing.
Community
Feedback & bugs
Site bugs, tool issues, reportable problems and broader feedback that should be reviewed by the team.
Contact Form
Wireframe the form first, then connect the real destination later.
This should support general support, account issues, bugs and business contact without needing four different pages.
Your name
Email address
Discord handle / Patreon name
Topic / product / page URL
What do you need help with?
Message details, screenshots, error text, links
Before you send
Keep the expectations visible.
A short checklist here should improve the quality of incoming requests and keep the team from having to ask for missing context.
• Tell us which library or page you are using: Assets, Tokens, Battlemaps, Nexus or the membership area.
• Include your Patreon-connected email or username if the problem is account-related.
• If it is a bug, include the exact page URL, a screenshot and what you expected to happen.
• If it is a commercial question, route them to the application and agreement first.
Quick links that should solve the common cases faster than email.
Commercial Application
Keep licensing and business requests on a dedicated path rather than inside the general inbox.
Open applicationMembership & access
If the real issue is entitlement or tier confusion, this should send people straight to memberships and connection info.
Open memberships