BigKidsCore

BigKidsCore

Required core v1.0.8

The core that links your Rust server to BigKids.pro.

Overview

BigKidsCore is the hub every BigKids.pro plugin connects through. It authenticates your server with one secure token, talks to the BigKids.pro API, writes the chosen map into server.cfg and reports live server status (heartbeat). Install it once — feature plugins won’t run without it.

What this can and cannot do

BigKidsCore is the single place a BigKids.pro plugin talks to the website from. It holds your server token and nothing more, and it never takes orders from the site: your server asks, the site answers.

  • The token is sent over HTTPS only — over plain http the core refuses to send it at all — and it is never written to any log.
  • Every command is console-only. There is no in-game permission to grant, so no admin rank can use them.
  • There is no "run this on my server" endpoint. The website cannot make this plugin do anything.
  • Revoke or regenerate the server token in your dashboard at any time and the link is dead.

Features

  • One secure server token per server (stored hashed, shown once).
  • Shared HTTPS API client for all BigKids.pro plugins.
  • Writes server.levelurl / server.seed into server.cfg (no launcher edits).
  • Heartbeat: reports version, players and current map to your dashboard.
  • Works on Oxide/uMod and Carbon.

Installation

  1. Drop BigKidsCore.cs into oxide/plugins/ (or carbon/plugins/).
  2. In your dashboard → Servers, add a server and copy its token.
  3. Paste the token into oxide/config/BigKidsCore.json → "Server token".
  4. Run oxide.reload BigKidsCore (or c.reload BigKidsCore).

Commands

bigkidscore info Show core version, API version and connection status. Server console only.
bigkidscore heartbeat Report to the site right now. Server console only.

FAQ

Do I need BigKidsCore for other plugins?

Yes — DiscordMapVote and other BigKids.pro plugins go idle without it.

Is my token safe?

It’s stored only as a hash on our side and sent only over HTTPS. You can regenerate it anytime in the dashboard.

See all settings in the documentation.

We use analytics cookies to measure traffic and improve the website.