Warterfall can't get kick message from subserver.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 752
- Forks
- 307
- Avg merge
- 15h 48m
- Merged PRs (30d)
- 7
Description
Waterfall version: #445
Paper version: 1.16.5 #762
Issue: When a player is refused by the subserver for some reason
( for example, refused by Authme, for using an illegal username),
The subserver's console can display the right message.
but waterfall can't get the right reason for "lost connection". It just displays "could not connect to a default or fallback server".
This caused my players to be unable to know the specific reason why they were disconnected. Everyone thought that the server had not been started yet.
I have developed a plug-in to verify some user information, and use the disallow method ( I have also tried player.kick method) to deny players who do not meet the requirements to enter. Waterfall also cannot obtain this information. Only the console of the subserver can correctly output the reason for the disconnection.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the refusal with Waterfall #445, Paper 1.16.5 #762, and the described plugin or Authme scenario, comparing the subserver console with Waterfall's fallback message. Trace how a denied connection and its reason travel from the subserver to the proxy; done means players receive the specific refusal reason instead of only the fallback-server message.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100