You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow Pandora Categories to be defined directly on the node via export.
Use case: I have an interactable object that takes a generic "tool type" value to tell if the character can interact with the object or not. Right now there isn't an easy way to define a category against the node (I have to hard code it in the gdscript file) or I would have to create a bunch of entities and embed the tool_type into each tool instead of using nested categories.
I wanted to see what people thought of adding category as a valid editor property or if I'm using the wrong data structure and we should document better data structure best practices.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Allow Pandora Categories to be defined directly on the node via export.
Use case: I have an interactable object that takes a generic "tool type" value to tell if the character can interact with the object or not. Right now there isn't an easy way to define a category against the node (I have to hard code it in the gdscript file) or I would have to create a bunch of entities and embed the tool_type into each tool instead of using nested categories.
I wanted to see what people thought of adding category as a valid editor property or if I'm using the wrong data structure and we should document better data structure best practices.
Beta Was this translation helpful? Give feedback.
All reactions