Unity-Technologies / Unity-Technologies/multiplayer-community-contributions
WebSocketTransport Support?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 555
- Forks
- 197
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 1
Description
I have been trying to get the WebSocketTransport to work and have found a few issues so I wasn't sure if this was still being supported.
There are issues with the JSWebSocketClient.jslib as it throws Runtime not found errors - from what I have read the newer versions of unity no longer support Runtime.dyncall and you have to do something like Module['dyncall_v#']. I tried to make these changes and I no longer receive the errors but now I am getting Netcode warnings:
[Netcode] Received a packet too small to contain a BatchHeader. Ignoring it.
My server is getting the messages correctly now but messages going down to the client seem to give the above warning and the message isn't processed.
Anyone come across this or know who wrote this package originally?
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 JSWebSocketClient.jslib and the Unity version's support for Runtime.dyncall, then trace how server-to-client messages reach Netcode. Done means the client processes those messages without the "packet too small to contain a BatchHeader" warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, javascript, unity
- Domain
- game-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100