Tags
Creators
Details
0.3.1-Beta
Compatibility
Changes
AtlasLobby 0.3.1-Beta
The first Beta: a top-to-bottom overhaul that makes AtlasLobby feel premium — a real cosmetic system, a coins economy, a flicker-free animated scoreboard, and gradient text throughout. Still 100% free, no paywalls.
✨ New: Cosmetic system
- Three cosmetic types — particles, hats, and gadgets (right-click toys).
- Categories + rarity tiers (Common → Mythic) with per-rarity colours and glow.
- Auto-generated, paginated cosmetics GUI with category tabs — no more hand-placing items.
- 7 new particle animations (atom, nova, hurricane, heartbeat, star, beam, shield) and many new cosmetics.
- Equip one particle + one hat + one gadget at the same time.
🪙 New: Coins economy
- Earn coins from daily rewards, spend them to unlock cosmetics.
- Works standalone, or sync with Vault (
economy.coins.use-vault). /coinsfor players;/al coins give|take|set <player|all> <amount>for admins.
🎨 New: Premium presentation
- Gradient (
<gradient:#a:#b>) and rainbow text anywhere text is accepted. - Custom player-head icons (owner / URL / base64) in menus and hats.
- Flicker-free, animated scoreboard (team-backed, in-place updates).
- Fully re-themed menus, messages, and cosmetics in the "Atlas aqua" style.
🛠️ Improvements & fixes
- Daily rewards now grant coins (base + per-streak bonus).
- Fixed held-item flicker caused by the inventory sanitizer.
- Added
/setlobby(alias of/setspawn) and/al cosmetic equip|unequip. - New placeholders:
%coins%,%equipped_hat%,%equipped_gadget%,%cosmetics_unlocked%, and more.
⚠️ Upgrading from 0.2.x (clean break)
Configs were restructured. Back up your plugins/AtlasLobby/ folder, then delete
cosmetics.yml and menus.yml so they regenerate. Player data carries over automatically.
Requires: Paper/Spigot 1.21, Java 21.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:NqnrjrSA:9QCueUKV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NqnrjrSA:9QCueUKV"
}

