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
Issue description:
When creating a C# script from a custom template (located in script_templates) the editor sometimes permanently freezes and locks up when the .mono directory is present. Some more details gathered after testing:
The .mono directory generated when opening the project does not cause the freeze
The freeze always happens after pressing the build button, or running the game
Deleting the .mono directory does not prevent the crash until the editor is restarted
Just restarting Godot without deleting .mono does not fix the issue
No errors/logs in the console
The contents of my script look like this
using Godot;using System;namespaceAsteroids{publicclass%CLASS%:%BASE%{publicoverridevoid_Ready(){}publicoverridevoid_Process(floatdelta){}}}
Steps to reproduce:
Open up a working Mono project
Creating a script from a custom template freezes the editor
Close the editor & delete the .mono directory
Custom scripts now work again
Minimal reproduction project:
I prefer to keep my projects source private, and so far attempting to reproduce the issue in separate projects hasn't worked out yet
This issue started happening around the same time as my other issue #35664
The text was updated successfully, but these errors were encountered:
Godot version:
3.2 (Mono)
OS/device including version:
Windows 10
Issue description:
When creating a C# script from a custom template (located in script_templates) the editor sometimes permanently freezes and locks up when the .mono directory is present. Some more details gathered after testing:
The contents of my script look like this
Steps to reproduce:
Minimal reproduction project:
I prefer to keep my projects source private, and so far attempting to reproduce the issue in separate projects hasn't worked out yet
This issue started happening around the same time as my other issue #35664
The text was updated successfully, but these errors were encountered: