PwnAdventure3: Pwnie Island is a limited-release, first-person, true open-world MMORPG set on a beautiful island where anything could happen. That’s because this game is intentionally vulnerable to all kinds of silly hacks! Flying, endless cash, and more are all one client change or network proxy away. Are you ready for the mayhem?!
Official Site click here
Also Read Tallow – Transparent Tor for Windows
Install Server
Requirements
From the official README:
- At least 2GB of RAM, more RAM will allow more instances to be run on a single machine
- The Game Server does not need any graphics hardware and runs purely on console. It is known to run well on Amazon AWS and Digital Ocean VPS instances.
- The Game Server requires a lot of RAM to run, but uses fork and copy-on-write memory to allow many instances to run on a single host.
- For a server with 2GB of RAM, it is not recommended to run more than 5 instances, but a server with 8GB of RAM can typically run as many as the CPU can handle.
- It is recommended to use 2-3 instances per CPU core if you have sufficient RAM. You may be able to run 4-5 instances per core, but doing so may introduce slight lag.
- The files for the client and server are over 2GB as well, so several GB of free disk space are required.
There are several ways to build and deploy your own server.
Option 1 – Original
One option is to download and follow the instructions included in the README of the official files. The download can be found on the official website here.
Option 2 – Guide
@Beaujeant created an excellent, and easy to follow step-by-step guide. It was also the basis for building the docker image from Option 3. The guide can be found here.
Option 3 – Docker
This option is super easy, as long as docker
and docker-compose
are installed on a host. It makes it easy to run and tear down a server, without making changes to the actual host system.
First, gather all necessary files:
git clone https://github.com/LiveOverflow/PwnAdventure3.git
cd PwnAdventure3
wget http://pwnadventure.com/pwn3.tar.gz
tar -xvf pwn3.tar.gz
In order to run the server, docker
and docker-compose
have to be installed. Docker is moving fast, so it’s a good idea to follow the current official steps for installation (which could also include to remove an older system version of docker):
- Docker CE Ubuntu: https://docs.docker.com/install/linux/docker-ce/ubuntu/.
docker-compose
: https://docs.docker.com/compose/install/- make sure the current user is part of the
docker
group with:sudo usermod -a -G docker $USER
. restart or re-login and verify withid
that the user is part of the docker group.
Then simply build the image and launch the master and game server:
docker-compose build
docker-compose up
docker-compose up
can also run in detached/background mode with -d
.
Install Client PwnAdventure3
First download the client from the official website here
To get a client connected to the new server, the server.ini
for the client has to be modified. The server launched with docker expects that hostnames master.pwn3
and game.pwn3
are being used (These could theoretically be changed in the docker/setup files).
The server.ini
for the client has to look something like this:
MasterServer]
Hostname=master.pwn3
Port=3333
[GameServer]
Hostname=game.pwn3
Port=3000
Username=
Password=
Instances=
Make sure that the client can reach these hosts, for example by adding them to the /etc/hosts
file. In this example the server is running on 192.168.178.57
and the entry for them would be:
192.168.178.57 master.pwn3
192.168.178.57 game.pwn3
Warning: Using an IP as Hostname
in the server.ini
does not work! I spent 2 hours trying to figure out what was wrong.
To stop the server, simply type docker-compose down
.
Warning: The database file is not persistent – taking down the container resets everything. So backup first.
Credits
The true heroes, are the people who built the game <3
Pwn Adventure 3 is the brainchild of one Rusty Wagner. He’s responsible for the idea, the planning, and nearly all of the execution (programming, level design, quests, and so forth). Without him, there would be no game! Special thanks also goes to the Ghost in the Shellcode organizers for their support during development and testing.