WoW Forever Beta: Stuck at 100% Loading After the Tram or a Flight?

Which transitions are being reported? #

The reports describe several travel and login situations. Similar symptoms do not prove that every case has the same cause, or that every character using these routes will become stuck.

Can other characters still load? #

Yes, according to some reports. One player could load other characters and create new ones while a character at the Loch Modan inn remained inaccessible. Another could access a Stormwind bank character while characters near Loch Modan failed. Other replies describe a second character becoming stuck, or a newly created Skyborne failing to load.

If you already have an alternate character in another area, one login check can help describe the scope of your problem. Keep it away from the reported transitions while checking. Success on that character does not recover the original one or identify the cause. If every character fails, record that difference instead of assuming this narrower pattern explains your case.

Which recovery claims remain untested? #

Recovery is inconsistent. The October 9 reply at 08:12 PDT still reports failure after 24 hours on both Mac and PC. A later reply reports access returning after 12 hours. Kingy has not reproduced a recovery for this cluster.

These posts describe outcomes after elapsed time or attempted changes. They cannot establish which action caused a recovery. Keep failures and relapses alongside successes when comparing a claim.

What to do while the character is inaccessible #

Preserve enough detail to distinguish a login failure from an install problem, a crash or an unavailable account. A concise beta report is more useful than a list of changes with no before-and-after result.

1. Record the installed beta build, OS, test realm/ruleset, character and last accessible location. Include the date, time and time zone.
2. Write the exact transition and direction: entering the Tram, taking a named flight, crossing a zone boundary or logging back in at an inn. Note any disconnect before the loading loop.
3. Record whether the bar reaches 100%, how long you observed it and the exact error, including WOW51900319 or WOW51900328 if shown. Audio behind the loading screen does not prove that controls are usable.
4. If an existing alternate character can safely be checked, record its location and whether it loads. A working alt is a comparison, not a recovery step.
5. Report in the WoW Forever Beta Discussion category. Include each attempted action, its result and any relapse; avoid posting account credentials or personal account details.

Save loss and the older Mac advice #

An inaccessible character does not establish that its progress has been deleted. Permanent save loss from this cluster is unverified. Preserve the affected character while documenting it; deleting and recreating it would prevent a later comparison of its state.

Our Mac Enter World page covers older hardware-specific reports on a named September build, with mixed Secondary Lighting outcomes. The October 9 cluster includes a player reporting the same failure on Mac and PC. The older lighting suggestion is not evidence of a fix for the new travel/login symptoms.

What a useful symptom and recovery video needs to show #

No firsthand symptom or recovery video has been recorded for this report. A useful test should use disposable beta characters whose progress the tester is willing to lose access to. Leave established characters out of reproduction attempts.

A short edited video can show the key moments, but retain the full original recording and elapsed times. Label cuts and distinguish a proposed recovery from one that succeeded in a recorded test.

• Show the client build and starting location, then the exact transition, 100% loading stall and any disconnect/error.
• Check a separate disposable character in another area, so viewers can see whether this is limited to one character.
• For a recovery claim, show the failed baseline, change one variable, record the waiting time and show the same character loading afterward. Repeat the comparison before calling it reproducible; a recovery after waiting alone cannot identify a cause.
• If access returns, show whether the character’s progress remains and note any later relapse. Keep unsuccessful attempts visible in the results.
• If no recovery repeats, publish the symptom demonstration with that result. Do not label graphics changes or reinstalling a fix without reproducible evidence.

KEEP GOING

Your next step.