Zion Games Studio Docs

Home / ZionTPS

🎯 ZionTPS

Third-Person Controller + Interaction Toolkit · Unity 6 · Version 1.5

ZionTPS 1.5.0 Release Notes

Workflow, interaction, diagnostics, and demo overhaul.

Version 1.5 turns ZionTPS into a more complete third-person setup and interaction foundation while preserving a modular, source-accessible runtime.

Highlights

  • redesigned five-stage UI Toolkit Setup Wizard
  • new Player Dashboard for generated implementations
  • automatic animation scanning and matching
  • Interaction Authoring for doors, buttons, and terminals
  • runtime pickup, chest, and talk interactables
  • UI Toolkit prompt, terminal, and message panels
  • primary in-window Diagnostics workflow with direct object selection
  • expanded camera, movement, Foot IK, and optional audio configuration
  • rebuilt ZionTPS_Demo movement and interaction test range

Upgrade from an Earlier Version

  1. Back up the project before importing 1.5.
  2. Do not regenerate a working player unless you need the new hierarchy or generated assets.
  3. Keep existing camera profiles, then review collision, crouch offset, and close visual protection.
  4. Run Diagnostics after import and review interaction UI references.
  5. If using audio, confirm the ZionTPS.Audio folder, configuration, and references.
  6. Update custom scene or documentation links from the obsolete ZionTPS_Showcase name to ZionTPS_Demo.

Supported Demo

Assets/ZionTPS/Demo/Scenes/ZionTPS_Demo.unity

The demo covers movement, crouch, ramps, jump, roll, camera collision, doors, buttons, terminals, prompts, and optional audio. Use it as the first comparison point when diagnosing custom setup issues.

Third-Party Content

The package includes Universal Animation Library 2 by Quaternius under CC0. See THIRD_PARTY_ASSETS.md in the package for attribution and details.

Validator Advisories

Demo FBX source-axis conventions and Unity's built-in legacy Font Material can produce non-blocking Asset Store Validator advisories. Treat red failures as blockers and record accepted advisories with their practical impact.

New users should begin with Getting Started. Existing users should run Diagnostics immediately after upgrading.