The server/client for community servers API.
Go to file
Julgers 31ad895542
Fix fuckup in readme
2023-08-14 14:57:20 +02:00
BattleBitAPI asfdsadsggsdfgsdfgsfdgfdsgdfsdg 2023-08-14 14:51:25 +03:00
.dockerignore Add docker support 2023-08-11 13:56:04 +02:00
.gitignore Add docker support 2023-08-11 13:56:04 +02:00
CommunityServerAPI.csproj First commit. 2023-03-03 15:15:17 +03:00
CommunityServerAPI.sln First commit. 2023-03-03 15:15:17 +03:00
Dockerfile Add docker support 2023-08-11 13:56:04 +02:00
LICENSE Initial commit 2023-03-03 15:09:34 +03:00
Program.cs asfdsadsggsdfgsdfgsfdgfdsgdfsdg 2023-08-14 14:51:25 +03:00
README-zhCN.md Update README-zhCN.md 2023-08-14 14:16:49 +02:00
README.md Fix fuckup in readme 2023-08-14 14:57:20 +02:00
README_koKR.md README file modify (#23) 2023-08-14 14:11:41 +02:00
docker-compose.yml Fix mistake in docker-compose.yml 2023-08-11 23:38:52 +02:00

README.md

BattleBit Remastered Community Server API

License: MIT

Language English | 中文 | 한국어

This repository provides an API that can be used to handle events on your community server(s) and manipulate them.

Getting started

Prerequisites

  • Your own community server within BattleBit Remastered with progression disabled and access to its launch options.
  • The ability to write and compile .NET 6.0 C# code.
  • (for production) A place to host this API on.

Writing

Documentation and examples can be found on the wiki (WIP).

The way to use this API is to make an instance of ServerListener (and start it) on which you pass the types of your own subclasses of Player & GameServer. In those subclasses, you can make your own overrides to the already existing methods in Player and GameServer. You can also add your own methods and fields/properties.

The easiest way to get started with all of this, is to use Program.cs and add your overrides etc. into MyPlayer & MyGameServer.

Building

This project can either be built by using dotnet build on the command-line or by using the run / build options inside your preferred IDE.

Connecting to the gameserver(s)

After writing and compiling this project. You will want to host it somewhere. This could be on the same server that the gameservers run on, or somewhere completely different. We do recommend to keep the latency to the gameserver minimal for smoother and faster communication. The same ServerListener can be used for multiple gameservers at the same time. You can specify the API server (address & port) in the launch options of the gameserver.

The gameserver connects to the API with the launch argument "-apiendpoint=<IP>:<port>", where <port> is the port that the listener listens on and the <IP> is the IP of the API server.