Skip to content

Upgrade Guide

This section helps you update custom actions and editor code written for PlayMaker 1 so they work with PlayMaker 2.

If you already have existing actions, start here before rewriting anything. Most upgrades are straightforward once you know the new patterns.

What Changed

PlayMaker 2 updates several core API conventions:

  • FsmStateAction is replaced by BaseAction
  • Action update callbacks are replaced by a single Execute flow
  • Variable and event fields use newer parameter conventions
  • Action summaries and progress reporting use new APIs
  • Some older helpers and attributes are no longer supported

If you're migrating an existing action library, this is the best order to read the docs:

  1. Base Action to understand the new inheritance model
  2. Action Parameters to update fields and references
  3. Action Update to move old update methods into Execute
  4. Action Summary to replace AutoName
  5. Action Progress to update progress reporting
  6. FSM List if your code queried active FSMs
  7. Deprecated to catch old APIs that no longer exist

Upgrade Topics

  • Base Action

    Learn how PlayMaker 2 actions inherit from BaseAction instead of FsmStateAction.

    Open Base Action

  • Action Parameters

    Update variable, event, and parameter fields to the newer PlayMaker 2 conventions.

    Open Action Parameters

  • Action Update

    Replace OnUpdate, OnFixedUpdate, and similar callbacks with Execute and related helpers.

    Open Action Update

  • Action Summary

    Replace AutoName with GetSummary and the newer summary template approach.

    Open Action Summary

  • Action Progress

    Migrate old progress methods to the Progress property workflow.

    Open Action Progress

  • FSM List

    See how PlayMaker 2 uses UpdateManager instead of the old FSM list access pattern.

    Open FSM List

  • Deprecated

    Check which older attributes and APIs are no longer supported, and what to use instead.

    Open Deprecated List

Good Migration Workflow

When updating an older action, a practical workflow is:

  1. Change the base class first.
  2. Rename and convert parameters.
  3. Move execution logic into Execute.
  4. Update summary and progress APIs.
  5. Scan the Deprecated page for anything left over.

This usually gets an older action compiling again quickly, then you can refine the behavior to match PlayMaker 2 best practices.