Developer FAQ
Secure Mods. Seamless Installs.
Revenue & Monetization
Transparent breakdowns of how creator payouts work on the ModVault platform.
What is the revenue split for paid mods and DLC packs?
ModVault operates on a 70/30 split favoring creators. For every $100 in net revenue (after payment processor fees like Stripe's 2.9% + $0.30), you receive $70. Payouts are processed bi-weekly via PayPal or direct bank transfer once your balance exceeds $50. Taxes are handled per your W-9 or W-8BEN on file.
Do I need to issue refunds for beta testers?
No. Beta access tokens are non-refundable by design. If you mark a mod as "Early Access" or "Beta," the storefront automatically disables the refund window. You can manually issue credits through your Creator Dashboard under Payouts > Manual Adjustments.
Content Moderation & Removal
Guidelines on takedowns, appeals, and community standards.
Why was my mod flagged for "Asset Rehosting"?
Our automated pipeline (VaultScan v3.2) compares file hashes against known proprietary SDKs and unlicensed asset packs. If you're using third-party materials, you must upload a signed license waiver to your mod's compliance tab. False positives can be appealed within 48 hours via the Support Ticket system.
Can I request a temporary takedown for updates?
Yes. Use the "Pause Visibility" toggle in your Creator Dashboard. This hides the mod from search and recommendation feeds for up to 14 days without affecting your download metrics or active subscriber counts. Re-enable it instantly when your patch is ready.
Technical Support & Integration
API limits, SDK compatibility, and troubleshooting.
What are the rate limits for the ModVault REST API?
Authenticated endpoints allow 1,200 requests per hour per API key. Unauthenticated reads are capped at 120 requests per hour. Exceeding these limits returns a 429 status with a Retry-After header. Need higher throughput for enterprise mod-loaders? Contact our API team at api-support@modvault.dev.
How do I handle dependency conflicts in my manifest?
Use the requires and conflicts fields in your modvault.json manifest. Specify version ranges using semantic versioning (e.g., >=2.1.0 <3.0.0). The installer will prompt users to resolve conflicts before proceeding. Test your dependency tree using the offline vault-cli validate command.
Still have questions about the SDK, payout thresholds, or compliance waivers?
Open a Support Ticket View Full API Reference