Defend Your Base From Scary Worm About This Wiki

This site is a fan-made wiki for Defend Your Base From Scary Worm on Roblox. It is not an official Evil Worm Simulator product, not a TreeTrunk_290 page, and not affiliated with Roblox Corporation. We do not take a cut of exclusive crates, we cannot restore a banned account, and we cannot publish a Discord invite that the group has not confirmed. If you need the play button, use official links. If you need the missing-Discord explanation, use community links. The rest of the links hub is the drawer those two pages sit in.

We exist because the title is easy to mix up, the loop is easy to explain badly, and search results are happy to sell you another worm game’s maps. The facts we keep repeating are the facts we can source.

What this wiki covers

• Game: Defend Your Base From Scary Worm
• Platform: Roblox, free, co-op, up to 35 players per server
• Group: Evil Worm Simulator (verified), owner TreeTrunk_290
• IDs: place 85070260180613, universe 9812090239
• Dates: released 28 February 2026, updated 3 September 2026
• Loop: claim a base, build and upgrade units, repair the wooden door, defeat the Scary Worm

We document starter cash around 450, spear throwers, money printers and farms, mortars, a door that players try to hold near 400 HP, a worm that heals and can show a bar like 748,293 / 999,999 (worm HP, not door HP), wave 13 callouts, a ~25 second “releasing boss” countdown, rare units, a blue high-tier unit around 16,000 cash / ~120 damage, gems, exclusive crates, and multiple difficulties. We do not document Forest, Desert, Freezer, or Lava maps. Those belong to a different experience.

What we refuse to invent

• Working promo codes. Creator Exchange lists none as of September 2026. The codes hub stays empty until a real string ships. How to redeem is a UI guide for a box that does not exist yet. Group rewards is the like-and-join bonus the description already advertises.
• A public Discord invite or Trello. See community links.
• A script loadstring for this place ID. None verified. The scripts hub and its subpages describe features and TOS risk only.
• Other games’ systems. Defend Your Base from 67, Find the Scary Worm, and zombie-base titles are out of scope even when thumbnails look similar.

If a sentence on this wiki ever contradicts those rules, the sentence is wrong.

How we source facts

Primary sources, in order:

1. The Roblox experience page and its IDs (visits, favorites, CCU, copy, like-and-join text).
2. The Evil Worm Simulator group (membership, owner, shouts).
3. Footage of this place ID — night-grass bunker, wooden door, cream-colored segmented smiling worm — not stock tower-defense video from a neighboring title.
4. Patch timestamps such as 3 September 2026, collected on the updates hub.

Secondary sources (Medal clips, recap videos) are allowed when the HUD matches. They are not allowed to overrule an empty codes field or a missing invite. We would rather publish “none” than a comforting lie.

Getting started is the onboarding page those sources collapse into. Play facts (door HP, printers, boss countdown) belong in guides. URL facts belong in the links set. Automation facts belong in scripts as warnings.

Languages

The wiki ships English, French, German, Spanish, and Brazilian Portuguese. English lives at the root. Other languages use a prefix (/fr/, /de/, /es/, /pt/) and the same trailing slash on every page URL. Legal pages (/terms/, /privacy/, /cookies/) stay English-only. In-article links are written without a locale prefix so each language build can point at itself.

We aim for the same depth in every language, not a machine-translated stub under the English article. If a translation lags, that is a bug, not a stub placeholder with noindex.

How pages are structured

Hubs (codes, scripts, links, guides, updates, and the rest of the nav) collect child pages. Child pages interlink with their siblings. We keep one topic per URL so “codes” does not bury “group rewards” and “scripts” does not bury executor safety. Titles on hubs include the word Hub. Descriptions stay short enough for a search snippet after a freshness stamp.

You should be able to enter from Google on a leaf page, climb to the hub, and reach official links without hitting a dead slug. If you find a dead slug, the source JSON is wrong — we do not hand-edit generated article files to hide that.

How to use this wiki without getting misled

• Check the place ID before you apply a tip from a video this article embeds or cites.
• Treat month stamps on titles as “last generated,” not as a developer patch note.
• Do not paste anything from the scripts hub into an executor; there is nothing to paste, on purpose.
• Do not skip the wooden door because a crate page was more fun to read. The lose condition is still the door.
• Share the language you actually play the Roblox client in. A Portuguese reader should not be sent to the English /codes/ path by a hand-copied URL if a /pt/codes/ page exists.

Corrections

When the group posts a code, an invite, or a map this game did not have yesterday, we update the source facts and the English articles first, then the other locales. We do not silently keep a fake working-code table up “until someone notices.” The empty table on the codes hub is the feature.

If you are Evil Worm Simulator and you want a link changed, the official URL is already on official links. This about page will still say we are unofficial, because we are.

We correct pages when the group wall, the Roblox listing, or footage of place 85070260180613 disagrees with us — not when a 67-game recap uses a similar worm smile. Month stamps on this fan wiki follow the article fingerprint, while the 3 September 2026 client date stays a sourced patch. Until TreeTrunk_290 posts a code, a Discord invite, or a Trello, those rows remain honest blanks instead of filler.