[Bug] openrct2-cli `--verbose` flag prevents master server registration -> clients can't connect
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 16.2k
- Forks
- 1.9k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 80
Description
Operating System
[Linux (x86-64)] debian:bullseye-slim
OpenRCT2 build
OpenRCT2, v0.3.5.1 (1085a30 on develop) provided by GitHub
Describe the issue
The --verbose flag seems to prevent a dedicated server from registering, or even attempting to register, with the master server. It also prevents clients from connecting at all.
May be related to #16401.
Granted, this has only been tested on a non-typical setup/build (see OS and OpenRCT2 build).
Area(s) with issue?
This bug is specific to multiplayer
Steps to reproduce
- Run
./OpenRCT2/openrct2-cli host Data/save/save.sv6 --port 25579 --user-data-path /home/container/Data/ --verboseon non-interactive Docker container. - "Registering server on master server" almost never appears (I've only seen it appear once), and "Server successfully registered on master server" never appears. However, "Listening for clients on *:25579" does appear everytime.
- Try connecting with a client manually (mine is Windows x64) with:
openrct2.com join <IP address> --port 25579. Client will try to authenticate for a second, and then disconnect (very similar behavior to issue #16396; maybe related?).
Attachments
No response
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
Start with the reproduced openrct2-cli host command and compare registration and client-connection behavior with and without --verbose. Read the related issues #16401 and #16396, then trace the master-server registration and client authentication paths. Done means a verbose dedicated server registers successfully and accepts client connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100