Update watch / update

Horde Defenders tech tree: Sep 25–29 refund notices

A Sep 25 developer-group announcement and Sep 28 official description discussed a tech-tree refund; the later description omitted its notice. Current account refunds and upgrade rules remain unverified.

Quick answer

A September 25 developer-group owner announcement addressed reported data loss and a tech-tree refund. A September 28 Roblox Games API snapshot also included a refund notice; the September 29 07:15 UTC response omitted it. These are dated public statements, not evidence that a particular account received a refund or that the present upgrade tree works in a particular way.

What changed in the official description

The September 28 19:26 UTC monitor snapshot opened with a tech-tree refund notice. A September 29 01:09 UTC Games API response omitted that opening notice and changed the title to [HEROES] Horde Defenders. A fresh official Games API response at 07:15 UTC still omitted the notice. The earlier announcement remains a historical record; its absence from a later description does not prove that the refund was reversed, finished, or that the tech tree now works in a particular way.

A separate public announcement by the owner of the developer's Roblox group was created September 25 at 09:24 UTC. It responded to reported data loss by saying tech-tree spending had been refunded and invited bug reports if an account still needed review. The group's announcement archive remained publicly readable when checked September 30. This supports what the developer said at that time, not the outcome for every player or the present menu.

How the old notice was checked

A site-hosted excerpt linked under Sources transcribes the earlier notice from our saved September 28 Games API response and shows its endpoint, Universe and Place IDs, acquisition time, and raw-file SHA-256. The excerpt is our copy, not an official historical permalink or the full raw response. The separate September 25 developer-group announcement has a live official archive link below. Neither record verifies a player's current refund.

An earlier official Roblox UPDATE 1 event was scheduled for September 20 and advertised a “Soft Rework” with bosses, new levels, a new tech tree, and a new UI. That event notice is evidence of what was announced at the time, not proof that those features were deployed or that the current tech-tree menu matches it.

Why old screens can mislead

An official wide thumbnail advertises a “Definitive Upgrade Tree.” The current Games API does not describe the refund or current tree behavior. That promotional image and the earlier notice cannot establish the current menu, balances, or compensation for a particular account.

Before following a tech-tree guide

Use the linked Roblox Games API to inspect the developer-maintained description for this exact Universe ID. Compare it with the dated site-hosted excerpt and September 25 group announcement below when interpreting older guidance. The group's shout field being null does not make its separate announcement archive empty.

  1. Check the latest developer description and in-game notices for a change to the refund statement.
  2. Compare any guide’s screenshot and build date with the current interface.
  3. If a balance or progression guide relies on pre-refund nodes, require a fresh current-build check before using its route.
Current state remains unknown

The refund notice was absent from the September 29 07:15 UTC official description. The September 25 group announcement remains a historical statement. We have not verified the present in-game tree, refund state, affected accounts, or a replacement progression system.

Common questions

Was the tech tree removed?

An earlier official description announced a refund, but the current description omits that notice. Neither version establishes whether the present in-game interface exists or was removed.

Why did the refund happen?

The September 25 group announcement responded to reports of data loss, but did not give a technical cause or establish any particular account's outcome.

Sources and checks