Configuration
Here you can view all the configuration and options for Player Auctions.
Last updated
Here you can view all the configuration and options for Player Auctions.
Last updated
Here are the latest plugin files, the plugin should automatically generate/update the files. If the plugin hasn't generated them make sure you've got the plugin requirements listed here. If you want to test your YAML syntax you can test it here.
Your plugin will automatically update when there is a needed configuration update, you cannot turn this off and is added to prevent errors on your plugin if you have any missing configuration options.
The plugin connects to my webserver, if this webserver is offline or your plugin cannot access it, then the configuration files may not be updated or downloaded.
Command actions are an easy way you to customize and execute all sorts of functions when an event is triggered, here are the latest command actions for Player Auctions.
Action | Description | Example |
---|---|---|
You can also add action tags that modify how the action is executed, you can use it in your command action like this [ACTION<TAG=value>]
.
Player Auctions supports certain requirements in the configuration, where certain requirements needs to be met for something to happen.
When requirements are created in the config, you will always have 3 default values that is available for every requirement. Here is a list and explaination of what they do.
Please note if multiple requirements are created under one section, it will evaluate the requirements in order, if a requirement is not met then it the outcome will not be successful. Multiple requirements can return a successful outcome.
Here is a list of all the avaliable requirement types:
This requirement checks if the player has the permission.
Here is an example on how to use the has permission requirement, below in the example the player needs the permission "requirement.test"
This requirement checks if the player has the money.
Here is an example on how to use the has money requirement, below in the example the player needs $100
This requirement checks if the input equals to the output.
Here is an example on how to use the string equals requirement, below in the example the output needs to equal "Notch"
Player Auctions supports color codes that you can use literally everywhere possible that is displayed to the player. If you don't know the color codes off by heart, you can view them here.
Player Auctions also supports the 1.16+ hex colors, with the current format {#HEX_CODE}
with the following example {#f5a142}
This shows a nice orange color. You can also use this here, to get your hex colors.
When using hex colors, you can also make cool looking gradients using 2 or more hex color codes. You can create gradients using these examples:
{#f5a142:#ffffff}
- This goes from a nice orange color then slowly fades into white.
{#f5a142:#ffffff:#0000ff}
- This goes from a nice orange color, then fades into white then slowly fades into blue.
You may want to use some external links to help you when configurating Player Auctions.
Here is a list of all of the valid materials that you can use to create items in Player Auctions for each version of Minecraft.
Here is a list of all the valid sound types that you can use to create cool sound effects in Player Auctions for each version of Minecraft.
Here is a list of all the valid item flags that you can use on your items in Player Auctions for each version of Minecraft.
Here is a list of all the valid item enchantments that you can use on your items in Player Auctions for each version of Minecraft.
Tag | Description | Example |
---|---|---|
Option | Description |
---|---|
player
Execute a command as the player.
[player] spawn
message
Send a message to the player.
[message] &aHello!
broadcast
Send a message to all online players.
[broadcast] &aHello World!
perm_broadcast
Broadcast a message to
players with the permission.
[perm_broadcast] message.view &aHello!
title
Send a title to the player.
[title] 20 60 20 &aHello\n&aWorld!
action_bar
Send an action bar message to the player.
[action_bar] &aHello!
loop_player
Loop through all online players and execute an action.
[loop_player] [player] spawn
server
Execute a command as the server.
[server] spawn %player%
command_event
Execute a unregistered command as the player.
[command_event] menu
chat_wait
Wait for the user to enter a value in chat.
[chat_wait] &aEnter a number:[message] &aYou said %value%
chat_wait
Wait for the user to enter a value in chat, but removes the color from the chat input with !color.
[chat_wait] &aEnter a number:[message] !color &aYou said %value%
add_money
Give a player money.
[add_money] 500
take_money
Take money from a player.
[take_money] 500
take_perm
Take a permission away from a player.
[take_perm] message.view
give_perm
Give a permission to a player
[give_perm] message.view
sound
Play a sound to the player.
[sound] AMBIENT_CAVE
[sound] AMBIENT_CAVE volume pitch
close
Close the inventory of the player.
[close]
delay
Execute the action later in ticks.
[broadcast<delay=20>] &aHello World
permission
Execute the action only if the player has permission.
[add_money<permission=pa.donator>] 1000
condition
Execute the action only if the value matches.
[add_money<condition=%player_name%=Notch>] 1000 [add_money<condition=%player_name%!=Notch>] 1000
vanished
Execute the action if the player is in vanish or not.
[broadcast<vanished=false>] This player is not in vanish!
inverted
If the value doesn't get met, then the outcome is successful. Inverted is disabled by default.
cached
If the value should be cached, this is useful if you've got a lot of requirements and do not want to constantly check for the same outcome. Caching is enabled by default.
type
The type of the requirement, you can view all the requirement types below.