Docs / Maintaining Scripts

Maintaining Scripts

Once a script is running, keeping it healthy comes down to two things: applying updates without losing your config, and knowing where to look when something breaks. Both are covered in depth on the pages below; this page is the short version.

The basics

• Updates are free for life. Every fix and improvement to a product you own ships as a free update. We never charge for a "v2" of something you've already bought.
• Always back up config.lua first. It's the file most likely to hold your own changes, and it's not touched by the update itself.
• Check the changelog before reapplying config. New versions sometimes add options that didn't exist in your backed-up copy, so a straight overwrite can silently drop them.
• Console errors almost always mean load order. Before assuming a script is broken, check that its dependencies are ensured above it in server.cfg.
• Subscription members update the same way as anyone who bought outright: just re-download from Keymaster whenever a new version ships.