Price-drop watch: how we track Cronus Zen script prices over time

Every product on CronusMarket has a price history. On Sep 2, 2026 each history had one point; every manual recheck that reads a price adds another, dated, whether or not the number moved. A drop is a lower readable checkout price than the previous point for the same offer and billing term. Compare-at prices never count, because on our launch check every "sale" in the market was live at once. The product page renders the history as a sparkline; the public dataset at /api/status.json carries the current values.

Why start a history with one point?

Because a comparison site that launches with fabricated back-data is lying, and one that launches with none is honest but thin. We chose thin. On Sep 2, 2026 we recorded one price per offer, dated, and we drew a flat line through it. Every product page says so: one point, checked Sep 2. As rechecks accumulate, the line gets interesting. The alternative, inventing a plausible curve, would make the site look mature at the cost of making every sparkline a fiction.

What is a price point?

A price point is: an offer (a specific product on a specific storefront), a billing term (one-time, monthly, yearly, lifetime, free), a readable price in USD, and a date. If the price is not readable in page text (embedded widget, library "value" label), no point is recorded and the offer shows "See vendor page". Nine offers had no readable price at launch.

A recheck that reads the same price adds a point at the same level. That is deliberate: a flat line over eight rechecks tells you the price has been stable for eight rechecks, which is different from a flat line over one.

What counts as a drop?

A lower readable checkout price than the previous recorded point, same offer, same term. Three things that are not drops:

A compare-at price appearing or growing. yewscripts.com shows $90 regular over $65; hoopers.gg, auto-green.gg, secretzens.com, syna.gg and FeatureZens show $100 over $50 to $64.99; ClipZ Aim shows $450 over $124.99. Every one of these was live on Sep 2. A strike-through that is always there is the list price's costume. We display them and never count them.

A promo code. Cronus Zen Central's Basic lifetime was $50 with the code "2K27" (ending Sep 6) against $70 regular. We record both the promo price and the regular price, with the code and the end date in the notes. When the code expires and the price reverts to $70, that is recorded as a rise from the promo point, which is accurate.

A cheaper storefront for the same script. Green at $50 on auto-green.gg is not a drop from $65 on yewscripts.com; it is a second offer. Gaps between offers appear on the home page's price-gap board, not in a single offer's history.

What did launch week show?

Two storefront gaps of $15 each (Green, Hoops). One promo code with a stated end date. One vendor (cronus.gg) with conflicting copy ($35 tagline, $55 blurb). One nine-game bundle ($124.99) whose per-script math looks generous until you notice the 2K script inside is the 2K26 build. And a market in which $50 to $65 was the creator price for a single-game script in every game with more than one vendor.

None of that is a trend yet. It is a baseline.

What will we watch?

• The Sep 6 promo expiry at Cronus Zen Central: does $50 become $70, or does a new code appear?
• The Sep 4 worldwide NBA 2K27 launch: do any 2K27 prices move once the full player base arrives?
• The Oct 16 Season 2 patch: do vendors that need to ship updates change prices around it?
• The two $15 gaps: do they close, widen, or get matched by other vendors?
• The hidden prices: do any of the nine widget-only checkouts, or the eight Discord and library entries with no public price, surface a readable number?
• The $35 / $55 conflict at cronus.gg: which number does the checkout show?

Each of these becomes a dated point or a dated note on the relevant product page.

What we will not do

We will not scrape vendors continuously. Rechecks are manual, on a cadence that prioritises patch days, which means a price that dropped for an afternoon and reverted may never be recorded. We would rather have a sparse, honest history than a dense one built on automated fetches that misread widgets. If a reader sends us a dated screenshot with a URL, we verify against the live page and record what we can confirm.

We will also not infer a drop from a strike-through changing. If yewscripts.com's $90 "regular" becomes $95 with the sale price still $65, nothing has happened to the price you pay, and the history stays flat.

How to use the history

On any product page, the sparkline shows the offer's recorded prices over time with the current price and date beside it. A flat line means stable across our rechecks; a step down means a recorded drop; a gap means we could not read a price on that check. The public dataset gives you the current values for every product in one request, cached an hour.

If you are timing a purchase, the history tells you whether the vendor moves prices at all. In launch week, none did. Prices as of Sep 2, 2026; the product pages have moved on.