.env.go.local -

Polar is a SaaS cheat prevention software aimed at limiting cheaters from gaining an unfair advantage on your Minecraft server.

Documentation Discord Server
Console

Our Strategy

Setting New Standards in Cheat Detection

Our innovative approach focuses on prevention and mitigation, creating a more effective way to combat cheating on Minecraft servers

.env.go.local -

To use a pattern like .env.go.local effectively, follow these best practices.

// Step 2: Initialize configuration cfg := mustLoadConfig()

(committed to version control):

Below is a useful content example for a .env.go.local file for a Go application. This example assumes your Go application interacts with a database, uses an external API, and requires a specific log level for local development:

If you’ve worked on Go applications that interact with databases, APIs, or external services, you know the pain of managing configuration across different environments (local, staging, production). Hardcoding values is brittle, and using a single .env file often leads to accidental commits of secrets or messy overrides. .env.go.local

to load these variables into the system environment at runtime. The "essay" of this file is written in the code that loads it: // Example logic for loading local overrides err := godotenv.Load( ".env.go.local" ); err != nil { // Fallback to standard .env if the local one doesn't exist godotenv.Load( Use code with caution. Copied to clipboard The Security Narrative The "story" of .env.go.local is ultimately one of caution. By appending and ensuring it is listed in .gitignore

: The most critical suffix. It signifies that this file is machine-specific and should be committed to version control (Git). Why It Matters In Go development, the .env.go.local To use a pattern like

Because .env.go.local is ignored by Git, fresh clones of your repository will lack the variables needed to compile or run the application. To solve this, create a tracked boilerplate file named .env.go.local.template (or .env.example ). This file defines the required keys but leaves the sensitive values blank:

What are mitigations really?

Compared to traditional punishments, cheating players may find it harder to notice mitigations affecting them, increasing the time it takes a cheater to return with a fresh account. Mitigations include, but are not limited to, movement, reach and damage restrictions.

The SaaS Idea

Most checks in Polar are performed by Polar cloud. By moving the load from the customer's server to our cloud, we can ensure stable operations on the server instance.

Polar Cloud

Powered by Advanced Cloud Technology

Our distributed cloud infrastructure enables powerful detection capabilities while maintaining optimal server performance

What is cloud?

Server instances running Polar are connected to the Polar cloud system. Polar sends relevant player packets to the cloud for inspection.

Why cloud?

Detections that do not necessarily require real-time action by Polar are ran in the cloud. This helps reduce CPU and memory load on the server instance.

Why is cloud reliable?

Cloud checks offer higher integrity and stability as they go through an extended processing period to accurately detect suspicious client behaviour.

What about delays?

Since cloud checks do not require real-time game intervention, the detection delay is not interrupting the anticheat operations.

Cloud will only apply mitigations until the anticheat is certain a player is cheating, at which point a punishment is applied.

To use a pattern like .env.go.local effectively, follow these best practices.

// Step 2: Initialize configuration cfg := mustLoadConfig()

(committed to version control):

Below is a useful content example for a .env.go.local file for a Go application. This example assumes your Go application interacts with a database, uses an external API, and requires a specific log level for local development:

If you’ve worked on Go applications that interact with databases, APIs, or external services, you know the pain of managing configuration across different environments (local, staging, production). Hardcoding values is brittle, and using a single .env file often leads to accidental commits of secrets or messy overrides.

to load these variables into the system environment at runtime. The "essay" of this file is written in the code that loads it: // Example logic for loading local overrides err := godotenv.Load( ".env.go.local" ); err != nil { // Fallback to standard .env if the local one doesn't exist godotenv.Load( Use code with caution. Copied to clipboard The Security Narrative The "story" of .env.go.local is ultimately one of caution. By appending and ensuring it is listed in .gitignore

: The most critical suffix. It signifies that this file is machine-specific and should be committed to version control (Git). Why It Matters In Go development, the .env.go.local

Because .env.go.local is ignored by Git, fresh clones of your repository will lack the variables needed to compile or run the application. To solve this, create a tracked boilerplate file named .env.go.local.template (or .env.example ). This file defines the required keys but leaves the sensitive values blank:

Pricing

Choose Your Plan

Select the perfect plan for your server and unlock the full potential of Polar

Small server

Perfect for small servers with under 75 players online

€15 /month (billed quarterly)
  • Up to 75 total players online
  • Up to 5 server instances
  • Up to 3 unique hardware IDs
  • ALL checks included
Subscribe

Medium server

Great for established servers

€29 /month
  • Up to 300 total players online
  • Up to 25 server instances
  • Up to 5 unique hardware IDs
  • ALL checks included
Subscribe

Large server

Great for large servers and minigame networks

€59 /month
  • Up to 600 total players online
  • Unlimited server instances
  • Up to 15 unique hardware IDs
  • ALL checks included
Subscribe

Enterprise Custom Solution

Tailored solutions for large networks with custom requirements

  • Unlimited players online
  • Unlimited server instances
  • Unlimited unique hardware IDs
  • Dedicated support
  • ALL checks included
Contact Sales

Detailed plan descriptions can be found in our docs.