Add TaloMultiplayerPeer and multiplayer sample.

[Daylily-Zeleen]

Implemented through Talo Channels.

Need #72 .

Need test.

---

Run two instances of sample/multiplayer/multiplayer.tscn and connect them. Then continuously moving one of them, the synchronization will be broken after few seconds and push error:

E 0:00:16:0622   talo_socket.gd:75 @ send(): Condition "ready_state != STATE_OPEN" is true. Returning: FAILED
  <C++ 源文件>      modules/websocket/wsl_peer.cpp:702 @ _send()
  <栈追踪>          talo_socket.gd:75 @ send()
                 channels_api.gd:153 @ send_message()
                 talo_multiplayer_peer.gd:145 @ _send_packet_message()
                 talo_multiplayer_peer.gd:202 @ _put_packet_script()

@tudddorrr could you test this pr to find the reason about this error?

[tudddorrr]

Implemented through Talo Channels.

Need #72 .

Need test.

Run two instances of sample/multiplayer/multiplayer.tscn and connect them. Then continuously moving one of them, the synchronization will be broken after few seconds and push error:

E 0:00:16:0622   talo_socket.gd:75 @ send(): Condition "ready_state != STATE_OPEN" is true. Returning: FAILED
  <C++ 源文件>      modules/websocket/wsl_peer.cpp:702 @ _send()
  <栈追踪>          talo_socket.gd:75 @ send()
                 channels_api.gd:153 @ send_message()
                 talo_multiplayer_peer.gd:145 @ _send_packet_message()
                 talo_multiplayer_peer.gd:202 @ _put_packet_script()

@tudddorrr could you test this pr to find the reason about this error?

I'll try to look at this tomorrow or over the weekend :)

[tudddorrr]

@Daylily-Zeleen looks like you're encountering rate limit errors. each socket connection is granted 100 requests per second. to get this sample working you would need to check if rate limit errors are received (RATE_LIMIT_EXCEEDED). clients are warned 3 times before being disconnected if they exceed the rate limit.

[Daylily-Zeleen]

I'm not sure, I have test about this, connectd Talo.socket.message_received in TaloMultiplayerPeer.listen_channel(), and have not receive message with "v1.error", and I set the MultiplayerSynchornizer's "replication_interval" and "delta_interval" to 0.02, it should not exceed the limitation. Maybe due to my terrible network environment？

Your can adjust the MultiplayerSynchornizer's "replication_interval" and "delta_interval" in player.tscn to do some further test.

[tudddorrr]

You're right about the v1.error message not coming through - I need to investigate why this is. However, running this locally I can see in my docker logs that the clients are being disconnected because of the rate-limiting. I haven't worked with Godot multiplayer before so unfortunately I don't know where to adjust these settings, can you point me in the right direction?

[Daylily-Zeleen]

You're right about the v1.error message not coming through - I need to investigate why this is. However, running this locally I can see in my docker logs that the clients are being disconnected because of the rate-limiting. I haven't worked with Godot multiplayer before so unfortunately I don't know where to adjust these settings, can you point me in the right direction?

In my environment, set intervals to 0.02s (50 times per second) will broken the connection, too.

2025-03-03.14-30-03.mp4

[tudddorrr]

That was it - setting both values to 0.2 fixes it for me. These should be the default values ideally. If you try setting it to a higher value does that work? Looks like there's a few things that need to happen before the can be merged:

1. I need to work out why the v1.error for rate limiting isn't being received. Maybe there should be a signal fired when this happens (the logging might be overflowing and therefore not printing it).
2. The channels table needs to be updated to support BIGINTs for the messageCount column to preventing overflow errors

I still haven't had a chance to look at the full code but the sample is looking really good!

[Daylily-Zeleen]

I adjust intervals to 0.03 second, the connection will become broken, too.
Maybe the rate limitation check in back end should be optimized for different network environment.

[tudddorrr]

Yeah you're right - I think I can increase the rate limit so that it handles synchronisation more smoothly

[tudddorrr]

I've bumped the rate limit now, hopefully it should work better for you?

[Daylily-Zeleen]

I think my network environment can't use Talo. The latency is over 1 second and can be disconnected easily.

---

Maybe we need a new way to transfer message without rate limitation to implement MultiplayerPeer, at least it should support default intervals value of MultiplayerSynchronizer, It should be optimize parameters instead of limitations, and users can use multiply MultiplayerSynchronizer, the transfer rate will become 3 times, 4 times, or more...

[tudddorrr]

By "disconnected" do you mean the clients are getting out of sync quickly? I don't think your latency would be affecting how quickly you're being rate limited given that the request count that contributes to the limit are reset every 1 second.

I think you need some interpolation to handle the movement syncing, this is a pretty common pattern in games. With that in place you can increase the intervals.

[tudddorrr]

@Daylily-Zeleen in the latest dev branch, there's now a error_received signal on the Talo Socket, allowing you to easily check for rate limiting errors

[Daylily-Zeleen]

I collect messages into a queue and send them in _poll(), to ensure a peer can send only once per frame.
And I tune the sync intervals to 0.03 s, I still got error "Too Many Requests".

I think my network environment can't use Talo, it seems like the sending rate of messages is unstable, see these videos.

I will stop use Talo, but the TaloMultiplayerPeer in this pr is functionally complete, you can consider to merge.

[tudddorrr]

Thanks @Daylily-Zeleen. I'm still not totally convinced it's anything to do with your network environment. I really appreciate all your contributions and I'll look into picking this up at some point :)