One Render Too Early: Hunting Down the Page Flashes

For a while, several screens in Lourdin RPG showed the wrong page for a moment before the right one appeared. In August 2026 we tracked down why: each page drew itself before it knew what it was supposed to show, so it fell back to a default screen and then swapped. Now each page decides what to show before it draws, login sends you straight to the right place, and adventure narration stops when you leave the page. Here is what you saw, what caused it, and what changed.

What page flashes did Lourdin RPG players see?

If you played before August 2026, you probably met at least one of these:

• The arena that was not there. Starting a single-player waypoint battle flashed the full-screen Enter the Arena gate for a moment before the real fight loaded.
• The menu nobody asked for. Pressing Continue Quest in the Tavern showed the whole Adventures menu first, then swapped it for the waypoint you actually wanted.
• The detour through character select. Logging in walked you through the character select page, drawn twice and once as a spinner, on the way to a Tavern you were always going to land in.
• The narration that followed you around. Adventure narration kept playing after you left the page, on every page after that.

All of that is gone. The interesting part is that the first three were the same bug wearing different clothes.

Why did the arena screen flash before a waypoint battle?

A web page that is still waiting for its data shows something in the meantime. That is a good thing, because a slow page then shows you something instead of a blank rectangle. The trap is what that something is.

The combat page decides which screen to show based on what kind of battle it is loading, and it used to learn that only after six lookups, one after another. Until then it fell through to its default screen: the full-screen arena gate. So for however long those six lookups took, you stared at an arena gate you never asked for.

The fix is boring, which is the point. The link that opens a waypoint battle already says it is a waypoint battle, so the page now reads the link before it draws anything, and the first thing you see is the "Preparing battle..." screen. While we were in there, we also stopped making those six lookups wait in line. Most of them do not depend on each other, so they now run in two batches side by side, and the loading screen does not stay up as long.

Battles run on desktops and on tablets held sideways, so that is where this flash showed up. On a phone, or a smaller tablet held upright, the combat screen asks for a bigger screen instead.

Why did Continue Quest show the Adventures menu first?

Same bug, different page. The Adventures page starts out on its main menu, and the Continue Quest link from the Tavern only found your waypoint after several lookups, including a check for whether that waypoint has narration audio. For that whole time you saw the main menu, and then it swapped.

Now the page reads the link first and shows a short "Resuming your quest..." screen until your waypoint is ready. Two related fixes came along:

• The story comes first. The waypoint's story text and its Begin Battle button now appear before the narration check finishes. Neither one depends on narration, so neither one waits for it; the narration player joins as soon as it is found.
• No more endless spinner. If the link points to a quest you finished or abandoned on another device, you land on the Adventures menu with a note that the quest is no longer active, instead of a spinner that never stops.

If you are just starting out, how to play Lourdin RPG covers creating a hero and setting off on story-driven adventures.

What changed about logging in to Lourdin RPG?

Logging in was the worst of the bunch, because three problems stacked up. One sign-in used to look like this: the login form, a blank flash as the page reloaded, the character select page, a "Loading your heroes..." spinner replacing it, the character grid again, and finally the Tavern. That is a lot of screens for what feels like one action, and two of them were a page you never asked to see.

The destination was decided too late. Login always sent you to character select, and the game only moved you on to the Tavern once that page had loaded. Now the decision is made during the sign-in itself. If your account has an active character that still exists and belongs to you, you go straight to the Tavern. Otherwise you go to character select, which works for every account. If anything at all goes wrong while deciding, you also land on character select, because picking a page to show you should never be able to break a sign-in. Accounts that need a new password are sent to change it first.

Pages loaded twice. Each page is drawn once quickly by the server and then again when your live connection to the game starts. Character select and the Tavern did all of their loading both times, which is why a fully drawn character grid collapsed back into a spinner. Now they load once. Character select shows its spinner until your heroes are ready, and the Tavern shows an "Entering the tavern..." screen instead of briefly flashing "No Hero Selected" before your hero appears.

One reload is on purpose. The single full page reload right after you sign in looks like a bug, but it is how your new sign-in reaches your live connection to the game. It stays, with a note in the code explaining why, so nobody "fixes" it later.

How did the Tavern's locked tiles get easier to use?

Below level 5, the Stables and Pet Shop tiles in the Tavern are locked. They used to be plain boxes with a tooltip that only appeared when you hovered a mouse over them, so anyone using a keyboard, a screen reader or a touchscreen could never find out why they were locked. Since the lock lasts until level 5, every new player ran into it.

Now they are real buttons:

• You can reach them with the keyboard, and screen readers announce them as locked.
• The tile itself says how many more levels you need.
• Selecting one tells you, in a message, why it is locked and when it opens.

Two smaller fixes came out of the same pass. The Tavern tiles now show a clear outline when you move between them with the keyboard. And the Inventory tile could stack two badges on top of each other in its top corner, where the second one covered the icon; it now shows one badge at a time, with upgrades ahead of new items, and its tooltip mentions both. Once those pets unlock, the companions guide explains what they do.

Why did narration follow players to other pages?

This one is short and a little embarrassing. Adventure narration plays through one audio player shared by the whole site. The Adventures page stopped it whenever you used the page's own buttons, but it had no way to stop it when you left. Leave by the menu, the back button or any link, and the narration kept going, page after page. The combat page had the same gap with its victory narration.

Both pages now stop narration whenever you leave them, however you leave.

What did we learn?

For anyone who builds web pages, the whole lesson fits in one question: what does this page show before any of its data has arrived? Because that is what your players see first. Decide everything you can before the first wait, give the first draw something honest to show, and if you start something that plays across the whole site, make sure something turns it off.

For more on how combat looks and plays, see the May 2026 combat overhaul.