Entities & abilities
Connect entities, abilities, stats, resource pools and tags.
Gameplay
Connect runtime gameplay systems and their authoring workflows.
A proposed Gameplay Solution for connecting runtime systems with the authoring work behind a game.
An idea under exploration. Scope and timing are undecided.
Is it a fit?
A starting point for your project.
For Unity teams evaluating a shared foundation for abilities, movement, interactions and related authoring workflows in a specific game.
Concept — not available
Before you plan around it
Later concept with a broad scope. A sharply defined supported use case and convincing sample are required before release.
Planned product scope
What it aims to bring together.
Candidate capabilities, subject to release verification.
Combat & effects
Connect effects, targeting and other runtime interactions through a common gameplay workflow.
Movement & authoring
Coordinate locomotion, animation and authoring tools with the game's active systems.
Know the boundaries
Scope & compatibility.
Review the intended installation and the evidence still needed before release.
Supported gameplay scope
The final boundary needs a representative gameplay workflow and current package evidence; it is not a promise to support every interaction, movement or combat model.
Integration choices
Animation, input, physics, camera, AI and networking integrations depend on the chosen use case. No engine-version or third-party compatibility matrix is published yet.
Project-specific extensions
Custom abilities, animation, controls and authoring extensions belong in a defined project scope. Existing gameplay architecture and content must be assessed before integration.
Product evidence
Demonstrations to come.
A representative gameplay workflow still needs to be identified and verified. The Fire illustration is decorative and does not demonstrate software behavior.
Availability & working together
The product. Help when you need it.
Concept — not available. Scope and timing are undecided. Software licensing and project services are separate offers.
Software · Concept
Gameplay software license
A proposed Solution license would include its required shared dependencies. Final product inclusion, support terms and a purchase destination are not published yet. Project implementation is a separate engagement.
Ask about the productSeparately scoped services
Aether Gameplay Integration
Discuss a concrete gameplay use case and the systems already in your project. Establish the supported foundation first, then scope any bespoke abilities, controls or authoring work.
Discuss gameplay integrationCompare service options & how we work together
Software licensing and project implementation are separate offers. Product-based setup and integration depend on a verified release and supported configuration; a concept page does not establish availability.
How working together works.
Start with a conversation
Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.
Define the work
Where the requirements are uncertain, paid discovery produces findings, risks and a recommended path. Before delivery, we agree on inputs, deliverables, exclusions and acceptance checks.
Build, test and hand over
I deliver against the agreed scope and hand over documentation, test results and known limitations. Ongoing support is a separate agreement.
A direct line to the developer
Tell me what you're building.
Interested in the Gameplay concept? Describe the problem you'd want it to solve. This is an expression of interest, not a preorder or a release commitment.
