멀티플레이어 게임 개발에 대한 접근 방식 계획 - 정말 고품질 제품을 만들 때 고려해야 할 많은 기준이 포함되어 있기 때문에 전체 프로젝트의 추가 개발에서 가장 중요한 역할 중 하나를 수행합니다. 오늘의 선언문 튜토리얼에서는 모든 보안 및 안티칫 규칙을 준수하면서 매우 빠른 게임을 만들 수 있는 접근 방식의 예를 살펴보겠습니다.
그러므로 주요 기준을 정의해 보겠습니다.
먼저 Node.js에 서버를 설정해야 합니다. 서버는 모든 중요한 계산을 담당하고 업데이트된 데이터를 플레이어에게 전송합니다.
환경 설치
Node.js에서 서버를 생성하려면 필요한 종속성을 설치하세요.
mkdir multiplayer-game-server cd multiplayer-game-server npm init -y npm install socket.io
Socket.io를 사용하면 웹 소켓을 사용하여 클라이언트와 서버 간의 실시간 양방향 통신을 쉽게 구현할 수 있습니다.
기본 서버 구현
클라이언트 연결을 처리하고, 데이터를 검색하고, 중요한 상태를 계산하고, 모든 클라이언트 간에 동기화하는 간단한 서버를 만들어 보겠습니다.
// Create a simple socket IO server
const io = require('socket.io')(3000, {
cors: {
origin: '*'
}
});
// Simple example of game states
let gameState = {};
let playerSpeedConfig = {
maxX: 1,
maxY: 1,
maxZ: 1
};
// Work with new connection
io.on('connection', (socket) => {
console.log('Player connected:', socket.id);
// Initialize player state for socket ID
gameState[socket.id] = { x: 0, y: 0, z: 0 };
// work with simple player command for movement
socket.on('playerMove', (data) => {
const { id, dx, dy, dz } = parsePlayerMove(data);
// Check Maximal Values
if(dx > playerSpeedConfig.maxX) dx = playerSpeedConfig.maxX;
if(dy > playerSpeedConfig.maxY) dx = playerSpeedConfig.maxY;
if(dz > playerSpeedConfig.maxZ) dx = playerSpeedConfig.maxZ;
// update game state for current player
gameState[id].x += dx;
gameState[id].y += dy;
gameState[id].z += dz;
// Send new state for all clients
const updatedData = serializeGameState(gameState);
io.emit('gameStateUpdate', updatedData);
});
// Work with unsafe data
socket.on('dataupdate', (data) => {
const { id, unsafe } = parsePlayerUnsafe(data);
// update game state for current player
gameState[id].unsafeValue += unsafe;
// Send new state for all clients
const updatedData = serializeGameState(gameState);
io.emit('gameStateUpdate', updatedData);
});
// Work with player disconnection
socket.on('disconnect', () => {
console.log('Player disconnected:', socket.id);
delete gameState[socket.id];
});
});
// Simple Parse our binary data
function parsePlayerMove(buffer) {
const id = buffer.toString('utf8', 0, 16); // Player ID (16 bit)
const dx = buffer.readFloatLE(16); // Delta X
const dy = buffer.readFloatLE(20); // Delta Y
const dz = buffer.readFloatLE(24); // Delta Z
return { id, dx, dy, dz };
}
// Simple Parse of unsafe data
function parsePlayerUnsafe(buffer) {
const id = buffer.toString('utf8', 0, 16); // Player ID (16 bit)
const unsafe = buffer.readFloatLE(16); // Unsafe float
return { id, unsafe };
}
// Simple game state serialization for binary protocol
function serializeGameState(gameState) {
const buffers = [];
for (const [id, data] of Object.entries(gameState)) {
// Player ID
const idBuffer = Buffer.from(id, 'utf8');
// Position (critical) Buffer
const posBuffer = Buffer.alloc(12);
posBuffer.writeFloatLE(data.x, 0);
posBuffer.writeFloatLE(data.y, 4);
posBuffer.writeFloatLE(data.z, 8);
// Unsafe Data Buffer
const unsafeBuffer = Buffer.alloc(4);
unsafeBuffer.writeFloatLE(data.unsafeValue, 0);
// Join all buffers
buffers.push(Buffer.concat([idBuffer, posBuffer, unsafeBuffer]));
}
return Buffer.concat(buffers);
}
이 서버는 다음을 수행합니다.
핵심 사항:
이제 Unity에서 서버와 상호 작용할 클라이언트 부분을 만들어 보겠습니다.
Unity를 Socket.IO의 서버에 연결하려면 Unity용으로 설계된 라이브러리를 연결해야 합니다.
이 경우 특정 구현에 구속되지 않고(사실 모두 유사함) 추상적인 예를 사용합니다.
Using reactive fields for synchronization
We will use reactive fields to update player positions. This will allow us to update states without having to check the data in each frame via the Update() method. Reactive fields automatically update the visual representation of objects in the game when the state of the data changes.
To get a reactive properties functional you can use UniRx.
Client code on Unity
Let's create a script that will connect to the server, send data and receive updates via reactive fields.
using UnityEngine;
using SocketIOClient;
using UniRx;
using System;
using System.Text;
// Basic Game Client Implementation
public class GameClient : MonoBehaviour
{
// SocketIO Based Client
private SocketIO client;
// Our Player Reactive Position
public ReactiveProperty<Vector3> playerPosition = new ReactiveProperty<Vector3>(Vector3.zero);
// Client Initialization
private void Start()
{
// Connect to our server
client = new SocketIO("http://localhost:3000");
// Add Client Events
client.OnConnected += OnConnected; // On Connected
client.On("gameStateUpdate", OnGameStateUpdate); // On Game State Changed
// Connect to Socket Async
client.ConnectAsync();
// Subscribe to our player position changed
playerPosition.Subscribe(newPosition => {
// Here you can interpolate your position instead
// to get smooth movement at large ping
transform.position = newPosition;
});
// Add Movement Commands
Observable.EveryUpdate().Where(_ => Input.GetKey(KeyCode.W)).Subscribe(_ => ProcessInput(true));
Observable.EveryUpdate().Where(_ => Input.GetKey(KeyCode.S)).Subscribe(_ => ProcessInput(false));
}
// On Player Connected
private async void OnConnected(object sender, EventArgs e)
{
Debug.Log("Connected to server!");
}
// On Game State Update
private void OnGameStateUpdate(SocketIOResponse response)
{
// Get our binary data
byte[] data = response.GetValue<byte[]>();
// Work with binary data
int offset = 0;
while (offset < data.Length)
{
// Get Player ID
string playerId = Encoding.UTF8.GetString(data, offset, 16);
offset += 16;
// Get Player Position
float x = BitConverter.ToSingle(data, offset);
float y = BitConverter.ToSingle(data, offset + 4);
float z = BitConverter.ToSingle(data, offset + 8);
offset += 12;
// Get Player unsafe variable
float unsafeVariable = BitConverter.ToSingle(data, offset);
// Check if it's our player position
if (playerId == client.Id)
playerPosition.Value = new Vector3(x, y, z);
else
UpdateOtherPlayerPosition(playerId, new Vector3(x, y, z), unsafeVariable);
}
}
// Process player input
private void ProcessInput(bool isForward){
if (isForward)
SendMoveData(new Vector3(0, 0, 1)); // Move Forward
else
SendMoveData(new Vector3(0, 0, -1)); // Move Backward
}
// Send Movement Data
private async void SendMoveData(Vector3 delta)
{
byte[] data = new byte[28];
Encoding.UTF8.GetBytes(client.Id).CopyTo(data, 0);
BitConverter.GetBytes(delta.x).CopyTo(data, 16);
BitConverter.GetBytes(delta.y).CopyTo(data, 20);
BitConverter.GetBytes(delta.z).CopyTo(data, 24);
await client.EmitAsync("playerMove", data);
}
// Send any unsafe data
private async void SendUnsafeData(float unsafeData){
byte[] data = new byte[20];
Encoding.UTF8.GetBytes(client.Id).CopyTo(data, 0);
BitConverter.GetBytes(unsafeData).CopyTo(data, 16);
await client.EmitAsync("dataUpdate", data);
}
// Update Other players position
private void UpdateOtherPlayerPosition(string playerId, Vector3 newPosition, float unsafeVariable)
{
// Here we can update other player positions and variables
}
// On Client Object Destroyed
private void OnDestroy()
{
client.DisconnectAsync();
}
}
To ensure smooth gameplay and minimize latency during synchronization, it is recommended:
In order to simplify your work with a binary protocol - create a basic principle of data processing, as well as schemes of interaction with it.
For our example, we can take a basic protocol where:
1) The first 4 bits are the maxa of the request the user is making (e.g. 0 - move player, 1 - shoot, etc.);
2) The next 16 bits are the ID of our client.
3) Next we fill in the data that is passed through the loop (some Net Variables), where we store the ID of the variable, the size of the offset in bytes to the beginning of the next variable, the type of the variable and its value.
For the convenience of version and data control - we can create a client-server communication schema in a convenient format (JSON / XML) and download it once from the server to further parse our binary data according to this schema for the required version of our API.
It doesn't make sense to process every data on the server, some of them are easier to modify on the client side and just send to other clients.
To make you a bit more secure in this scheme - you can use client-side anti-chit system to prevent memory hacks - for example, my GameShield - a free open source solution.
We took a simple example of developing a multiplayer game on Unity with a Node.js server, where all critical data is handled on the server to ensure the integrity of the game. Using a binary protocol to transfer data helps optimize traffic, and reactive programming in Unity makes it easy to synchronize client state without having to use the Update() method.
This approach not only improves game performance, but also increases protection against cheating by ensuring that all key calculations are performed on the server rather than the client.
And of course, as always thank you for reading the article. If you still have any questions or need help in organizing your architecture for multiplayer project - I invite you to my Discord
You can also help me out a lot in my plight and support the release of new articles and free for everyone libraries and assets for developers:
My Discord | My Blog | My GitHub
BTC: bc1qef2d34r4xkrm48zknjdjt7c0ea92ay9m2a7q55
ETH: 0x1112a2Ef850711DF4dE9c432376F255f416ef5d0
USDT (TRC20): TRf7SLi6trtNAU6K3pvVY61bzQkhxDcRLC
위 내용은 예제를 통해 Unity 및 NodeJS 게임에서 안전하고 빠른 멀티플레이어 만들기의 상세 내용입니다. 자세한 내용은 PHP 중국어 웹사이트의 기타 관련 기사를 참조하세요!
![[웹 프런트엔드] Node.js 빠른 시작](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
