SkriptlyShipping the script is the start. This page covers updating it, helping buyers when something breaks, and the tools you get for keeping an eye on it.
Releasing an update
Upload a new version from the script's page in your dashboard. It goes through the same scan and review as the first one, and you're Discord-DMed when it's decided.
- Use a new version number each time, and write a changelog: buyers see it.
- Keep the compatibility accurate. The version history shows what each release added or dropped, so changing the list is visible.
- Once approved, buyers' servers pick it up on their next restart or
/skriptly reload, and the loader tells them an update is available. A buyer can pin a version to hold back an update that doesn't suit them, so keep older versions working where you can.
If an update turns out to be bad, moderators can pull it, and the loader switches affected servers back to the latest good version.
When it breaks after a Skript or addon update
Skript and its addons change quickly, and this is the most common problem. Buyers use Broke after an update? on your script's page to tell you what stopped working, with the script version, their Skript and Minecraft versions and any addons.
- You're Discord-DMed straight away, and the report appears on your script's page in your dashboard.
- Answer it: I'm looking into it or Mark as fixed, with an optional note. The reporter is Discord-DMed whichever you choose.
- When several reports are open, the page points out what they have in common, such as "4 of 6 reports are on Skript 2.12". Start there.
Reports have dates, and the refund policy uses them: if a paid script stops working because of an update and isn't fixed within 30 days of a report, Skriptly may offer the buyer a partial refund. Answering early, even with just "looking into it", is the best way to stay clear of that.
Seeing how it's doing
- Downloads, sales and what you keep, as 30-day charts on your dashboard.
- Page views and conversion on each script's page. A view is a page load, not a person, and your own visits, moderators, bots and visitors who ask not to be tracked aren't counted. Skriptly keeps no cookie or address behind these numbers.
- Servers running it, for paid scripts, and a public "Running on N servers" count on the listing once it reaches three.
Alerts in Discord
In Settings you can connect a Discord webhook to get alerts for sales, review decisions and breakage reports. Alerts name the script but never the buyer or the person reporting, and the webhook address is stored encrypted and never shown again. If Discord stops accepting it, alerts switch off and you can turn them back on by pasting it again or sending a test message.
Removal and takedowns
Moderators can remove a version or take down a script if it breaks the content policy. For a paid script that stops it loading on buyers' servers at their next check-in (the loader checks in every 30 minutes), and you'll be told why.
Status
If buyers say scripts won't load, check the status page. Servers keep running a licensed script from their last check-in for up to 72 hours if Skriptly can't be reached.