Comments

• AdventureFan

  September 2015 edited September 2015

  I find it works great with AC at this point. You can exchange variables, run an AC interaction from Playmaker, or a Playmaker state from AC. So they can work seamlessly together. You could make minigames, an array database of some other stuff, handle GUI stuff instead of from AC, character job or patrol systems, or whatever.
  
  I don't think there's any real particular benefit over C# though. I mean basically what it is is similar to the AC actions and ActionList editor, except it covers pretty much everything you could code for. It does have a learning curve in starting, and then more for doing more complex things, but overall it's quite powerful and for me handy. Whether it's necessary when you can code, I think is almost all down to your tastes of whether you want to work that way or not.
  
• Snebjorn

  September 2015

  Hmm, I think I'll give it a try on a patrol system for NPCs - I expect it would be quite useful to have the visual feedback from the FSM updating in realtime for that type of thing.

  
  

  Thanks for your input!
• kici

  March 2016

  @Snejborn You'll find that even though if you use playmaker ( which I'd suggest to do so ) you will still have some need of old fashioned scripting for more in depth complicated scenarios.