openmultiplayer / openmultiplayer/launcher
In-game connect requests target the wrong server even though the launcher sends the correct IP and port
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 203
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
When using the in-game launcher overlay, selecting different unprotected servers can still connect the player to the same server.
This may also affect protected servers, but I only verified it with unprotected servers.
- Opened the in-game launcher with F9
- Selected two different unprotected servers
- Triggered connect from the overlay
- Verified that the launcher sent different
ip:porttargets
[in-game connect] message=connect:82.22.82.10:8008:Trifun_Djordjevic
[in-game connect] message=connect:91.211.244.140:7777:Trifun_Djordjevic
SA-MP 0.3.7-R4
Contributor guide
No contributing guide indexed for this repository
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 issue from the in-game launcher overlay opened with F9 using two unprotected servers on SA-MP 0.3.7-R4. Trace the overlay's connect handling after it sends the differing ip:port targets, and consider the issue done when each selected server receives the connection rather than the same server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100