Do these assets work well together, or get in each other's way?

I’m looking to make a simple top-down turn-based strategy game that could become very complex eventually. I’d like to build it from the ground up using good frameworks available.

I am considering the following assets:

uScript
Behavior Desiner
uFrame

I own all three of these. They all appear to use nodes. They all seem to generate code.

Behavior Designer claims to work with the other two. But uScript and uFrame don’t say whether or not they work with each other.

Is there any advantage to using all three of these assets together? Or would they just get in the way of each other?

Disclaimer: I’m not asking which of these three assets are the “best”. I’m only trying to determine if they work well together, and / or if they would get in each other’s way. I am not an asset developer. I don’t own any of these assets.

They’re different things.

  • uScript does finite state machines (FSMs).

  • Behavior Designer does behavior trees (BTs).

  • uFrame does finite state machines, but its focus is more on providing a visual, scene-based game framework.

FSMs and BTs are two (mostly-)different ways to define how an entity makes decisions. Even though the products all visually use nodes, what those nodes represent are different. You could just as easily define an FSM or BT in text. Mecanim uses nodes for its animation state machines, too, but those nodes are primarily for animation control. You’ll want to familiarize yourself with their differences and purposes before making a decision.

1 Like