Netpacket interface: Fix SRAM and client reconnecting #15797
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Working together with a core developer who is in the process of implementing the new netpacket libretro interface we found some issues in the frontend which this PR addresses.
Both issues and fixes are exclusive to cores that call
RETRO_ENVIRONMENT_SET_NETPACKET_INTERFACE
, which until now have yet to be used by a publicly built and released libretro core.To recap, this new netpacket interface was added earlier this year in #15413. It allows a core to send and receive custom network packets, which can be used to implement a communication based multiplayer system instead of using the default state serialization based multiplayer. For example games with multiplayer that originally used wireless or ethernet based networking.
Related Pull Requests
#15413, #15434