godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2025-12-31 17:49:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update high_level_multiplayer.rst

Browse Source 
I think `WebSocket` implementation of `MultiplayerPeer` should be `WebSocketMultiplayerPeer`, instead of `WebSocketPeer`.
This commit is contained in:
Water Zheng
2025-10-02 12:09:00 +09:00
committed by GitHub
parent bc88ade318
commit 27758f8bdc
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
tutorials/networking/high_level_multiplayer.rst
View File

@@ -60,7 +60,7 @@ This object extends from :ref:`PacketPeer <class_PacketPeer>`, so it inherits al
This class interface can abstract most types of network layers, topologies and libraries. By default, Godot
provides an implementation based on ENet (:ref:`ENetMultiplayerPeer <class_ENetMultiplayerPeer>`),
one based on WebRTC (:ref:`WebRTCMultiplayerPeer <class_WebRTCMultiplayerPeer>`), and one based on WebSocket
(:ref:`WebSocketPeer <class_WebSocketPeer>`), but this could be used to implement
(:ref:`WebSocketMultiplayerPeer <class_WebSocketMultiplayerPeer>`), but this could be used to implement
mobile APIs (for ad hoc WiFi, Bluetooth) or custom device/console-specific networking APIs.
For most common cases, using this object directly is discouraged, as Godot provides even higher level networking facilities.