RadiantGames

APP · PLAY DESK

One player.
A clear next step.

Bookmarks stay on this device.

RADIANTGAMES APP · SESSION SUPPORT

Browser game not loading? Find the stage that stopped.

Browser game not loading? Identify a demo download, arena connection, game menu or file prompt, then take the next step for QuakeWorld, Uplink or Diablo shareware.

Start with what you can see.

01

A number or progress bar is changing

Let this download finish. Restart begins a new attempt.

02

A menu is already visible

Use the project’s start sequence; movement comes later.

03

Only a connection message remains

Check the same arena project in its original tab.

KEEP THE PLAYER IN REACH

Which session are you working on?

Choose the player so you can return to the same launch instructions.

Choose a player →

The guide works without selecting a player.

THE NEXT USEFUL CHECK

Keep one clear step in view.

A visible download is different from a stopped game

Watch the project’s own progress before using Restart. Engine and asset preparation happen inside the third-party window. A changing indicator is evidence that this attempt is still advancing; the App cannot supply a fixed completion time.

The toolbar’s loaded-window message describes an iframe event. It does not confirm that a demo download completed, that an arena joined or that a character entered a game. Use the visible project screen to decide what comes next.

Use the next action for your selected player

  • QuakeWorld: enter a name and press Play in q1. A continuing connection message depends on the arena service; it is a different stage from selecting a demo.
  • Half-Life Uplink: select Uplink (45M), then Start Demo. When the game menu arrives, choose New game and a difficulty.
  • Diablo shareware: choose Play Shareware. After its first load, select Single Player and create a hero. Select MPQ starts a separate full-game import path.

Keep one selected version while you compare results. Loading a different demo in another tab is not a useful check of the original attempt.

Compare a stopped attempt with its original project

Use Open original below the player and choose the same version there. If the original tab progresses, continue that session there. If both stop at the same screen, note the exact stage and the project’s error rather than assuming the surrounding App is the cause.

The comparison can narrow the problem to an embedded context or to a shared project, device or network condition. It does not prove one specific cause. The blank-window guide gives a separate route when no project interface appears.

Restart only when you are ready to leave this attempt

Restart replaces the embedded player. Close removes it and restores the ready screen. Both can interrupt an active session; neither exports progress. If the project has reached a game scene, use its own save options before deciding to restart.

When the scene responds but movement does not, switch to keyboard and mouse help. If a compatible file is requested, follow the version’s import route. Those symptoms need different next actions from an unfinished download.

Questions about this session

How long should a first load take?

There is no fixed promise. Watch the selected project’s progress; connection, assets and device conditions differ.

Will restarting finish a download faster?

Restart creates another player attempt and may repeat work. Let a changing progress indicator finish first.

Why do movement keys do nothing on a game menu?

Complete the menu and version choices first. A menu can be running before the playable scene exists.

A NEXT STEP FOR EACH SYMPTOM

Get back to your session.

Full launch guide →

Choose a player and try the next step.