Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.3.0a9
Issue ID
UUM-52188
Regression
Yes
Scripts derive from StateMachineBehaviour instead of MonoBehaviour when creating new C# Scripts
How to reproduce:
1. Create a new project
2. Create a new C# Script
3. Open the C# Script
Expected result: The newly created C# script derives from MonoBehaviour
Actual result: The newly created C# script derives from StateMachineBehaviour
Reproducible with: 2023.3.0a9
Not reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproduced on: macOS Ventura 13.5 (Intel), Windows 11 (User reported)
Not reproduced on: No other environment tested
Notes:
- The reporter has noted that - “Likely cause: Scripting submenu has Playables submenu under it with two items, likely there should be three there (another for mentioned state machine).”
- The same happens if using C# Script from the Scripting submenu.
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
There are no fixes planned for this Bug