Just like in Flowey's Time Machine, this save editor could benefit from a mode where more advanced flags can be edited. We don't currently have a grasp of all the flags and their meanings... but some of the more obscure flags are listed as (Advanced) in research/save.yml, and these would be suitable for a flags editor for more advanced users.

Instead of just Ceroba and Martlet, obj_debugger and obj_dev_console (I think those are the names) could be useful for setting as followers, to activate some debug features.

There's no Necklace in the editor. It's displayed as Nothing if loaded from a file

Save.sav

uty-save-editor.netlify.app

To make the 'load from template' option more useful, there should be more save files to pick from. The key problem here is identifying which save files would be useful as starting points, and then optimizing their inventory and equipment for the occasion.

Currently, there are several issues arising from location controls not synchronizing between themselves:

1. When changing the room, the room name does not update.
2. When changing the room, the X and Y coordinates stay the same so the map may be way out of the location picker.
3. When the SAVE room is not in the picker, the "Show only SAVE locations" control needs to be updated to reflect that.

This could be solved by extracting location-related controls into a separate component with state of its own.

Genocide data, such as how many kills are left and whether Genocide has been completed in an area, should be editable through the editor.

The Genocide Route kills table could display a "where" button that shows you the maps on which more monsters are left to kill.

Currently, in the temporary save editor, Flowey's regular attacks are just named "Attack 1", "Attack 2"... they should have more descriptive names so that players know which attacks are they selecting.

Many times in the code, there are repeating save="save" section="Save1" and similar constructs. We know that for the same save editor the same save should be edited, and for the same section of the editor (usually) the same section of the save file should be edited, so we could pass this information through context. This information never changes, so we don't need to worry about useless re-renders.

Similarly to #2, battle stats need to change whenever equipment or LV changes. This is pretty important because it's not obvious at all that when changing equipment, primary/secondary AT/DF should be changed as well.

When doing a genocide route, I set all my stats to 9999999999999999999999 and gave myself friendliness pellets and yet I still do 5 damage to flier, did I set the values to high or is this a bug? [[NOTE]] I set myself to LV.20 but then I killed a Flier I went to LV.21.

These unfinished sections are supposed to contain many important flags we discovered so far, such as which bosses have been killed. Not all flags should be listed under these sections, but the ones we discovered so far seem important enough to be added.

Detect when users load a save file where a Genocide Route has been aborted in the Steamworks by going past the point where the encounter list is cleared, and ask them how they want to fix it (restore encounters, set Genocide as complete).

"Factory - Offices [SAVE]" should be the third floor of the Steamworks Factory, but that room is currently named "Factory - Third Floor". This issue is for me to check out what's with that.

Currently, users can only save their user templates, but not delete them. Once their user template storage overflows, removing specific user templates is not going to be very easy without an interface for it.

If the user has already passed Axis, and loads the save file, the editor fixes them back onto the Genocide Route but does not update the level to LV 19.

Right now, all saves are under the same context and controls that modify save file data (all of them) use the same context. This means that all the controls re-render whenever any control changes save file data. This does not currently create performance issues (aside from ones with the Steamworks ID editor... which were patched rather horribly) because the editor is not very big, but could create them in the future.

The solution to this is to have save files as state in the app, passed to their respective editors and controls through props. This way, only controls whose values were actually changed get re-rendered.

The editor doesn't allow you to change your current room to rm_mainmenu_debug, and doesn't seem to recognize files with it, defaulting to "Dark Ruins - Entrance".