[BUG] Critical bug in Netplay chat; it's not working for clients, With the RetroArch Nightly version.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
With the RetroArch Nightly version, when using the NetPlay client to send a message to the host, the connection drops instantly.
https://github.com/user-attachments/assets/d0d47e66-571f-44b7-b6ff-40c3ee289186
Expected behavior
to be able to send the message to the host and prevent the netplay connection from dropping.
Steps to reproduce the bug
- First : Entering a netplay room as a client, I tested it with the fbneo_libretro core in the game Street Fighter 2.
- Second : I activated the chat to send a message to Host indicating that I am a client.
- When I enter the chat menu, the connection drops.
Version/Commit
1.22.2 Nightly
Bisect Results
1.21 1.21 - works correctly
Present in the nightly version
Yes, this is reproduced in the nightly build
Platform & operating system
Linux and Wildowns
Affected Cores
fbneo_libretro - I haven't tested it on other cores.
Environment information
I dont kinow
Relevant log output
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 by reproducing the failure in a NetPlay room with the client chat menu, using the fbneo_libretro core and the listed nightly version. Compare the behavior with version 1.21 and inspect the NetPlay chat and connection-handling entry points. Done means a client can send a message to the host without the NetPlay connection dropping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100