Sākums Izpētīt Palīdzība
Reģistrēties Pierakstīties
ease
/
godot-demo-projects
1
0
Atdalīts 0
Faili Problēmas 0 Izmaiņu pieprasījumi 0 Vikivietne
Koks: 722bd11689
Atzari Tagi
godot-demo-proj...
/
networking
/
webrtc_signaling
Fabio Alessandrelli f954d78903 Fix missing parameter in webrtc_signaling "connected" handler (#995) 9 mēneši atpakaļ
..
client db8ac0422d make websocket pool every time 1 gadu atpakaļ
demo f954d78903 Fix missing parameter in webrtc_signaling "connected" handler (#995) 9 mēneši atpakaļ
screenshots 7d64830cfe Ensure most demos have descriptions and screenshots 3 gadi atpakaļ
server ddf6d60ed4 Fix Web platform checks in WebRTC signaling demo (#1015) 9 mēneši atpakaļ
server_node 364e8cbfb8 Update WebRTC signaling demo to Godot beta4. 2 gadi atpakaļ
.gitignore 2a57c64c30 Add webrtc signaling example 5 gadi atpakaļ
README.md 364e8cbfb8 Update WebRTC signaling demo to Godot beta4. 2 gadi atpakaļ
project.godot 2a962929f3 Update demo files for Godot 4.2.1 (#1013) 9 mēneši atpakaļ

README.md

A WebSocket signaling server/client for WebRTC.

This demo is devided in 4 parts:

  • The server folder contains the signaling server implementation written in GDScript (so it can be run by a game server running Godot)
  • The server_node folder contains the signaling server implementation written in Node.js (if you don't plan to run a game server but only match-making).
  • The client part contains the client implementation in GDScript.
    • Itself divided into raw protocol and WebRTCMultiplayer handling.
  • The demo contains a small app that uses it.

NOTE: You must extract the latest version of the WebRTC GDNative plugin in the project folder to run from desktop.

Language: GDScript

Renderer: GLES 2

Check out this demo on the asset library: https://godotengine.org/asset-library/asset/537

Protocol

The protocol is JSON based, and uses messages in the form:

{
  "id": "number",
  "type": "number",
  "data": "string",
}

With type being the message type, id being a connected peer or 0, and data being the message specific data.

Messages are the following:

  • 0 = JOIN, must be sent by client immediately after connection to get a lobby assigned or join a known one (via the data field). This messages is also sent by server back to the client to notify the assigned lobby, or simply a successful join.
  • 1 = ID, sent by server to identify the client when it joins a room (the id field will contain the be assigned ID).
  • 2 = PEER_CONNECT, sent by server to notify new peers in the same lobby (the id field will contain the ID of the new peer).
  • 3 = PEER_DISCONNECT, sent by server to notify when a peer in the same lobby disconnects (the id field will contain the ID of the disconnected peer).
  • 4 = OFFER, sent by the client when creating a WebRTC offer then relayed back by the server to the destination peer.
  • 5 = ANSWER, sent by the client when creating a WebRTC answer then relayed back by the server to the destination peer.
  • 6 = CANDIDATE, sent by the client when generating new WebRTC candidates then relayed back by the server to the destination peer.
  • 7 = SEAL, sent by client to seal the lobby (only the client that created it is allowed to seal a lobby), and then back by the server to notify success. When a lobby is sealed, no new client will be able to join, and the lobby will be destroyed (and clients disconnected) after 10 seconds.

For relayed messages (i.e. for OFFER, ANSWER, and CANDIDATE), the client will set the id field as the destination peer, then the server will replace it with the id of the sending peer, and send it to the proper destination.

Screenshots

Screenshot