Test the exact published connection route
Delete the saved server record from the test client and add the address according to your connection page. Repeat in Java and, if supported, in Bedrock with a separate port field. Record the first screen and required action after logging in.
Take the registration command only from the installed system. A direct online-mode server may not have an additional /register. Paper properties describe server-side account verification, but do not come up with the login text for your plugins.
Write three short tips for one result
For the test route, choose one goal: enter Survival, find a safe place and place a bed. If the server provides a different first mode, replace the target with the appropriate short action. The name of the button and help command must match the real interface.
Show confirmation after the actual result: clicking the button does not mean a successful teleport or a completed round. The next window must not overlap the previous one before the player has read the answer.
| moment | Hint Contents |
|---|---|
| Before action | Open your navigator in the hotbar → Survival |
| After action | You have entered Survival. Find a place for the first night |
| Return to help | Exact existing command or Help button |
Test with failures
Ask the tester to complete the route without prompting from the administrator. For each dead end, record the screen, the action, and the expected next step.
- Close the greeting immediately and open the help again yourself.
- Enter the mode, click “Back” and repeat through another published entrance - NPC or portal.
- Try an action without the required right or money: get the reason for the refusal and the next step.
- Normally exit the game, then check the usual things.
- Log out of the server and log in again: do not repeat a completed registration or completed goal.
Correct any obstacle found at its source
If the command doesn't work, briefly enable lp verbose on, replay one try, and disable lp verbose off. Verbose LuckPerms helps to find the requested right; issuing the OP will hide the problem instead of checking.
Count separately successful entry, mode selection, first completed action and return on another day. To do this, limited game events and units are enough. Don't collect passwords or private chat for the sake of analyzing a button. After one correction, go through the route again with a new account and on a small screen.
Each branch must have a predictable return path. Make help available from every screen.
Under the OP, the initial restrictions are easy to miss. Reproduce the failure of a regular player.
