FAtiMA Toolkit v4.0

We are releasing FAtiMA Toolkit v4.0 !

We’ve made some fundamental, highly valuable, changes to the Toolkit.

The main improvement is that now we only need 2 different files:

  • The Scenario file: It stores all information regarding the Dialogue, World Model and information regarding each Character, including their name, body, voice type etc…
  • The Rule Storage file: Stores all information about the rules within the scenario.

Instead of keeping 6 different files, one for each component, now you only need 2. If you used past versions of FAtiMA Toolkit you can imagine this is a pretty fundamental change, as such, we will need to update almost everything. Past Scenarios and Demos are no longer compatible with v4.0.

We are doing this update step by step, as in, we are keeping most of the Demos and Tutorials intact for now and prioritising the Starter Kit Unity Project and a tutorial specifically made for FAtiMA v4.0 (detailing its changes to how the overall system work).

Here are some resources you can use:

Both executables contain simple unfinished scenarios which you can use FAtiMA Toolkit to edit. Open both its scenario and storage file (inside the Streaming Assets folder) and customise them as your wish.

Video Examples

Sometimes the best way to learn how to use FAtiMA (or any software of this kind) is to watch people using it.

The following is a video recording of when I tried to take a simple story and put it “into” the FAtiMA-Toolkit. I also describe by thought process and some of the practices we have when using the framework.

Robbery Story:
Fairy Tale Story


Hopefully that helps   🙂


Previous Tutorials

To learn more about FAtiMA Toolkit and how its architecture works feel free to look at the tutorials available in the Right Sidebar of this page.

They all work for FAtiMA v4.0 just keep in mind that now all the rules are stored in the same place and that now FAtiMA only uses 2 files.

  • If you want a rule to affect only one of the RPCs (Role Play Characters, agents in FAtiMA), you need to specify either the name or something in the knowledge base that differentiates that agent from the others (example: “is(Police) “) and use that as a condition in the rule


No announcement available or all announcement expired.