Bug Report: [DESCRIBE YOUR BUG IN DETAIL HERE]

[Witherbomb-47]

What version of the engine are you using?

Version: Experimental 1.0.1 a7b0401

Which target are you using?

[ x] Windows
[ ] Linux
[ ] Mac

Explain your issue

Please check first if your issue haven't already been reported yet.

1. Enter chart editor
2. Click on song
3. Click "New Difficulty"
4. Click "Save & Close"
5. The window freezes entirely and you are forced to close it

2026-06-16.20-38-24.mp4

[r6915ee]

Have you tried putting the difficulty name in all lowercase? That, and does your Windows user have permissions to write to the mod folder?

[Witherbomb-47]

Creating a difficulty name in all lower-case does not work, and i've managed to successfully create a difficulty (prior to this bug) with a capital letter in it. I'm not sure if my windows user has permissions to write to the mod folder or not (Windows 10 user permissions are a confusing mess), but I've been adding files for my mod without windows defender or a permissions error appearing. One thing to note, this is in my D: drive, but this was working before and i'm unsure what changed.

[r6915ee]

In that case, what does the console show when the freeze occurs? You're able to open to console by pressing F2 or the keybind you've set in the controls menu.

[Witherbomb-47]

The window freezes entirely without showing anything in the console, I've double checked this to make sure.

Also, I'm in the discord if you want to discuss this more directly.

[r6915ee]

The window freezes entirely without showing anything in the console, I've double checked this to make sure.

In that case, do you have any addons or custom changes to the editors running? Codename allows modifying the editors in addition to everything else, so you may have some kind of addon that is causing the problem.

[Witherbomb-47]

I can send you my entire CNE installation in dms, just dm me on discord (@Witherbomb47)

[r6915ee]

I can send you my entire CNE installation in dms, just dm me on discord (@Witherbomb47)

No, thank you; I'm fine with doing this through a GitHub issue, as it allows for others to see the issue and potentially contribute to fixing the problem. In any case, you are able to set up push notifications for GitHub if you're using GitHub on a mobile device of some kind.

On another note, I took a closer look into the video. I've only just now noticed the Charter.hx tab. If that script is coming from your current mod, then have you tried creating a difficulty in a different, "bare-bones" mod? That is, something like creating another modpack (creating another folder in your mods folder), switching into it, adding a song, etc..

[Witherbomb-47]

Disabling my mod and attempting to create a new difficulty results in the same issue, unfortunately

[r6915ee]

Disabling my mod and attempting to create a new difficulty results in the same issue, unfortunately

In that case, what mods did you play before the issue started? Some mods might use a nightly version of Codename instead of a stable version, and they have some differences in the save data, which appears to have caused issues beforehand, often with the highscore system.

[Witherbomb-47]

That might be the root cause. I installed Shaggy's Alternate Universes beforehand to look at the code and work off of, that mod enters a lot of values into FlxG.save.data and I imagine that would have an effect on things.

[r6915ee]

That might be the root cause. I installed Shaggy's Alternate Universes beforehand to look at the code and work off of, that mod enters a lot of values into FlxG.save.data and I imagine that would have an effect on things.

In that case, you may want to either delete your save data files, or move them so that they'll still be available, but they can't be interacted with. The save data files on Windows are usually placed right in <user>\AppData\Roaming\CodenameEngine if the modpack doesn't set the save file location itself.

[Witherbomb-47]

Deleted my save data entirely, the issue persists

[r6915ee]

Hm, I just went through the commit history. You mention that you're using commit a7b0401; however, there is commit a8a5ae7 that was pushed later, which does seem to address a chart editor issue that appears to be quite similar to your issue.

In that case, you may want to update to a later nightly version. Replacing the build files should suffice.

[Witherbomb-47]

That seemed to work. Thank you!