# How Script Updates labels builds and assigns a status

> A build is recorded only from a seller's public, dated announcement, with the version name copied as published and set against the game patch it followed.

- Canonical: https://scriptupdates.com/updates/how-versioning-works
- Site: Script Updates (https://scriptupdates.com/)
- Author: Ryan Kessler (https://scriptupdates.com/authors/editorial)
- Section: Method
- Published: 2026-10-10 · Updated: 2026-11-14
- Tags: method, build labels, status, patch response

---

## Where do version names come from?

From the seller's public announcement, copied as written. VeraScripts names its builds in its [update log](https://verascripts.com/updates), for example Demon V6.1, Reaper V1.9 and Fadeaway 2.5.1. A version name is treated as a name, and no sequence is read into the numbers.

A seller that publishes no version names or dates gets no release entries, whatever its product page promises about updates.

## Release entries and running pages

The log is made of two kinds of document.

A release entry describes one build. Its title carries the version and date, and its facts panel shows the status on the day the entry went up, above a changelog block of what the seller says changed. If a detail proves wrong, a dated correction explains the amendment. The publication date and seller release date remain separate from the revision date.

A running page grows by rows, one patch log per game. Each edit moves the updated date in the byline, while every row keeps the date of its own patch.

## What does a patch row record?

One row per game patch, built from the publisher's own notes and linked to them:

- the release date and the platforms it covers, which can differ: NBA 2K27 v2.0 came to PlayStation 5 and Xbox Series X|S on 8 October 2026, with Nintendo Switch 2 and PC following eight days later
- the lines a timing or anti-recoil script leans on, such as Takeover timing windows, contest rules or a dunk-meter fix in NBA 2K27, and a recoil percentage or a new fire rate in Call of Duty

The rest of a patch note stays with its publisher: Call of Duty rows link the studio's own page on callofduty.com.

## What do the status words mean?

| Status | Meaning on this site | Record needed |
| --- | --- | --- |
| release recorded | The seller has published this build with a date | The seller's dated announcement, linked from the entry |
| historical record | An entry kept for reference once newer patches or builds have followed it | The original sources, still linked |

A status describes the record. Release recorded means the build exists and when it came out; it does not mean the script was run on the current patch. Reports on Discord or Reddit that a script broke are followed up, but on their own they change no entry.

## How is time to update counted?

In hours when the patch and the build both carry a published time, and in calendar days when they do not. A seller's promise of same-day updates does not count as a dated build.

The sourcing rules behind every row are in the [editorial policy](/editorial-policy), and the entries themselves are in the [changelog list](/updates).

## FAQ

**How does Script Updates track Cronus script versions?**

Only from releases a seller has announced in public with a date. The version name is copied as the seller writes it, the announcement is linked, and the build is set against the game patch that was current on its date.

**What does release recorded mean?**

A dated seller announcement was found and is linked from the entry. It shows what the seller published and says nothing on whether the script works on the current patch.

**Why do some scripts have no entries?**

Their sellers publish no versions or release dates for a reader to check. When their pages were read on 14 November 2026, that held for Lura, YewScripts and EmberZens.

**How quickly are scripts updated after a patch?**

It can only be measured when the patch and the build both carry a published date. None of the releases on record so far is announced as the answer to a particular patch, so no response time is printed.

