Links
Tags
Creators
Details
Licensed CC-BY-ND-4.0
Published 3 months ago
Updated last week
All versions
2.1.3
Release
Fabric SMP 2.1.3last month 20
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Dedicated servers only
Changes
Research Results and Fixes for My Minecraft Modpack
I analyzed Spark with 10 players online and drew the following conclusions.
EasyAuth Configuration
| Setting | Value | Reason |
|---|---|---|
premium-auto-login |
false |
Set to false because my modpack is designed for pirate (offline) gameplay. |
floodgate-auto-login |
false |
I won't be adding Bedrock support anytime soon. |
vanish-until-auth |
true |
Hides players who haven't authenticated yet. |
session-timeout |
1800 |
Doesn't keep player sessions hidden for too long. |
Added Vanish Mod (by DrexHD)
- Required for EasyAuth to work properly with
vanish-until-auth=true. - Also useful for player moderation.
- Works at the packet level and shouldn't cause issues (prevents players from noticing they're being watched).
SkinRestorer — Switched from Automatic to Manual Mode
The Problem
The mod was frequently sending requests to Mojang / Ely.by / MineSkin:
- If the mod couldn't find a skin, the server received a
"not found"response. - This generated errors with stack traces.
- Stack traces clogged up logs, consumed memory, and pressured Java's garbage collector.
- Results were cached for only 60 seconds.
- After a minute, the mod repeated the same checks and spammed the logs all over again.
Consequences
- ⚠️ Increased RAM consumption
- ⚠️ Excessive log spam
- ⚠️ Potential player disconnections
The Fix
Now the mod no longer:
- ❌ Automatically checks skins on player login
- ❌ Makes unnecessary API requests
- ❌ Attempts to assign skins automatically
✅ If a player wants a skin, they must set it manually using the command:
/skin set
























