Rewards and Player Data

AtlasLobby stores reward progress and player state in YAML. Rewards can grant commands and coins, while player data tracks lobby preferences, cosmetics, and resource-pack status.

Daily Rewards

Rewards are configured in rewards.yml:

enabled: true
claim-cooldown-hours: 24
streak-reset-hours: 48
coins:
  enabled: true
  base: 100          # coins granted on a claim
  per-streak: 25     # extra coins per streak day
  max: 1000          # cap
groups:
  default:
    permission: ""
    commands:
      - "give %player% emerald 3"

Setting	Meaning
`enabled`	Turns daily rewards on or off.
`claim-cooldown-hours`	Hours before the player can claim again.
`streak-reset-hours`	Hours before the streak resets.
`coins.enabled`	Enables coin rewards.
`coins.base`	Coins granted on a claim.
`coins.per-streak`	Extra coins per streak day.
`coins.max`	Maximum coin payout.
`groups`	Permission-based reward groups and command lists.

Each claim grants:

base + per-streak * (streak - 1)

The result is capped at max.

The amount is available to the claim message and title as %coins_earned%. See Coins Economy.

Players claim rewards through the rewards menu action:

actions:
  - "claim_daily_reward:"

Spam Protection

AtlasLobby uses a claim lock so a player cannot process multiple reward claims at once.

The in-memory claim timestamp is updated before reward commands run. That means fast menu clicks cannot repeatedly trigger rewards.

Menus also support click-cooldown-seconds.

Player Data File

Player data is stored here:

plugins/AtlasLobby/data/players.yml

Data includes:

Data	Notes
UUID	Player UUID.
Last known name	Most recent player name.
First join timestamp	When the player first joined.
Last join timestamp	Most recent join.
Visibility mode	Player visibility preference.
Last daily claim timestamp	Last reward claim time.
Daily streak	Current reward streak.
Coin balance	Built-in economy balance.
Equipped cosmetics	Stored per slot: `particle`, `hat`, and `gadget`.
Resource pack status	Latest pack status.
Sound and particle preferences	Player settings.
Favorite/recent server	Server selector state.
Unlocked cosmetics	Purchased or unlocked cosmetics.

Saving Notes

AtlasLobby currently saves player data as YAML.

Player data is saved automatically during normal server use, including reward claims and cosmetic changes. On shutdown, AtlasLobby performs a final save so the latest player state is written to disk.

Avoid editing data/players.yml while the server is running unless you know exactly what you are changing.