No description
  • CSS 62.9%
  • JavaScript 27.7%
  • Go 8.4%
  • HTML 0.6%
  • PowerShell 0.4%
Find a file
Jakob Wallner 1c4c545f73
All checks were successful
Build and Release Polyserver / Build and Release (push) Successful in 4m55s
full workflow
2026-05-21 13:15:35 +02:00
.forgejo/workflows full workflow 2026-05-21 13:15:35 +02:00
config change config for 0.6.0 2026-03-12 21:01:21 -04:00
game buunch of fixes for dashboard stats 2026-03-07 19:49:28 -05:00
signaling invite stuff 2026-03-04 17:20:39 -05:00
tracks Revert "Bind to 0.0.0.0" 2026-03-19 21:49:55 +01:00
web fix spikes :yay: 2026-03-07 23:29:25 -05:00
webrtc fixed for beta5 2026-03-01 20:30:57 -05:00
.gitignore Optimize workflow 2026-03-08 20:42:59 +01:00
amp_config.json [temp] AMP stuff 2026-03-28 02:32:41 +01:00
build-all-platforms.ps1 Optimize workflow 2026-03-08 20:42:59 +01:00
console.go Add console commands 2026-03-28 02:02:30 +01:00
CONSOLE.md Add console commands 2026-03-28 02:02:30 +01:00
embed.go Embed web files in the compiled binary 2026-03-27 20:19:25 +01:00
go.mod Do a lot of stuff and break a lot of stuff 2026-02-18 22:12:04 +01:00
go.sum Do a lot of stuff and break a lot of stuff 2026-02-18 22:12:04 +01:00
main.go Add console commands 2026-03-28 02:02:30 +01:00
polyserver.kvp [temp] AMP stuff 2026-03-28 02:32:41 +01:00
polyserverconfig.json [temp] AMP stuff 2026-03-28 02:32:41 +01:00
README.md Update readme 2026-03-27 20:25:33 +01:00
server.go Revert "Bind to 0.0.0.0" 2026-03-19 21:49:55 +01:00

Polyserver

About

Polyserver is a headless server for PolyTrack

Usage

Download

Grab the binary for your system from https://github.com/polytrackmods/polyserver-go/releases
If the right binary for your system is not there, you can also build the server yourself by cloning the repository and running go build .

Tracks

The server looks for tracks inside the tracks folder inside the working directory in the form of .track files. .track files are just raw text files containing a track code

You can grab the .track files for the official and community tracks from the releases page

In the end, the folder structure should look something like this:

|--- tracks
    |--- community
        |--- 4_seasons.track
        |--- 90_reset.track
        |--- anubis.track
        |--- arabica.track
        |--- ...
    |--- custom
        |--- test1.track
    |--- official
        |--- desert1.track
        |--- desert2.track
        |--- ...
|--- polyserver.exe

Running the Server

To run the server, simply run the binary you just downloaded

Launch options

port: the port the server management dashboard runs on. Default is 8080.
control-port: the port the control server runs on. Default is 9090.
address: The address the web frontend binds to. If you want the frontend to only be available to the host, either ignore this or set it to 127.0.0.1. If you want the frontend to bind to all addresses, set this to 0.0.0.0. Default is 127.0.0.1.