Search Issue Tracker
In Progress
In Progress in 1.0.X
Votes
0
Found in [Package]
1.0.9
Issue ID
BEHAVB-302
Regression
No
Collider is not listed when creating an action
Steps to reproduce:
- Create and open a behavior graph
- Right-click and select "Create new > Action"
- Click "Next"
- Type anything in the description
- Click on the dropdown that appears, which says "Regular Text"
- Search for "Collider"
Actual results: Collider is not listed
Expected results: Collider is listed and selectable
Reproducible with versions:
1.0.9
Tested on (OS): MacOS
Notes:
- A workaround is to manually change it in the script, but if that is done, the "edit definition" workflow does not work for that node
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
martinemma989
Feb 12, 2026 10:33
With no collider options,the installation stops working while all around it seems to propagate chaos in the process. The behavior needs to be supported when technical staff come for troubleshooting by means of documentation or examples that make these things clear. Technical forums today reveal that when doing so,one cipdassignmenthelp.uk.com is what a user is seeking.
jenniferjame066
May 28, 2025 21:04
In version 1.0.9 on macOS, the "Collider" option is missing from the behavior graph’s "Create New > Action" dropdown. This prevents users from selecting it directly and forces manual script edits, disrupting the standard workflow. At childrenpublishers.com, where we support interactive and educational children's content, this issue highlights the need for all core components to be easily accessible in the creation process to ensure smooth and efficient development.