PaperMC / PaperMC/Paper

Audience can't return previous dialog after click open_url text in AsyncPlayerConnectionConfigureEvent

Open
#13,708 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs triage version: 1.21.11
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

Audience need to return to dialog that Audience was viewing, after click any open_url dialog's buttons.

Observed/Actual behavior

Audience just see frozen 'Joining world...' so they can't do anything after click button in open_url dialog.

Steps/models to reproduce
  1. Prepare dialog with open_url click event textcomponent.
  2. Show prepared dialog in AsyncPlayerConnectionConfigureEvent.
  3. Click the text with click event in dialog, so open_url dialog in this step.
  4. Click any button. it doesn't matter.
  5. finally, we can't see previous dialog. there's just frozen 'Joining world...'.
Plugin and Datapack List

not related

Paper version

Checking version, please wait...
This server is running Paper version 1.21.11-92-main@e7445e1 (2026-01-11T23:38:04Z) (Implementing API version 1.21.11-R0.1-SNAPSHOT)
You are 35 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 1.21.10-127-92ee2c2 (MC: 1.21.10)

Other

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the sequence in AsyncPlayerConnectionConfigureEvent: show a dialog, click an open_url text component, then press a button in the opened dialog. Trace the dialog transition and verify that the previously visible dialog is restored instead of leaving the audience at the frozen “Joining world...” screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.