δΈζζζ‘£ | English
Official and community plugins registry for ECS Framework Editor.
This repository serves as the plugin marketplace registry for ECS Framework Editor. It contains:
- Plugin metadata (not the actual plugin code)
- Automated validation and security checks
- Official and community plugin listings
Plugins developed and maintained by the ECS Framework team:
- Behavior Tree Editor - Visual behavior tree editor with execution visualization
High-quality plugins contributed by the community, reviewed and approved by maintainers.
Browse all available plugins in the Plugin Marketplace.
Want to add your plugin to the marketplace? Follow these steps:
-
Use our template to create your plugin:
# Copy the plugin template cp -r PLUGIN_TEMPLATE my-awesome-plugin cd my-awesome-plugin npm install
-
Develop your plugin following the Plugin Development Guide
-
Build and publish to your GitHub repository:
npm run build git tag v1.0.0 git push --tags
-
Submit metadata to this registry:
- Fork this repository
- Create
plugins/community/your-plugin-name.json - Submit a Pull Request
{
"id": "my-awesome-plugin",
"name": "My Awesome Plugin",
"version": "1.0.0",
"author": {
"name": "Your Name",
"github": "yourusername",
"email": "you@example.com"
},
"description": "An awesome plugin for ECS Editor",
"category": "Tool",
"tags": ["utility", "helper"],
"icon": "Package",
"repository": {
"type": "github",
"url": "https://github.com/yourusername/my-awesome-plugin"
},
"distribution": {
"type": "cdn",
"url": "https://cdn.jsdelivr.net/gh/yourusername/my-awesome-plugin@1.0.0/dist/index.js"
},
"requirements": {
"ecs-version": ">=2.0.0"
},
"license": "MIT",
"homepage": "https://github.com/yourusername/my-awesome-plugin"
}All plugin submissions go through:
- β JSON schema validation
- β Repository accessibility verification
- β Distribution URL checking
- β Basic security pattern scanning
- β Code quality review
- β Security audit
- β Functionality testing
- β Documentation review
Your plugin MUST NOT:
- β Use
eval()orFunction()constructor - β Access file system directly (use provided APIs)
- β Execute arbitrary shell commands
- β Contain obfuscated code
- β Collect user data without consent
Your plugin SHOULD:
- β Use TypeScript for type safety
- β Handle errors gracefully
- β Follow React best practices
- β Minimize dependencies
- β Document all public APIs
Total Plugins Official Plugins Community Plugins
- Contributing Guide - How to submit your plugin
- Plugin Template - Starter template for plugin development
- Metadata Schema - Required fields for plugin metadata
# Install dependencies npm install # Validate a specific manifest node scripts/validate-manifest.js plugins/community/plugin-name.json # Check repository security node scripts/check-repo-security.js plugins/community/plugin-name.json # Generate registry.json npm run generate-registry
- Review the PR
- Run automated checks
- Manually review the plugin code
- Merge the PR
- Registry will be auto-updated via GitHub Actions
- π¬ Discussions - Ask questions and share ideas
- π Issues - Report bugs or request features
- π ECS Framework Documentation
MIT License - see LICENSE file for details.
Thank you to all plugin developers who contribute to the ECS Editor ecosystem!
Made with β€οΈ by the ECS Framework Team