Operations
Plugins
Last updated 2026-07-06 07:00
Racinage plugins extend the hosted web version through a reviewed library, family-scoped installs, and super-admin approval gates.
Plugin library
The public library is served from plugins.racinage.com in production and from the local plugins/ folder in development. It has its own menu for Home, Plugins, Forum, Developers, Rules, Your Account, and a Main Website link back to racinage.com.
Family users can browse published plugins from the plugin site or from Manage > Plugins, then install, enable, disable, update, or uninstall plugins for the selected family account when they have the Manage Plugins permission. The plugin site install flow can select one or more family accounts.
- Installs are scoped by
family_long_id. - Each plugin keeps its own manifest, versions, install rows, purchases, reviews, comments, issues, FAQs, and audit log entries.
- Uploaded packages are stored for review; runtime hooks only load manually deployed files approved by the platform.
- Paid plugin purchases are pending manual review until checkout/webhooks are connected.
Developer access
Users must have Developer permission before publishing plugins. A super-admin can grant it manually from the user edit form by enabling Can publish plugins. Users can also request it from the developer access page.
Super-admins control the request mode from admin7839 > Plugins. The default is paid access at $5 USD. If the mode is free and auto-approval is enabled, requests grant developer permission immediately. If it is paid, the request waits for payment review and approval.
Publishing and review
Developers submit a ZIP containing manifest.json or a JSON manifest. Super-admins review each version, request changes, approve, reject, publish, delist, or delete listings. Destructive or public-facing actions stay behind super-admin permissions.
Packages are statically scanned for unsafe paths and blocked executable server/native files before storage. Each stored package keeps a SHA-256 checksum, a server-side review signature, compatibility bounds, and rollback notes. When an approved version replaces another version, Racinage records the previous version as the rollback target.
Plugin pages include overview text, current features, roadmap items, comments, reviews with 1-5 star ratings, an Issues tab with image/video attachments, and a Forum FAQs tab. Issues can be marked solved and reopened; FAQ threads can be closed and reopened.
The Developers page lists publisher profiles with search and sorting such as highest installs, most stars, most plugins, newest, and name. The account area lets logged-in users manage their plugin submissions, public developer profile, reviews, and badges.
Pricing and earnings
Plugins can be free, one-time paid, or subscription-based. User-published paid plugins split earnings as 20% to platform owners and 80% to the plugin publisher. Plugins published directly by super-admins keep 100% of earnings for the platform owners.
User publishers must keep a verified payout profile with identity, payout, and tax details before paid plugins can be approved. Paid purchase payouts are held until the publisher profile is verified.
Developers can also maintain public profile details such as public name, description, contact fields, website, social links, profile photo, and cover photo.
Remaining payment controls
- Connect payment provider webhooks before automatic paid approval.
- Connect the final payout provider before marking publisher payouts as paid.