Our run installed azeroth-survivors-re in 37 seconds; build and tests each timed out after 900 seconds. Use this repository if investigating or changing a local Rust/Bevy reconstruction is your goal. Choose Aethus's original if you want to play without compiling this repository. The distinction matters throughout this review: the source harness used commit 72048f4, the unofficial reference guide uses eb9bbe3, and some tracker reports explicitly concern the original game.
What people use azeroth-survivors-re for
Documented uses include extracting guide data, establishing a fork's test baseline and attempting Windows builds. These examples give a prospective contributor concrete starting points: inspect the extracted game values, reproduce the reported JavaScript mock problem, or follow the WebAssembly setup stages. They also show why a repository review needs more than a feature list. Each use involves a particular source, revision or reporter rather than a general claim about adoption.
| Who used it | What they did | Recorded outcome |
|---|---|---|
| Authors of azeroth-survivors.com | Used repository data and screenshots for an unofficial reference guide | Published references tied to commit eb9bbe3. Guide sourcing policy |
| Reporter of issue #1 | Ran JavaScript checks while establishing a fork baseline | Reported a DOM mock missing style.setProperty and proposed an implementation. Fork-baseline report |
| welcome-dd and Iryn-e in issue #13 | Attempted Windows builds through Git Bash | Iryn-e reported success after manual changes; welcome-dd later reported another compiler failure. Windows build discussion |
| Peed92 in issue #15 | Reported making an Android port | Named an Ayn Thor handheld. Android-port comment |
The guide's sourcing policy is useful for anyone building a similar reference. Its authors identify commit eb9bbe3 and say they leave missing fields unmarked rather than guess. Preserve that revision alongside an extraction so readers can identify which reconstruction supplied a value. A spell name or zone clock taken from that guide belongs to its stated source revision; it should not silently become a claim about the current original game. Guide methodology.
What you can do with azeroth-survivors-re
The README describes a local survivors game on a WoW 1.12.1 client engine built with Rust and Bevy. It credits Aethus, links the original browser game and calls this repository a personal-use source build. For a developer, that supplies a specific object to investigate: the survivors mode lives under crates/benilla-app/src/survivors/, with benilla and wenilla named as upstream projects. Repository README.
The documented game loop is to choose a class and battleground, move with WASD while abilities cast automatically, survive enemy waves and select upgrades as the character levels. The README lists sixteen zones, a class movement spell on F from level 5, and a camera that C unlocks. The mouse wheel changes zoom, Esc pauses, and 1/2/3 selects an upgrade card. These documented inputs give someone reading the engine concrete places to start tracing movement and interface behavior. Documented features and controls.
What happened when we ran it
Our November 15, 2026 source run used commit 72048f4 and completed installation in 37 seconds, with 702 dependencies recorded. Build and tests each exhausted a separate 900-second budget. The configured sandbox had 3 CPUs, 12 GB RAM and image lab-rust:1. Those are the recorded configuration and outcomes of our source harness, separate from the research pack's Compose-based deployment attempt.
| Hands-on question | Answer | Verdict | Why |
|---|---|---|---|
| Did source installation finish? | Yes, in 37 seconds; 702 dependencies recorded | Completed | The harness records a successful installation step. |
| Did the source build finish? | It timed out after 900 seconds | Timed out | The build step reached its allotted time. |
| Did the tests finish? | They timed out after 900 seconds | Timed out | The supplied tail still contains compilation output. |
| Did the separate deployment attempt pass its safety step? | No; the required Compose filenames were absent | Failed | The runner explicitly required a Compose file. |
| What does the deployment summary say? | It claims deployment with its own Docker Compose and ports bound to 127.0.0.1 | Conflicting record | That summary conflicts with the failed safety step. |
| Did teardown report success? | The record says teardown: ok | Recorded success | This is the teardown outcome supplied by the pack. |
The supplied test-log tail contains compilation messages for bevy_pbr v0.18.1, bevy_animation v0.18.1 and gltf v1.4.1, among other crates. The source scan recorded 1,914 files, approximately 764,510 lines of source and a 33.1 MB checkout. It also recorded two CI workflow files, no Dockerfile and no tests directory. Issue #1 separately names JavaScript checks under web/tests, so that directory signal and the issue report describe different observations.
Where people get stuck: Windows scripts and the data path
Issue #13 records a Windows Git Bash build progressing through toolchain errors and ending with another compiler failure from welcome-dd. The initial WASI SDK error rejects the MINGW host and mentions a WASI_SDK override. The discussion also records a binaryen bplat variable error and a later clang startup failure with Win32 error 193. Iryn-e reports getting a build working after manual changes. Windows issue #13.
| Report | Concrete symptom | Action described in the evidence |
|---|---|---|
| Issue #13 | Unsupported MINGW host during WASI SDK setup | Read the host-selection discussion and WASI_SDK override instruction. |
| Issue #13 | bplat: unbound variable | Inspect the binaryen edits discussed in the thread. |
| Issue #13 | clang fails to start with Win32 error 193 | Keep the executable path and exact error with the report. |
| Issue #5 | make build encounters an existing wow-data path | The issue proposes removing the tracked symlink and adjusting the ignore rule. |
| Issue #1 | TypeError: e.style.setProperty is not a function | The reporter proposes adding setProperty to the mock style object. |
Issue #5 describes wow-data as a committed dangling symlink pointing outside the clone. Its local workaround removes that link before retrying make build; its proposed repository change removes the tracked link and changes the ignore rule to /wow-data. Inspect the path before applying the workaround and preserve any real data directory. The relevant distinction is between the reported link and a directory containing your own game files.
Issue #1 identifies the JavaScript mock error at eb9bbe3, where createBootUi calls style.setProperty while creating 26 ember elements. The reporter's environment was Node v24.11.0 on macOS arm64, and the report describes the problem as a deterministic mock gap. Its proposed correction is a no-op setProperty implementation or a map that records properties for assertions. That report concerns a different revision and check from our Rust compilation timeout.
Local play needs external game data
The README requires a WoW 1.12.1 client's Data folder and lists Rust, make, curl, unzip and bash as prerequisites. Its documented make build route chains scripts/fetch-data.sh, scripts/web-setup.sh and scripts/web-build.sh. These respectively fetch and extract game data, install the WebAssembly tools and build into web/dist/. Keeping those stages separate in a bug report helps another contributor identify whether the stopping point was data acquisition, tool setup or compilation. README setup instructions.
The default fetch route downloads the English WoW 1.12.1 client, build 5875, with an approximately 5.5 GB download described in the README. It extracts MPQs into wow-data/Data/. The README also documents --data and WOW_DATA for an existing client, and make start points to 127.0.0.1:8090. These are the project's documented setup instructions. Its game description says local play needs no server, login or account. README data and start instructions.
Engine licensing and game assets have separate terms
The README licenses engine code under MIT or Apache 2.0 and says vendored components retain their upstream licenses. It also says the repository ships no Blizzard content, listing art, models, sounds, maps, MPQ contents and FrameXML. These are separate statements about code and assets. A source checkout, the external game data it reads and screenshots rendered from that data therefore need to be identified separately when discussing what the repository contains. README legal section.
Repository attention and gameplay coverage describe different things
GitHub's November 15, 2026 snapshot reported 685 stars, 275 forks and 15 open issues and pull requests, with an October 26, 2026 last-push timestamp. These figures describe repository attention and activity. The sampled tracker includes source-build problems, original-browser reports and original-Windows reports, so the tracker total combines different kinds of requests. Read the client and revision fields before using an issue to decide which setup path to take. GitHub repository snapshot.
The supplied transcript describes an unsuccessful Scarlet Monastery attempt and a viewer's suggestion to try a tank warrior. That narrower account is what the extract supports from the video titled Azeroth Survivors Endless Mode Is TOO EASY! A reader looking for build ideas can distinguish a player's described attempt from the repository's documented controls or our source-harness timings. The transcript belongs to the gameplay discussion; the measured installation and compilation outcomes belong to our run. Supplied gameplay transcript.
azeroth-survivors-re vs alternatives
Aethus's original is the route the repository itself links for browser play; azeroth-survivors-re is the source-build route for investigating this engine. Vampire Survivors is a separate choice for someone seeking a survival game with roguelite elements. The comparison below turns those differences into a reader decision, using the README for the reconstruction and poncle's own description for Vampire Survivors. Reconstruction README and poncle's Vampire Survivors page.
| Choice | Choose it for | Evidence behind the distinction |
|---|---|---|
| OutThisLife/azeroth-survivors-re | Reading or changing a local Rust/Bevy reconstruction | The README supplies source-build instructions and external game-data requirements. |
| Aethus's original Azeroth Survivors | Playing through the original browser host | The README links wow.aethus.pl; the supplied unofficial FAQ also describes a creator-linked Windows download. Player routes |
| Vampire Survivors | A separate survival game with roguelite elements | Poncle describes time-survival gameplay and upgrades between runs. |
Issue #25 supplies a further platform-specific account: its reporter says an unofficial Linux client returned to character selection after an update to 0.139.0, and reports success using the Windows client through GE-Proton in Lutris. The reporter describes repository ancestry as an assumption and offers an underlying-client update as their explanation. Keep those statements attached to that reporter when considering the account. Linux-client discussion.
What the other reviews get wrong
HotRepo calls the repository legally clean because it excludes Blizzard assets, while the README specifies asset exclusion and engine-code licensing. Replace that broad conclusion with the two source statements. The same care improves platform advice: a claim about the original browser launcher belongs to that launcher, and the README's Git Bash instruction belongs beside the successive toolchain errors reported in issue #13. HotRepo account, README and Windows thread.
The supplied research also records conflicting advice about embedded play and loading screens. The October 31 how-to page says a WebGPU-capable frame runs the original; the later launcher guide reports that framed startup is blocked even at the correct game address. That later guide distinguishes a stalled request from graphics initialization, replacing the older troubleshooting page's fixed one-minute diagnosis with the actual warning or failed request. Older frame advice, older troubleshooting and launcher troubleshooting.
Platform claims also need dates and attribution. The supplied synthesis records a guide reporting a developer x86_64 Linux release after November 4 Discord checks, contradicting browser-only Linux advice. It also records a later launcher guide reporting creator release notes for M1-and-later Mac support, contradicting an earlier categorical no-macOS statement. Those are reported original-game release options, distinct from building this Rust repository. Platform guide and later launcher guide.
FAQ
azeroth-survivors-re is a separate community reconstruction, and its README points to Aethus's original for browser play. That answers the identity question behind several supplied requests: someone seeking the original source, someone troubleshooting a local build and someone reporting a browser-game bug may all arrive at this tracker. The answers below keep each question attached to the relevant repository, client or commenter. Identity discussion and README.
Is azeroth-survivors-re the official source repository or a separate reconstruction?
It is a separate community reconstruction. In issue #21, a commenter calls it a reverse engineered version of the game at wow.aethus.pl, and the requester acknowledges that explanation. The README credits Aethus and describes this repository as a personal-use source build. Use those identity statements when deciding whether a question concerns this code or the original game's development. Issue #21.
Can the original game's source be released so the community can fork and develop it?
Issue #21 contains that request and a reply explaining the reconstruction's identity. The reply is a commenter's account, including their opinion about the original developer's intentions. The practical answer supplied by the thread is where the requester has arrived: this repository contains the reconstruction. The README's local-build instructions describe that code rather than a process for contributing to Aethus's hosted original. Source-release request.
Do I need GitHub or a local build just to play Azeroth Survivors?
No. The README links Aethus's original browser game at wow.aethus.pl, and the supplied unofficial FAQ says the GitHub source rebuild is optional for players. That FAQ also describes an original Windows download. Start with the creator's host when playing is your purpose; choose the repository when the code, local build or reconstruction engine is what you want to investigate. Player FAQ.
How do I fix make build failing on Windows Git Bash?
Issue #13 gives different advice for different stopping points: WASI SDK host selection, the binaryen bplat error and a later clang startup failure. Match the exact error before applying a script change. Iryn-e reports success after manual changes, while welcome-dd later reports another failure. Preserve the failing command and executable path so a follow-up report identifies which stage needs attention. Windows discussion.
Why does make build fail on a fresh clone because wow-data already exists?
Issue #5 attributes that symptom to a committed dangling wow-data symlink. Its proposed repository correction removes the tracked link and changes the ignore rule; its local workaround removes the link before retrying the build. Inspect the path first and preserve any real data directory. That makes the advice specific to the reported filesystem condition instead of treating every existing wow-data path as disposable. Fresh-clone report.
Why does the boot test fail with style.setProperty is not a function?
The issue #1 reporter identifies a mock style object missing setProperty at commit eb9bbe3. Their proposed correction adds a no-op implementation or records the properties in a map for assertions. The report places the error in boot.test.mjs when createBootUi creates the ember elements, which gives a contributor a concrete place to inspect. Our separate source harness used commit 72048f4. Boot-test report.
Are there plans for an Android port, and can the community help?
Peed92 reports an Ayn Thor Android port in issue #15. The original question asks about future plans and community assistance, while the captured reply is a contributor's short account of their own port. For someone interested in that work, the issue identifies a person and device to ask about. It supplies a different kind of evidence from the README's documented local WebAssembly build path. Android discussion.
Why does the unofficial Linux client return to character selection after updating to 0.139.0?
Issue #25 reports that behavior after the update and describes the Windows client through GE-Proton in Lutris as a working route for its reporter. The author presents both repository ancestry and the underlying-client explanation as assumptions. Their useful observation is the sequence: character selection worked, entering the world returned to selection, and the Windows route worked for them. Linux-client report.
Can cache chests spawn at least five yards away from the character?
Issue #7 requests a five-yard spawn buffer after describing chests appearing under a Druid bear character and obstructing a no-cache achievement. The request gives a contributor a specific desired behavior to examine: chest placement relative to the character. Its captured build and setup fields are empty, so the report's own wording, rather than an assumed reconstruction revision, is the appropriate starting point. Chest-placement request.
Why does Soulfire stop at three targets despite additional target bonuses?
Issue #26 reports three targets where the player expected four after combining Atiesh's +1 with a +2 level-up bonus. That is the player's described discrepancy, rather than a measured targeting result from our run. The captured issue leaves build and setup blank. A useful follow-up would attach the client and revision to the same bonuses and observed target count. Soulfire report.
How can players recover from falling through the floor in the original Windows client?
Issue #24 concerns the original Windows client and describes falling through floors or becoming stuck before falling. A commenter redirects the reporter because this tracker belongs to a reverse engineered copy. Keep that client identification when seeking help: the supplied report mentions Gurubashi, SM, AQ and Naxx, while the comment explains why reporting the symptoms here led to an identity correction. Floor-collision discussion.
How do I restore a disappearing cursor and stop camera movement in the original browser game?
The issue #11 reporter says clicking the left and right mouse buttons restored the cursor on wow.aethus.pl. The same report describes camera movement with mouse input and a disappearing cursor during play. Attribute the button combination to that reporter and original-browser context. The reconstruction's README separately documents C for unlocking its camera, so these two pieces of advice concern different described situations. Cursor report.
What we have not tested yet
The supplied attempts contain no completed reconstruction playthrough, passing source build or completed test suite. The 900-second timeouts give the source harness's outcome without identifying a cause on another machine, and the compilation tail contains no failing assertion. Actual runtime and operating-system versions require raw toolchain logs; lab-rust:1 is an image label. The contradictory Compose summary needs reconciliation with the failed safety step before it can support a completed deployment claim.
A clean Windows build, an applied issue #1 mock correction with a passing rerun, and a landed issue #5 repository correction are outside the demonstrated results. Original-to-rebuild save transfer, update compatibility, gameplay parity and comparative performance also need evaluation. The unofficial Linux client's ancestry lacks independent confirmation. The Android comment supplies no artifact, installation procedure or device matrix. The platform-guide accounts do not supply our own Linux or Mac installation results, and the sampled issues do not measure support responsiveness or active adoption.
The supplied video extract supports an unsuccessful Scarlet Monastery attempt and a tank-warrior suggestion, without establishing the character class used in the failed attempt or a successful warrior run. Videos and Bilibili titles do not tie talents, permanent equipment, Heroic play or T0.5 sets to commit 72048f4. The chest, Soulfire, floor and camera reports supply no demonstrated reconstruction fixes; several omit build identity or concern the original. The pack contains no lab screenshot records. Malware analysis, network auditing, legal conclusions, rendered layout and research-link resolution are also outside this text review. The next useful evaluation is a completed build and playthrough with the toolchain and revision recorded.


