To ensure the editor has data to "work" with, you must implement basic Save/Load calls in your scripts: // Saving a value with a unique key "playerScore"
The ES3 Save Editor is a testament to a bygone era of utility software—functional, dense, and unforgiving. Its interface resembles a database management tool more than a gaming app. A typical session involves navigating nested tabs: "Stats" for attributes, "Skills" for proficiency, "Inventory" with a searchable list of thousands of items by their internal Editor IDs (e.g., bm_arrow_bomb for a Bomb Arrow from Bloodmoon ).
Morrowind saves accumulate "garbage data" over time—references to objects that no longer exist or items that have been moved and forgotten. This bloats save files and causes stuttering.