Ultimate Character Controller

Export

Atlas supports the released Ultimate Character Controller Version 3 family, including UFPS and Third Person Controller. Use version 3.3.7 or newer within Version 3. Version 4 development APIs are outside this guide.

Open Tools > Opsive > Ultimate Character Controller > Atlas and use a duplicate test character for a new ability.

Choose the right object

Object Purpose
Ability Character behavior coordinated through the ability lifecycle
Item Ability Item-related behavior using the item-ability framework
Ability Starter Custom logic for starting an ability
Ability Stopper Custom logic for stopping an ability

Attach the relevant character, component, and existing user-authored ability source. Explain the active perspective, input setup, Animator requirements, and any installed add-ons the behavior depends on.

Example: plan a short dash

/plan Add a short dash ability for my Version 3 character. Use the controller's movement and ability APIs. Define start conditions, stopping, interruption, and cleanup. Do not move the Transform directly. Identify inspector setup and a test plan before generating code.

Check how the dash coordinates with existing movement, camera, items, and animation. Define which abilities block it and whether it is concurrent. Only then ask Atlas to build the agreed plan.

Atlas docked beside a Character Controller workflow while presenting an ability result.

Apply and configure

  1. Review the generated source and inherited ability lifecycle methods.
  2. Save the files under your own Assets/... folder and wait for compilation.
  3. Add the ability to the test character through the controller’s normal Abilities inspector workflow.
  4. Configure Start Type, Stop Type, input, ordering, and required fields according to the implementation.
  5. Assign any States, Animator parameters, or references the result requires.

Generated source does not configure all character and Animator settings for you. A compiled ability can still fail to start because its start conditions, priority, input, or required components are not configured.

Verify behavior

Test starting, normal stopping, interruption by another ability, disabled character, death/respawn, and perspective changes where relevant. Confirm temporary States, scheduled callbacks, event subscriptions, and motion are cleaned up.

Test any networked behavior through the actual networking integration and authority model. Generating a local ability does not create replication automatically.

Atlas uses installed-product metadata when selecting add-on context. Do not assume an Agility, Climbing, or Swimming API is available merely because another controller-family product is installed.

See Abilities, Creating a New Ability, and the existing Atlas integration guide.