Fix toast notifications not displaying immediately on login/register screens

[Copilot]

Problem

Toast notifications were not appearing immediately when validation failed on login and register screens. Users would click the login button with empty password, but the toast would only appear after navigating to another screen (like clicking the register button).

Root Cause

The issue was caused by timing problems in the Minecraft rendering pipeline. Toast calls made directly in button event handlers (UtilToast.toast()) were added to Minecraft's toast manager but not processed until the next screen refresh cycle.

Solution

Wrapped all immediate toast calls in ctx.get().enqueueWork{} blocks to ensure they execute in the proper render cycle timing. This follows the same pattern already used successfully in PacketResponse.handle() for network-triggered toasts.

Changes Made

Before:

if (this.passwordEditBox.value.isEmpty()) {
    UtilToast.toast(UtilComponent.getTranslatableComponent(Lang.Auth.EMPTY))
    return@Button
}

After:

if (this.passwordEditBox.value.isEmpty()) {
    this.ctx.get().enqueueWork {
        UtilToast.toast(UtilComponent.getTranslatableComponent(Lang.Auth.EMPTY))
    }
    return@Button
}

Applied to:

• Login screen empty password validation (both forge-1.19.2 and forge-1.20.1)
• Register screen empty password validation (both versions)
• Register screen password mismatch validation (both versions)

Expected Behavior

After this fix:

• Empty password toasts display immediately when clicking login with no password
• Password mismatch toasts display immediately when passwords don't match on register
• No more delayed toast display requiring screen navigation to see validation messages

Testing

The fix follows the established pattern used by PacketResponse.handle() which successfully displays toasts for network responses, ensuring consistency with existing working code.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• mirrors.cloud.tencent.com
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java -Xmx64m -Xms64m -Dorg.gradle.appname=gradlew -classpath /home/REDACTED/work/AsyncAuth/AsyncAuth/gradle/wrapper/gradle-wrapper.jar org.gradle.wrapper.GradleWrapperMain projects (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.