Summary
Multiple projects, when verse errors are present, the editor crashes on start-up.
I’ve had to open up VS Code and fix the errors and then I could load up the editor.
In one instance, the errors weren’t showing up in VS Code, so I had to remove groups of Verse scripts to find the culprit.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Verse
Steps to Reproduce
The last error I had was importing my framework into a Star Wars project, and I had a data structure named Weapons, which conflicted with the scenegraph API.
I was able to find this error in VS Code.
Later, I found that my enum option of Environment was also a problem, but that didn’t show until a later session.
"The enumerator (@fortnite.com/StarWars/Gorillas/Framework/GameSystems/goal_based_category:)Environment in package StarWars is ambiguous with this definition:
Note: the previous times had nothing to do with Star Wars.
Expected Result
The editor to not crash on startup ![]()
Observed Result
The editor crashing on startup.
Platform(s)
PC
Additional Notes
I submitted many crash reports.
I forgot to mention, it happened again when I followed the instructions to migrate the LightSaber and Forcepowers example into a project, but before I did I changed the directory name because I already had a UI directory. The broken UI.Materials.Whatever links in the code cause the crash as well.
Also, it might be worth noting that I have a lot of Verse in my project.