Comments

• Teshla

  March 2016

  I'd go with programming a custom action for any kind of mini-game puzzle. If the puzzle is more complex I'd suggest to program it without AC and only interface with AC while starting, solving or failing a puzzle. To send messages to your custom script and thus capture a start of a puzzle I'd go with "Send message" Action that runs a custom method from AC actions and after puzzle completion or failure I'd go with [SomeAction].Interact() method to move on from custom script to actionlist actions. So that would be my recommended entry/exit points into/out of custom mini-game puzzles.
• ChrisIceBox

  March 2016

  Yes, custom scripting would be the way to go if you want to avoid a complex Action tree.  The best way to avoid this would be to write a new script that handles everything, and simply disable AC for the puzzle's duration.
  
  You can selectively disable AC's systems using the Engine: Manage systems Action - this way you could de-activate the movement and interaction systems, but still retain the dialogue system.  ActionLists can be called manually by running their Interact() function.
  
• vigrid

  March 2016

  Thank you, Teshla and ChrisIceBox. I created a custom MonoBehaviour to drive the puzzle logic and simply sent messages to it like you recommended. It worked like a charm.