# Frame - v1.0.3 ## Config Migration ### PLUGIN UPDATES - **Your config updates itself.** `config.yml` now carries a `config-version`. When a Frame update adds new settings, they are written into your existing file — with their explanatory comments — the next time the server starts. Everything you have already set stays exactly as it is, including any comments you wrote yourself. Nothing is removed. - **Your old file is kept.** Before anything is written, Frame saves a copy as `config.yml.v<old>.bak`. If that copy can't be made, Frame leaves your config alone entirely rather than risk it. - **Upgrading from an older Frame is now safe.** Configs written by 1.0.0 through 1.0.2 pick up every setting added since, so features like groups, sorting, LuckPerms ranks and the spectator fix become available without rewriting the file by hand. - **Your sorting won't change under you.** If you had customised `tablist.sort-key`, the newer `sorting:` list is added empty so your existing order is preserved, with a note explaining how to switch when you're ready. Configs that never set a sort-key get the new default sorting. - **A config from a newer Frame is left alone.** If you roll back to an older build, Frame warns you and refuses to touch the file rather than quietly downgrading it. ### PLUGIN FIXES - **Tidier config comments.** A commented-out sorting example could drift onto the wrong setting when the file was rewritten. Examples now sit above their setting where they belong.