Arena Restore system:

- Sometimes the System just place more blocks than the allowed value in blocks per second due the Iterator Delay and to prevent ConcurrentModificationException, this can reduce the value in 5-8 seconds.
- You can change the Iterator-Delay and Blocks-Per-Iterator values in config to have something faster.
- Yes, the restore system replace ALL blocks to prevent fails.
- If your restore system is low, use some Math to check if everything is ok:

First example (Big arena - 14k):
> I have 14k of blocks in an arena, with 5 Iterator delay and 50 blocks per iterator.
> 4 Iterators = 20 ticks (5 Iterator dealy * 4 Iterators = 20 ticks = 1 second)
> If 4 iterators = 1 second, I'm getting 200 blocks placed per second (4 iterators * 50 blocks)
> If I'm getting 200 blocks placed per second and my arena has 14.000 blocks, the calculated delay to reset the arena is 70 seconds. (14.000/200)

Second example (Normal arena - 3k):
> I have 3k of blocks in an arena, with 5 Iterator delay and 50 blocks per iterator.
> 4 Iterators = 20 ticks (5 Iterator dealy * 4 Iterators = 20 ticks = 1 second)
> If 4 iterators = 1 second, I'm getting 200 blocks placed per second (4 iterators * 50 blocks)
> If I'm getting 200 blocks placed per second and my arena has 3.0000 blocks, the calculated delay to reset the arena is 15 seconds. (3.000/200)

After this, if you're getting more delay than the calculated, check your server TPS or enable the Spigot Timing Test (/timings on) during the arena restore.
If your TPS is out of the default, reduce the values in config and teste again.

Sound system:
- To set a sound, use {SOUND_NAME}:{PITCH}

Switch database:
- To send the data from YAML to SQLITE or MYSQL use /sp switch MySQL or /sp switch SQLITE. [(Read more here)]

API:
- To access the new SPAPI use "API api Splegg.getAPI();" or just pick the method "Splegg.getAPI().yourmethod".

Config:
- To made in-game changes use /sp config set <path> <value> --> /sp config set Advanced.Restore-Log false
Shop system:
- buyPermission: The player needs to have this permission to buy an item (permission).
- permission: The item (permission) that the player with the buyPermission will purchase.
- So it's confuse but easy, if you want to add something to VIP Only you can add the buyPermission for the VIP group and players without this permission can't buy the permission to use item.

Examples:
I am a VIP member ->
The permission to buy the diamond shovel is splegg.buy.shovel.diamond. I'll buy because I have the buyPermission and I'll get the permission to use when I want.

I am normal member ->
I don't have the splegg.buy.shovel.diamond permission so I can't buy the item.

As you can see we are using permissions system instanceof saving everything in the Database, works with the same way and don't you can modify what you want.

Trails & Effects:
- The number is the ID and will be saved in Database.
- name: The display name in menu.
- buyPermission: The player needs to have this permission to buy an trail/effect.
- permission: The trail/effect that the player with the buyPermission will purchase.
- particles: The particle type, the list is on Main page. CLICK HERE TO GO
- menuItem: The display item in menu.
- lore: The item lore in menu.
- buyCommands: Commands to execute when player buy the trail/effect.
- price: The price
- slot: Slot in menu
- rotateParticles: For Effects Only, special/rotative particles around the player or normal particles.
- helmet: (Full armor set will be added soon) If player will get some hat with the effect.