Loading
How it works
Pick something in your game. Give it a brain.
Actorvia starts with an entity you already have — a character, a vehicle, a machine — and gives it the infrastructure to perceive, remember, decide and act. This page walks the whole loop, from the thing in your world to the change your server commits.
- The unit
- An entity, not a world
- You control
- Observations, actions, goals
- The runtime runs
- Reasoning, validation, execution
- First platform
- Roblox
Start with the thing
Actorvia starts with something you already have.
A merchant, a bus, a ferry, an aircraft, a loading arm. If it has observable state and a way to act on it, it can carry a brain — no particular hierarchy, tag scheme or base class required.
The brain
Give it a brain.
A brain here is not a chat window bolted onto a prop. It is the loop a believable entity needs — and conversation is just one capability it might or might not have. A wolf never speaks. It still perceives, remembers, decides and acts.
Perceive
It sees the world through observations you declare — nothing else exists to it.
Remember
Its role, its goal and its spent budget persist from one decision to the next.
Decide
It reasons over what it perceives and holds, toward the goal it was given.
Plan
The decision becomes an ordered sequence of actions from its declared surface.
Act
Approved actions actuate through your mechanics, and the world actually changes.
Perception
You decide what it can perceive.
Observation is an allowlist, not a camera feed. The adapter for your entity declares exactly which fields enter its view of the world.
A field you do not declare is not merely hidden — it never exists inside the agent. It is absent from the planner’s input, absent from diagnostics, and can never be sent to an external model. Declaring narrowly is a privacy control and a performance control at once.
A bus might perceive its speed, its route progress and the obstacle ahead. It does not perceive the player’s account, the whole map, or anything else you left out.
Capability
You decide what it can do.
A brain does not get control of your game. It chooses between the actions you expose — and only those.
Each action declares its parameters, its preconditions and its cost against declared resources. Plans are composed only from this set; there is no escape hatch that lets a decision call arbitrary code. That is what makes giving something a brain safe enough to actually do.
The same declaration is what the runtime enforces at execution time — an action outside the surface has no reachable call path, however the decision was produced. The details live on the security page.
Goals
Give it goals and behaviour.
An agent needs something to want. Goals are declared with a satisfaction predicate and abandonment conditions, and roles bundle the capabilities and constraints a kind of agent carries.
Your existing systems submit goals — a quest system, a dispatcher, a scheduler, or a player request that has already passed your own checks. The agent works toward the goal until it is satisfied or its abandonment conditions fire.
Roles come from domain packs: reusable bundles of capabilities, constraints, resources and goals for a problem area, like port operations or wildlife. Behaviour is authored in Roblox Studio, where you already build.
06 — The loop
Actorvia runs the loop.
Every decision, for every kind of agent, travels the same route. You author the surfaces it travels between; the runtime drives.
Observe
The adapter normalises the entity — pose, load, surroundings — into an observation frame, frozen for the tick. Only fields you declared exist in it.
Context
The frame joins what persists: the role the agent holds, the goal it is working toward, the budget it has left. A decision never starts from a blank slate.
Goal
Goals arrive in the runtime’s own vocabulary, with a satisfaction predicate and abandonment conditions — from your quest system, a dispatcher, or a player request you have already checked.
Reason + plan
The planner turns the goal into an ordered sequence of actions, composed only from the surface you declared. Deterministic and seeded by default.
Validate
Every step is checked against capability, constraint and world preconditions. Rejection is ordinary: a typed reason comes back and the agent re-plans.
Act
Resources settle atomically, the adapter actuates, and world state is written once — on your server. Then it observes again.
The full eight-step execution path — observation, manifest resolution, planner, validation, resource ledger, executor, commit, diagnostics — is documented on the product page. External models attach as proposals at one step and can reach none of the others.
The boundary
Models can think. They do not own the world.
External models — hosted or local — can contribute intelligence to the loop. What they contribute is a proposal, and a proposal is not a command.
A provider sees only the observation fields you enumerated, already redacted. Its answer re-enters the loop at validation and is checked exactly like a locally planned decision — it holds no capability, no resource authority and no path to world state. If it is slow or unreachable, the deterministic planner continues on its own.
This is the difference between agents that act and agents that just talk. Speech is one capability a character might have; the loop — perceive, decide, act, inside declared bounds — is the product.
Clientrequest only
Modelproposal only
Your server, running Actorvia
- 01Validate against role and world
- 02Reserve resources atomically
- 03Commit world state — sole writer
world state
08 — Embodiments
One brain system, many kinds of bodies.
These are the surfaces the adapter layer is designed around — you author the adapter for your entity. One prebuilt role ships today: a greeter.
Humanoids and characters
Guards · Villagers · Companions · Crowd extras
- Observes
- Pose, footing, nearby actors, audible events, held items, damage state.
- Actuates
- Locomotion targets, animation intent, item use, speech and emote hooks.
Ground vehicles
Cars · Trucks · Trams · Service vehicles
- Observes
- Speed, heading, lane or path progress, obstacle lookahead, fuel, occupancy.
- Actuates
- Throttle, brake, steering target, gear, signals, doors.
Boats and watercraft
Ferries · Cargo vessels · Patrol craft · Dock tenders
- Observes
- Heading, drift, berth availability, draft clearance, cargo and passenger load.
- Actuates
- Throttle, rudder, mooring lines, ramps, loading and unloading sequences.
Aircraft
Fixed wing · Rotorcraft · Drones · Airport ground traffic
- Observes
- Altitude, attitude, airspeed, waypoint progress, clearance state, separation.
- Actuates
- Throttle, control surfaces, gear, waypoint commitment, hold and go-around.
Robots and machines
Cranes · Robotic arms · Conveyors · Turrets · Drills
- Observes
- Joint state, working envelope, load, queue depth, maintenance state.
- Actuates
- Joint targets, grip and release, feed rate, start, stop and safe-hold.
Also designed forAnimals and wildlifeSwarms and formationsInfrastructure and systemsCreator-defined actors
See eight worked examples
Adapters are authored by you — this is a design surface, not a catalogue of shipped templates.
Today
Starting with Roblox.
Roblox is the first shipping surface, not the size of the idea. What exists today is concrete: alpha — unsigned windows build, downloadable the moment you subscribe.
- Actorvia for Windows
- The desktop application (0.1.0-alpha.4, Windows 10/11 64-bit). It signs you in, holds your projects and issues the pairing code that connects Studio.
- Roblox Studio plugin
- The authoring side: attach adapters, inspect live observation frames, replay decisions and run scenario suites without leaving Studio.
- Your Roblox servers
- The runtime executes inside your own experience — planning, validation and commit happen on your server, not on a service between your players and your world.
Alpha — unsigned Windows build
Give something
a brain tonight.
Create an account, subscribe, and the desktop app and Studio plugin are yours immediately.
Sign-up and billing are self-serve; pairing Studio to a project is a manual step during the alpha. Cancel from the billing portal whenever you like.