Choose the matching symptom
| What you see | Start here |
|---|---|
| “This browser has no WebGPU” | The browser is not exposing the required API. Check the browser and HTTPS address in WebGPU checks. |
| “WebGPU found no usable graphics card” | The API exists but no adapter was obtained. Check acceleration, driver and GPU selection below. |
| Busy notice with HTTP 429 | Stop repeated refreshes and retry later; the launcher associates 429 with its request limit. |
| Download counter keeps advancing | Let it finish; client download and interface startup are different stages. |
| Black canvas or “failed to start” | Open the original URL directly, then record the full startup error. See black-screen checks. |
| “WebGPU device lost” after loading | The graphics device stopped responding. See the restart and driver checks below. |
| Import/module error immediately after an update | Try a cache-bypassing reload, not a save reset. |
| RAR will not open or Windows blocks a file | Use the Windows download guide; archive and security warnings are separate from browser startup. |
| Waiting for the host | The game loaded; the host has not entered the selected zone. |
| Zone or Heroic access error | Check the selected hero’s unlocks in the co-op guide. |
| Progress seems missing | Use the original browser profile and read save recovery before clearing anything. |
Check WebGPU support
- Open
https://wow.aethus.pl/directly. WebGPU requires a secure context; a downloaded HTML copy or a third-party frame is not the same entry point. - Update the browser and operating system. The creator names Chrome, Edge and Safari, but a browser name alone does not establish support for your hardware.
- In Chrome, open Settings → System and check Use graphics acceleration when available, then relaunch after changing it. Enter
chrome://gpuin the address bar and inspect the WebGPU status. “Software only,” a blocklist message and a missing adapter are useful details to report. - Update the graphics driver through your device or GPU vendor. On a Windows laptop with two GPUs, the launcher specifically suggests Settings → System → Display → Graphics, choosing the browser’s high-performance GPU, then restarting the browser. Test whether the error changes.
Chrome’s official troubleshooting page distinguishes a missing API from an unavailable adapter. A driver blocklist or a managed-device policy needs diagnosis; this guide does not use experimental flags to override those protections.
On a managed device, graphics policies may be outside your control. If browser play remains unavailable, the creator’s Windows download route is an alternative for a suitable Windows device. It is not a confirmed fix for every graphics failure.
Busy server or HTTP 429
The public launcher shows its busy notice when startup reports HTTP 429. Stop repeatedly reloading and try later, or follow the creator’s download/community links. This notice does not mean your graphics settings or save file caused the problem.
This guide has no live capacity reading. A successful visit to the launcher is not proof that all game resources or the co-op service are available.
Record the failing URL and status if the browser shows them. A 404 means a requested resource was not found; it is not the same signal as 429. If a fresh visit still fails on the same resource, report that resource rather than repeatedly changing graphics settings.
Read the loading stage
The current public loading script separates these stages. It does not promise a fixed loading time.
More columns → Swipe, or focus the table and use the arrow keys.
| Stage | What it tells you | Useful next action |
|---|---|---|
| Downloading client, with bytes or a percentage | The client file is arriving; the transfer can overlap compilation. | Wait while the counter changes. If it stops with an HTTP error, record the code and resource. |
| Downloading game data or a file counter | The launcher is fetching additional data. | Check whether the counter changes; do not assume the client percentage alone means startup is finished. |
| Starting / Loading interface | Startup has moved beyond the initial transfer. | If it stays stuck, collect the first startup error instead of treating it as a slow download. |
| Preparing world data near the picker | The launcher is preparing resources for world entry. | Allow that preparation to finish before using the first zone entry as a performance comparison. |
| The picker works but entering a zone freezes | Basic startup succeeded; the failure is later. | Report the selected zone, difficulty, class and whether it happens only on first entry. |
The prefetched-data counter can advance even when an individual request fails. A full bar by itself does not prove every resource loaded successfully. If you inspect Chrome’s Network or Console panel, copy the relevant error text; you do not need to paste commands into the console.
A black or stuck screen
- Open wow.aethus.pl directly, outside a third-party frame.
- Use the loading-stage table to distinguish an active download from a failure after startup. Copy the exact message, including any HTTP code or “device lost” wording.
- Close other graphics-heavy tabs and reload once. If the same failure repeats, restart the browser and check updates and graphics diagnostics. Repeated device-loss errors need the device/GPU details and the action that triggered them.
- If a request is explicitly marked as blocked by an extension, review that extension’s permission for the original game page. Do not turn off browser security or antivirus as a blanket loading fix.
- If testing another profile or browser, expect separate local progress. Return to the original profile to export a backup first whenever it still works.
On Android, the current launcher contains specific shader-workaround defaults. On iPhone/iPad, it handles browsers without element fullscreen. These measures show that the launcher has mobile paths; they do not guarantee that a particular phone will run without graphics crashes. Report your exact phone, OS and browser rather than only “mobile.”
If the picture works but audio is silent, click or press a key inside the game and check the tab and system volume. The launcher resumes browser audio after an input gesture; silence alone is not evidence that the client failed to load.
Refresh old files without resetting progress
A normal refresh can reuse cached files. The launcher uses versioned script URLs to keep its JavaScript and client paired; an old module with a new client can produce an import error after an update.
- Export a save first if the game still opens. Close duplicate game tabs so you are testing one copy.
- In Chrome, use Ctrl + Shift + R on Windows/Linux or Command + Shift + R on macOS. Chrome documents this as a hard reload that bypasses cache.
- Reopen the original game address and record whether the error or displayed version changes.
- If it still fails, keep the error text and report it. Clearing all cookies, site storage or a browser profile is a different action and can remove progress; it is not the next automatic step.
Keep the save intact
Do not begin by clearing site data or reinstalling. The checked client has Options → Saves with export, import and local backups. Follow the backup and restore steps before making a change that removes browser storage.
If an old embedded or copied page displays the creator’s wrong-site warning, the current launcher can also offer Download your save when it finds accessible local progress. Save that file before leaving, then follow the import instructions on the original site. The button is conditional: its absence does not prove that a different browser profile or storage partition has no save. This recovery path is visible in the public launcher source.
Send a useful bug report
- Exact error message and the stage where it appears: download, picker, run or co-op join.
- Browser version, operating system and any relevant graphics diagnostic.
- Game version and whether opening the original URL directly changes the result.
- For a loading error: the last stage shown, failing resource URL and HTTP status, if available.
- For device loss: GPU/driver or phone model, and whether it happened during loading, zone entry or a particular spell effect.
- For co-op: the host and guest versions, chosen class, zone and difficulty.
Use the creator’s community. Describe the failure first; do not publish private lobby passwords or your save file.
Sources & scope
Public launcher and loading-script branches rechecked October 29, 2026, with Chrome’s official troubleshooting guidance. Save and co-op menu instructions refer to the v0.125.0 snapshot. This is not a live outage monitor or a device compatibility benchmark.
Aethus: original gameBrowser entry, Windows download and creator community link. Checked October 29, 2026.
Chrome: WebGPU troubleshootingBrowser vendor guidance on graphics acceleration, adapters and platform support.
Game client and version recordGameplay reference: original client v0.125.0, rechecked October 29, 2026. Live v0.127.0 was also observed that day; interface descriptions were compared, but talent execution rules and combat balance were not revalidated for the newer build.
Creator’s current launcherPublic launcher diagnostics, WebGPU checks and wrong-site save recovery. Inspected October 29, 2026.
Creator’s loading stagesClient transfer, interface initialization, resource preparation and HTTP errors. Inspected October 29, 2026.
Chrome: reload without cacheHard-reload shortcuts; cache refresh is separate from removing site storage.