j-conrad
j-conrad
**Description** The `Multigate` flow node doesn't work as expected. 1) The outputs are numbered `1, 2, 3` but the `startIndex` values are `0, 1, 2` 2) The `Reset` action doesn't...
**Description** The `Trigger` node (Custom Event) has a flow node output that doesn't fire when the input is triggered. This prevents chaining of events past the Trigger node. **To Reproduce**...
**Description** The `Get Component Property` and `Set Component Property` nodes display parameters of type `vec3` when choosing a `Rigidbody` component and selecting `Collision Mask`:  Based on the `Rigidbody` component,...
**Description** Writing this as a bug because the lack of this feature severely limits the usefulness of tags. When using tags on entities, there is no node that allows you...
**Description** When using a `ForLoop` flow node, the output doesn't appear to fire the correct number of times as specified in the `startIndex`/`endIndex` values of the node. **To Reproduce** Steps...
**Is your feature request related to a problem? Please describe.** In behavior graphs, it can be difficult (and in many cases, impossible) to manage multiple entities or other values at...
**Is your feature request related to a problem? Please describe.** OnInteract fires when an entity is clicked. Having more granularity would be extremely useful. Similar to other web-based interactive elements,...
**Is your feature request related to a problem? Please describe.** There are many places where being able to control logic based on randomness would be helpful. This includes both random...
**Description** When dealing with `Float` values, the output shows 17 decimal places. I might expect this when working with values such as `Position`, however, even declaring a variable and setting...
**Is your feature request related to a problem? Please describe.** It is common to want to be able to take a range of input values and remap them to a...