2
0
Эх сурвалжийг харах

Update high_level_multiplayer.rst

I think `WebSocket` implementation of `MultiplayerPeer` should be `WebSocketMultiplayerPeer`, instead of `WebSocketPeer`.
Water Zheng 2 долоо хоног өмнө
parent
commit
27758f8bdc

+ 1 - 1
tutorials/networking/high_level_multiplayer.rst

@@ -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
 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>`),
 provides an implementation based on ENet (:ref:`ENetMultiplayerPeer <class_ENetMultiplayerPeer>`),
 one based on WebRTC (:ref:`WebRTCMultiplayerPeer <class_WebRTCMultiplayerPeer>`), and one based on WebSocket
 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.
 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.
 For most common cases, using this object directly is discouraged, as Godot provides even higher level networking facilities.