Before the plugin enters the chat.
Featured gameplay classes can become hard to track when the runtime shell, package docs, and feature rules drift apart.
Game Featured Classes keeps the shell narrow so teams can register and reason about featured classes without turning the package into a full workbench. The public landing page explains the target architecture and routes buyers to the shipped docs instead of overpromising missing tooling.
What that feels like
- Runtime shell behavior is easy to misunderstand without a clear landing page.
- Feature-class documentation gets scattered across package files and ad hoc notes.
- Target architecture can be mistaken for already-shipped workbench tooling.