Simple-Online-Multiplayer-Networking-Authoritative-Dedicated-Server

KO | EN

gitlite — search

#javascript #hacktoberfest #golang #go #machine-learning #linux #docker #nodejs #java #awesome #kubernetes #security #ios #open-source

Simple-Online-Multiplayer-Networking-Authoritative-Dedicated-Server

(★ 93)

No description available.

Simple-Online-Multiplayer-Networking-Authoritative-Dedicated-Server Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Simple Online Multiplayer Networking Authoritative Dedicated Server

A simple Godot multiplayer setup. Change the IP address to your cloud hosting public DNS, then compile and upload it as a Linux headless version with debug. The clients will connect automatically to the server. The server has full authority; players can only send inputs in order to prevent cheating. The server is the only one able to see the players’ inputs. The server selects a random map, then selects a random node in the spawn area group, obtains its dimensions, and sets a random position for the client spawned inside it.

## Tutorial to host the game online

* Create an Amazon Web Services account, then click **Sign in to console** then **Sign in using root user email**. Check **Root user**. A menu will ask you to secure your account check **Authenticator app**. At the top right, set the region to where you want to create the server (ideally East United States or West Europe).

* Create an EC2 instance by clicking on **Launch instance**. Create a key pair, name it for example **mykey**, and save it in a folder that you call **security**. Beside the checkbox **Allow SSH traffic from**, set the option to **My IP**. Click **Launch instance**.

* Go to your instance. Click the **Security** tab. Open the **Security groups** link. Click **Edit inbound rules**. Click **Add rule**, set the type to **Custom UDP**, and for the port range use the port of your game (in this demonstration project it is 8080). For the source, select **Anywhere IPv4**. Click **Save rules**.

* Copy the full Public DNS address of your instance to your game script for the constant `SERVER_IP`. Important: each time you stop the instance and then start it again the Public DNS will change, and you will need to rebuild your game.

* Export a Linux build of your game. In the **Resources** tab, set the **Export mode** to **Export as dedicated server**. Export it and check **Export With Debug** in order to obtain a `.sh` file. This is the file the cloud host will run. Use a simple name such as **server** and save your project in a folder called **server**.

Open the console. Go to the folder where you saved your key, for example (use right click to paste in the console):

```bash
cd "C:\Users\USERNAME\Desktop\security"
```

Then type this to connect to your instance:

```bash
ssh -i mykey.pem ec2-user@PUBLIC_DNS_HERE
```

If it asks for the fingerprint, type **yes**. Then type the previous command again to connect; you should see a bird displayed.

Before uploading your server file, make sure that you have pasted the Public DNS of your instance for the SERVER_IP constant in your game. If you want to upload a new version, delete the previous folder in your instance first using this command: `rm -rf ~/server`. To upload the files, you must not be connected to the instance. Open a new console and type this, using the path to your key and the path to your server folder.

```bash
scp -i "C:\Users\USERNAME\Desktop\security\mykey.pem" -r "C:\Users\USERNAME\Desktop\server" ec2-user@PUBLIC_DNS_HERE:~/server
```

Go back to the previous console where you are connected or use the previous ssh command to connect again:

```bash
ssh -i mykey.pem ec2-user@PUBLIC_DNS_HERE
```

You can type **ls** to see whether the folder has been uploaded correctly.

Set the correct permissions for the files:

```bash
chmod -R +x server
```

Launch the server with this command:

```bash
./server/server.sh
```

Press **Ctrl + C** to stop it.

**Make it persistent**

To make it persistent and make it always run even if you close the terminal or shut down your computer you must install tmux while being connected to your EC2 instance.

To install tmux:

```bash
sudo yum install tmux -y
```

Launch tmux and give the session a name:

```bash
tmux new -s godotserver
```

Do the same command as before to launch the server:

```bash
./server/server.sh
```

You can now close the console or shut down your computer, and your server will still be running.

To disconnect your server, go back to your tmux session if you had left it by typing this:

```bash
tmux attach -t godotserver
```

Then press **Ctrl + C** to disconnect the server.

Simple-Online-Multiplayer-Networking-Authoritative-Dedicated-Server

Simple-Online-Multiplayer-Networking-Authoritative-Dedicated-Server Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Simple-Online-Multiplayer-Networking-Authoritative-Dedicated-Server

Simple-Online-Multiplayer-Networking-Authoritative-Dedicated-Server Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README