Skip to content

0.2.2

Choose a tag to compare

View all tags
@Nenkai Nenkai released this 22 Jun 17:51
· 5 commits to master since this release
0.2.2
a3bd511

0.2.2

  • fsms: when adding quest components (QuestActionComponent/QuestConditionComponent), quest related properties will be automatically tracked and added (category, subcategory, etc).
  • fsms: saving quest fsms will default to a proper file name rather than the name specified within baseinfo files
  • fsms: layers pointed to by more than one node is now allowed (#1)
  • docs: none because none was provided 💔

⚠️ Report any regressions if any, especially on the FSM side.

FSMs

Some Usage Notes

  • Adding Nodes/Layers: Right click on the graph, context menu.
  • Adding components to nodes: Right click node, Add Component. You will be presented with a search menu.
  • Edit Node/Layer name: Double click name, or right click node -> Edit Name
  • Create/remove node transition to self (repeating): Right click node, Create/Remove self transition
  • Delete transition: Select transition, on the Connection Editor, press the bin button
  • Connecting Nodes: Left click from border of node to another node
  • Panning: Middle Click or Right Click (hold)

Some context menu options may be greyed out depending on whether the context allows it.

Note

For quest fsms that contain properties like category, subcategory, etc, these will be automatically filled transparently. Note that it requires the file name to properly start with quest_ so that the editor knows they're quests.

Documentation/Help

Tip

Documentation on components and fields are always required and welcome! Almost everything can be documented and represented on the editor.

Known Issues

  • When creating FSMs it's possible to create illogical flow, (i.e in->out->in layers), please try to keep it to original flow design you can see in original FSMs.
  • Some FSMs in ui are not yet supported.
  • className, fsmName, addAllTransition, addTransition, EnableBaseAllTransition, EnableBaseTransition, EnableFalseComponent are NOT supported, check the log window when that happens (there should be a prompt)
  • You should always check that the export was correct on the fsm level, just to make sure no original data was dropped, just incase there is a bug.

BTs (Behavior Trees)

Currently viewing only.

Note: data from RandomSelectorEmNode is not shown.

Message Files

  • Scene (placement) message files are not supported
  • Files that store data rather than entities (text_* files).
  • files in behaviorparam are not supported since they're basically different entities for every single file
Assets 4
Loading