BioForge Terrarium Studio
Procedural ecosystem, genetic evolution and live event mutation engine for playful operational simulations inside NocoBase.
Package
@max/plugin-bioforge-terrarium-studio
Version
1.0.1
Runtime
Node >=18
Source
Bound into storage/plugins/@max
Plugin documentation
This commercial preview explains the package identity, capabilities, runtime compatibility, deployment surface and operational requirements a buyer should review before purchase.
Procedural ecosystem, genetic evolution and live event mutation engine for playful operational simulations inside NocoBase.
Feature modules
- Core capabilities: Seeded habitat simulation
- Core capabilities: Mutation and lineage tracking
- Core capabilities: Event-driven world changes
- Core capabilities: Replayable timeline experiments
- NocoBase integration: Server entry point packaged for plugin manager
- NocoBase integration: Client bundle for admin UI registration
- NocoBase integration: Documentation, changelog and security notes travel with the package
When to use it
- Teams that need simulation lab inside NocoBase.
- Administrators who want packaged, versioned features instead of one-off custom screens.
- Operators who need source, dist, docs and release evidence kept together.
NocoBase surfaces
- /bioforge
- /admin/bioforge-terrarium
Access and governance
- NocoBase role-based access control
- Admin-only configuration surface
Install and upgrade
NocoBase plugin-manager flow
yarn pm pull /app/nocobase/storage/plugins/@max/plugin-bioforge-terrarium-studioyarn nocobase upgrade --skip-code-updateEnterprise readiness
Built to pass a company review, not only a demo.
Procurement packet
Package name, maintainer, edition, version, compatibility and delivery model are visible before contracting.
Security review
RBAC expectations, install surface, private delivery and artifact proof are part of the product dossier.
Deployment control
Pilot, production rollout, upgrade and rollback conversations can be run from the same facts.
Support lifecycle
Changelog, maintenance window, support scope and license rotation are positioned as enterprise operations.
Package identity