Search Issue Tracker
Fixed in 2021.3.32f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X
Votes
0
Found in
2020.3.47f1
2021.3.22f1
2022.2.13f1
2023.1.0b10
2023.2.0a9
2023.3.0a3
Issue ID
UUM-32235
Regression
No
ROOTNAMESPACEBEGIN variable is parsed to the new script when placed on the first line of the template
Reproduction steps:
1. Open the attached project “ScriptTemplateBug“
2. Open the Assets folder
3. In the Project window press RMB>Create>C# BrokenClass
Expected result: Script is created with an empty class
Actual result: Template variable “#ROOTNAMESPACEBEGIN#” is parsed before an empty class
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a9
Reproducible on: Windows 11
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
- [Linux] Bug Reporter window is in Light mode when the Editor theme is Dark mode
Resolution Note (fix version 2023.2):
Fixed the logic used to replace the #ROOTNAMESPACEBEGIN# token
Resolution Note (fix version 2023.1):
Fixed an issue with custom script templates containing #ROOTNAMESPACEBEGIN# on their first line
Resolution Note (fix version 2022.3):
Fixed an issue with custom script templates containing #ROOTNAMESPACEBEGIN# on their first line
Resolution Note (fix version 2021.3):
Fixed the logic used to replace the #ROOTNAMESPACEBEGIN# token