Reward Requirements

Before a player can claim a reward, they must pass through a series of toggleable checkers. Here is a list of these checkers:

Checkers for Rewards

1. Permission Checker

   • Checks if the claimer has stated permission.

   • Multiple permission can be used, see Reward Variants

   • Permission can be set per reward in reward's .yml using permission: "<text>" (set to "" for no required permission)

2. Enough Inventory Slots Checker

   • Cancels the claiming if the player doesn't have enough free inventory slots.

   • Can be specified per reward in it's .yml file by required-slots: <number> property.

3. Discord Account Synchronization Checker

   • Verifies if the player has synchronized their Discord account.

   • To specify that a reward requires synchronization, add require-discord-sync: true to the reward’s .yml file.

4. Claiming in Disabled World(s) Checker

   • Prevents claiming of rewards if the player is located within a designated disabled world.

   • Worlds can be specified per-reward by listing them in the disabled-worlds section of the reward's .yml file.

5. Enough Play-Time Checker

   • Determines if the reward can be claimed based on the total time the player has spent on the server.

   • This can be configured in the config.yml file: first-time-join-required-play-time: <number> (set to 0 to disable this checker)

6. Session Play-Time Checker

   • Checks if the player has accrued the required amount of session time to claim a reward.

   • This can be configured in the config.yml file: session-required-play-time: <number> (set to 0 to disable this checker)

Checkers for Affiliates

1. Referral Creation Required Time Checker

   • Enables players to create their own referral after they have accumulated sufficient play-time.

   • Configuration can be set in referrals.yml using referral-create-required-play-time: <number> (set to 0 to disable this checker)

2. Maximum Play-Time to Apply Referral Checker

   • Disallows the activation of player referrals if the player has reached the maximum play-time.

   • This limit can be configured in referrals.yml using maximum-playtime-for-referred-player: <number> (set to 0 to disable this checker)