Skip to main content

A stuck start restarts itself

The startup freeze, where Roblox stops on the loading screen on a signed-in profile, is not fixed yet, but Cordial now recognises it from Roblox’s own log within a few seconds and restarts Roblox, up to twice. You see “Roblox got stuck starting. Restarting it (2 of 3).” If it still freezes, Cordial says so instead of leaving the loading screen up. Set CORDIAL_NO_FREEZE_RESTART=1 to turn this off. This was tested with a recorded freeze, not yet on a live one; what is known about the cause is on #92.

Enter in a text box

0.24.0 stopped chat boxes from keeping their text by making Enter do nothing in multi-line boxes. That decided for Roblox. Now Enter behaves as on a phone: a multi-line box gets the newline, and a single-line box tells Roblox that Enter was pressed. Roblox then decides whether the box sends, clears, keeps its text or moves on. On the sign-in page, Enter in the username box now moves to the password box. CORDIAL_EDITOR_GTK_ENTER from 0.24.0 is gone.

Reporting dead movement keys

If W, A, S and D stop working after joining a game (#29), start Cordial with CORDIAL_TRACE_KEYS=1 (Flatpak: flatpak run --env=CORDIAL_TRACE_KEYS=1 io.github.luohoa97.Cordial), press W while stuck, and paste the [cordial] key lines. It prints every key, passwords included, so trim it to the W lines.

What is still broken

The startup freeze itself (#92): restarting hides it, it does not prevent it. Movement keys sometimes stop working after joining a game (#29). Respawning brings them back. A touchscreen can crash the client (#36). Two-step verification sign-in can crash the Flatpak (#90). Use Quick Log In. The rest of the list in the 0.24.0 notes still applies.