SupaHam - User contributions [en]

MCBall

2015-03-24T20:59:15Z

SupaHam:

MCBall is a unique paintball Minecraft server. MCBall was first launched back in May/June of 2012, and has been running 24/7 ever since, providing an unforgettable experience to over 115,000 (24th March 2015) players from all over the world.

'''Website''': http://mcball.net

'''Minecraft IP address''': play.mcball.net
=Original=
Around May/June of 2012, MCBall was first launched with a gamemode called TDM. In this gamemode there were two teams: Blue and Red. Each player that joined the game would get split up into both teams, adding a balance to the game for all. In TDM, each player had a single life each match, and a stack of snowballs. When the player ran out of snowballs, the player automatically reloaded. Alternatively, left clicking would reload. Reloading took five seconds to complete, if a reload is initiated whilst the player has snowballs, the snowballs are removed.

When a game is not active (usually counting down towards the next game), all players are within the lobby. The Lobby had podiums of the top 3 players on the server, based on the highest K/D (read more later). In the lobby, there was also NPCs which each sold the player different items, hookshots, flashbangs, and many other perks, for points. Points were awarded by killing players.

Every kill, shot fired, death, win, and loss was recorded per player. Kills and deaths were arguably the most important feature of the game, used to generate a player's K/DR (Kill/Death Ratio).

LimitedNametags

2015-03-24T20:52:59Z

SupaHam: Added General Usage section.

LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to [http://www.spigotmc.org/members/clippy.16503/ ''gsand''] AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

You can purchase this plugin over at SpigotMC, [http://www.spigotmc.org/resources/4699/ click here].

=General Usage=
The idea of LimitedNametags is to provide a unique experience from the basic minecraft mechanic of nametag rendering. Although this '''server-side''' plugin does not necessarily change the client code, it does how ever plug in to the server platform known as [http://www.spigotmc.org/ Spigot].

I first implemented this mechanic on [[MCBall|MCBall]] back in 2014 to replace the blank nametags. Blank nametags were made possible using 4 section signs as the player name (§§§§), leaving a little empty box above the player's head. Prior to that, all players were forced to sneak in order to hide nametags rendering behind walls, but that was just plain ugly and irritating. That just wasn't good enough, so after some research, I figured it out, and implemented the feature. Where you, as a player, couldn't see your opponent's nametags at all, but were able to see your teammates'. A few weeks ago, gsand reminded me of the idea, but with a radius based aspect, instead of "team" based, and here we are today, releasing LimitedNametags publicly. LimitedNametags can be used in many ways, not just a paintball server.

=Commands=
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

=Configuration=
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
==config.yml==
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| (OUTDATED) worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| {{since|1.1}} worlds.<world>.radius-groups || [[Configurations#Section|Section]] || This section specifies the radius groups used to default what radius a player gets based on their permission. If they don't have permission to any of the groups, LimitedNametags will fallback to the group called ''default'', '''thus the default group must always be defined'''!
|-
| {{since|1.1}} worlds.<world>.radius-groups.<groupName> || [[Configurations#Double|Double]] || This double specifies the radius of nametag visibility for players in this group. A radius group is applied to a player by giving them the permission node 'limitednametags.radius.<groupName>', where <groupName> is the same as this configuration key, except lowercased; meaning ABC would be abc. Please do not confuse this with group implementations provided by permission plugins.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|}

==Examples==
{{example|title=Generic config.yml|text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in a world named 'world'.
world:
# Whether to enable this world, this is provided as a convenient option instead of having to remove the whole world configuration.
enabled: true
# Permission based groups to check for each player, with the default always given to the player.
radius-groups:
# default group to give all players, with a nametag visibility radius of 10 meters/blocks. This is required and always needs to be defined.
default: 10.0
# vip group to give to players by giving them the permission 'limitednametags.radius.vip', with a nametag visibility radius of 20 meters/blocks.
vip: 20.0
# client team name, don't worry about this unless told to.
team-name: ltd-nt
</syntaxhighlight>
}}

{{example|title=Generic config.yml. Credits go to Gsand |text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in all loaded worlds.
'*':
enabled: false
radius-groups:
default: 10.0
vip: 20.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'world_the_end', and overwrite the default settings (asterisk configuration above).
'world_the_end':
enabled: true
radius-groups:
default: 5.0
vip: 8.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'kitpvp', and overwrite the default settings (asterisk configuration above).
'kitpvp':
enabled: true
radius-groups:
default: 16.0
vip: 20.0
team-name: ltd-nt
</syntaxhighlight>
}}

MCBall

2015-03-24T20:35:42Z

SupaHam: initial creation.

MCBall is a unique paintball Minecraft server. MCBall was first launched back in May/June of 2012, and has been running 24/7 ever since, providing an unforgettable experience to over 115,000 (24th March 2015) players from all over the world.

=Original=
Around May/June of 2012, MCBall was first launched with a gamemode called TDM. In this gamemode there were two teams: Blue and Red. Each player that joined the game would get split up into both teams, adding a balance to the game for all. In TDM, each player had a single life each match, and a stack of snowballs. When the player ran out of snowballs, the player automatically reloaded. Alternatively, left clicking would reload. Reloading took five seconds to complete, if a reload is initiated whilst the player has snowballs, the snowballs are removed.

When a game is not active (usually counting down towards the next game), all players are within the lobby. The Lobby had podiums of the top 3 players on the server, based on the highest K/D (read more later). In the lobby, there was also NPCs which each sold the player different items, hookshots, flashbangs, and many other perks, for points. Points were awarded by killing players.

Every kill, shot fired, death, win, and loss was recorded per player. Kills and deaths were arguably the most important feature of the game, used to generate a player's K/DR (Kill/Death Ratio).

LimitedNametags

2015-03-12T07:08:26Z

SupaHam: Updated page formatting.

LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to [http://www.spigotmc.org/members/clippy.16503/ ''gsand''] AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

You can purchase this plugin over at SpigotMC, [http://www.spigotmc.org/resources/4699/ click here].

=Commands=
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

=Configuration=
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
==config.yml==
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| (OUTDATED) worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| {{since|1.1}} worlds.<world>.radius-groups || [[Configurations#Section|Section]] || This section specifies the radius groups used to default what radius a player gets based on their permission. If they don't have permission to any of the groups, LimitedNametags will fallback to the group called ''default'', '''thus the default group must always be defined'''!
|-
| {{since|1.1}} worlds.<world>.radius-groups.<groupName> || [[Configurations#Double|Double]] || This double specifies the radius of nametag visibility for players in this group. A radius group is applied to a player by giving them the permission node 'limitednametags.radius.<groupName>', where <groupName> is the same as this configuration key, except lowercased; meaning ABC would be abc. Please do not confuse this with group implementations provided by permission plugins.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|}

==Examples==
{{example|title=Generic config.yml|text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in a world named 'world'.
world:
# Whether to enable this world, this is provided as a convenient option instead of having to remove the whole world configuration.
enabled: true
# Permission based groups to check for each player, with the default always given to the player.
radius-groups:
# default group to give all players, with a nametag visibility radius of 10 meters/blocks. This is required and always needs to be defined.
default: 10.0
# vip group to give to players by giving them the permission 'limitednametags.radius.vip', with a nametag visibility radius of 20 meters/blocks.
vip: 20.0
# client team name, don't worry about this unless told to.
team-name: ltd-nt
</syntaxhighlight>
}}

{{example|title=Generic config.yml. Credits go to Gsand |text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in all loaded worlds.
'*':
enabled: false
radius-groups:
default: 10.0
vip: 20.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'world_the_end', and overwrite the default settings (asterisk configuration above).
'world_the_end':
enabled: true
radius-groups:
default: 5.0
vip: 8.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'kitpvp', and overwrite the default settings (asterisk configuration above).
'kitpvp':
enabled: true
radius-groups:
default: 16.0
vip: 20.0
team-name: ltd-nt
</syntaxhighlight>
}}

LimitedNametags

2015-03-12T07:07:53Z

SupaHam: Added reference to SpigotMC resource page.

=LimitedNametags=
LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to [http://www.spigotmc.org/members/clippy.16503/ ''gsand''] AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

You can purchase this plugin over at SpigotMC, [http://www.spigotmc.org/resources/4699/ click here].

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
===config.yml===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| (OUTDATED) worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| {{since|1.1}} worlds.<world>.radius-groups || [[Configurations#Section|Section]] || This section specifies the radius groups used to default what radius a player gets based on their permission. If they don't have permission to any of the groups, LimitedNametags will fallback to the group called ''default'', '''thus the default group must always be defined'''!
|-
| {{since|1.1}} worlds.<world>.radius-groups.<groupName> || [[Configurations#Double|Double]] || This double specifies the radius of nametag visibility for players in this group. A radius group is applied to a player by giving them the permission node 'limitednametags.radius.<groupName>', where <groupName> is the same as this configuration key, except lowercased; meaning ABC would be abc. Please do not confuse this with group implementations provided by permission plugins.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|}

===Examples===
{{example|title=Generic config.yml|text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in a world named 'world'.
world:
# Whether to enable this world, this is provided as a convenient option instead of having to remove the whole world configuration.
enabled: true
# Permission based groups to check for each player, with the default always given to the player.
radius-groups:
# default group to give all players, with a nametag visibility radius of 10 meters/blocks. This is required and always needs to be defined.
default: 10.0
# vip group to give to players by giving them the permission 'limitednametags.radius.vip', with a nametag visibility radius of 20 meters/blocks.
vip: 20.0
# client team name, don't worry about this unless told to.
team-name: ltd-nt
</syntaxhighlight>
}}

{{example|title=Generic config.yml. Credits go to Gsand |text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in all loaded worlds.
'*':
enabled: false
radius-groups:
default: 10.0
vip: 20.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'world_the_end', and overwrite the default settings (asterisk configuration above).
'world_the_end':
enabled: true
radius-groups:
default: 5.0
vip: 8.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'kitpvp', and overwrite the default settings (asterisk configuration above).
'kitpvp':
enabled: true
radius-groups:
default: 16.0
vip: 20.0
team-name: ltd-nt
</syntaxhighlight>
}}

LimitedNametags

2015-03-12T07:06:10Z

SupaHam: Added Examples section.

=LimitedNametags=
LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to [http://www.spigotmc.org/members/clippy.16503/ ''gsand''] AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
===config.yml===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| (OUTDATED) worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| {{since|1.1}} worlds.<world>.radius-groups || [[Configurations#Section|Section]] || This section specifies the radius groups used to default what radius a player gets based on their permission. If they don't have permission to any of the groups, LimitedNametags will fallback to the group called ''default'', '''thus the default group must always be defined'''!
|-
| {{since|1.1}} worlds.<world>.radius-groups.<groupName> || [[Configurations#Double|Double]] || This double specifies the radius of nametag visibility for players in this group. A radius group is applied to a player by giving them the permission node 'limitednametags.radius.<groupName>', where <groupName> is the same as this configuration key, except lowercased; meaning ABC would be abc. Please do not confuse this with group implementations provided by permission plugins.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|}

===Examples===
{{example|title=Generic config.yml|text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in a world named 'world'.
world:
# Whether to enable this world, this is provided as a convenient option instead of having to remove the whole world configuration.
enabled: true
# Permission based groups to check for each player, with the default always given to the player.
radius-groups:
# default group to give all players, with a nametag visibility radius of 10 meters/blocks. This is required and always needs to be defined.
default: 10.0
# vip group to give to players by giving them the permission 'limitednametags.radius.vip', with a nametag visibility radius of 20 meters/blocks.
vip: 20.0
# client team name, don't worry about this unless told to.
team-name: ltd-nt
</syntaxhighlight>
}}

{{example|title=Generic config.yml. Credits go to Gsand |text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in all loaded worlds.
'*':
enabled: false
radius-groups:
default: 10.0
vip: 20.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'world_the_end', and overwrite the default settings (asterisk configuration above).
'world_the_end':
enabled: true
radius-groups:
default: 5.0
vip: 8.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'kitpvp', and overwrite the default settings (asterisk configuration above).
'kitpvp':
enabled: true
radius-groups:
default: 16.0
vip: 20.0
team-name: ltd-nt
</syntaxhighlight>
}}

LimitedNametags

2015-03-12T07:03:59Z

SupaHam: Added a few more examples, thanks to gsand.

=LimitedNametags=
LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to [http://www.spigotmc.org/members/clippy.16503/ ''gsand''] AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
===config.yml===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| (OUTDATED) worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| {{since|1.1}} worlds.<world>.radius-groups || [[Configurations#Section|Section]] || This section specifies the radius groups used to default what radius a player gets based on their permission. If they don't have permission to any of the groups, LimitedNametags will fallback to the group called ''default'', '''thus the default group must always be defined'''!
|-
| {{since|1.1}} worlds.<world>.radius-groups.<groupName> || [[Configurations#Double|Double]] || This double specifies the radius of nametag visibility for players in this group. A radius group is applied to a player by giving them the permission node 'limitednametags.radius.<groupName>', where <groupName> is the same as this configuration key, except lowercased; meaning ABC would be abc. Please do not confuse this with group implementations provided by permission plugins.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|}

{{example|title=Generic config.yml|text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in a world named 'world'.
world:
# Whether to enable this world, this is provided as a convenient option instead of having to remove the whole world configuration.
enabled: true
# Permission based groups to check for each player, with the default always given to the player.
radius-groups:
# default group to give all players, with a nametag visibility radius of 10 meters/blocks. This is required and always needs to be defined.
default: 10.0
# vip group to give to players by giving them the permission 'limitednametags.radius.vip', with a nametag visibility radius of 20 meters/blocks.
vip: 20.0
# client team name, don't worry about this unless told to.
team-name: ltd-nt
</syntaxhighlight>
}}

{{example|title=Generic config.yml. Credits go to Gsand |text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in all loaded worlds.
'*':
enabled: false
radius-groups:
default: 10.0
vip: 20.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'world_the_end', and overwrite the default settings (asterisk configuration above).
'world_the_end':
enabled: true
radius-groups:
default: 5.0
vip: 8.0
team-name: ltd-nt
# Tell LimitedNametags to operate in a world named 'kitpvp', and overwrite the default settings (asterisk configuration above).
'kitpvp':
enabled: true
radius-groups:
default: 16.0
vip: 20.0
team-name: ltd-nt
</syntaxhighlight>
}}

LimitedNametags

2015-03-12T06:55:02Z

SupaHam: Fixed config.yml table formatting.

=LimitedNametags=
LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to [http://www.spigotmc.org/members/clippy.16503/ ''gsand''] AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
===config.yml===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| (OUTDATED) worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| {{since|1.1}} worlds.<world>.radius-groups || [[Configurations#Section|Section]] || This section specifies the radius groups used to default what radius a player gets based on their permission. If they don't have permission to any of the groups, LimitedNametags will fallback to the group called ''default'', '''thus the default group must always be defined'''!
|-
| {{since|1.1}} worlds.<world>.radius-groups.<groupName> || [[Configurations#Double|Double]] || This double specifies the radius of nametag visibility for players in this group. A radius group is applied to a player by giving them the permission node 'limitednametags.radius.<groupName>', where <groupName> is the same as this configuration key, except lowercased; meaning ABC would be abc. Please do not confuse this with group implementations provided by permission plugins.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|}

{{example|title=Generic config.yml|text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in a world named ''world''.
world:
# Whether to enable this world, this is provided as a convenient option instead of having to remove the whole world configuration.
enabled: true
# Permission based groups to check for each player, with the default always given to the player.
radius-groups:
# default group to give all players, with a nametag visibility radius of 10 meters/blocks. This is required and always needs to be defined.
default: 10.0
# vip group to give to players by giving them the permission 'limitednametags.radius.vip', with a nametag visibility radius of 20 meters/blocks.
vip: 20.0
# client team name, don't worry about this unless told to.
team-name: ltd-nt
</syntaxhighlight>
}}

LimitedNametags

2015-03-12T06:54:15Z

SupaHam: Added config.yml example.

=LimitedNametags=
LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to [http://www.spigotmc.org/members/clippy.16503/ ''gsand''] AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
===config.yml===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| (OUTDATED) worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| {{since|1.1}} worlds.<world>.radius-groups || [[Configurations#Section|Section]] || This section specifies the radius groups used to default what radius a player gets based on their permission. If they don't have permission to any of the groups, LimitedNametags will fallback to the group called ''default'', '''thus the default group must always be defined'''!
|-
| {{since|1.1}} worlds.<world>.radius-groups.<groupName> || [[Configurations#Double|Double]] || This double specifies the radius of nametag visibility for players in this group. A radius group is applied to a player by giving them the permission node 'limitednametags.radius.<groupName>', where <groupName> is the same as this configuration key, except lowercased; meaning ABC would be abc. Please do not confuse this with group implementations provided by permission plugins.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|-
|
|}

{{example|title=Generic config.yml|text=
<syntaxhighlight lang="yaml">
worlds:
# Tell LimitedNametags to operate in a world named ''world''.
world:
# Whether to enable this world, this is provided as a convenient option instead of having to remove the whole world configuration.
enabled: true
# Permission based groups to check for each player, with the default always given to the player.
radius-groups:
# default group to give all players, with a nametag visibility radius of 10 meters/blocks. This is required and always needs to be defined.
default: 10.0
# vip group to give to players by giving them the permission 'limitednametags.radius.vip', with a nametag visibility radius of 20 meters/blocks.
vip: 20.0
# client team name, don't worry about this unless told to.
team-name: ltd-nt
</syntaxhighlight>
}}

LimitedNametags

2015-03-09T23:53:26Z

SupaHam: Added version 1.1 documentation.

Configurations

2015-03-07T15:25:23Z

SupaHam: /* Minecraft */

=Format=

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

=Types=
==General==

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===Double===
This type is like an '''Integer''', but accepts decimals and can store 15 digits.

===Float===
This type is like '''Double''', but stores only 7 digits.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===List===
This type is a Collection, you can give it more than one '''single type'''. An example for usage of List would be player names that should be allowed to build in an area.

===String===
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.

==Minecraft==
These are Minecraft related types.

===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'
enchants:
DAMAGE_ALL: 2
repair-cost: 1

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

===EntityType===
This type represents a Minecraft '''Entity Type''' through [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/EntityType.html#enum_constant_summary Bukkit's enum names]. These don't necessarily have to be UPPERCASE as the provided value will always be converted into uppercase letters.

NPCs

2015-03-07T15:19:14Z

SupaHam: Added API to ToC

=NPCs=
NPCs is a lightweight Bukkit Plugin created by SupaHam publicly available as a free resource on [http://www.spigotmc.org/ SpigotMC] that adds the possibility of creating all sorts of NPCs. You can create NPCs that when left clicked executes a command, such as giving the player a diamond, or even ones that socialise with the Player. Are you sad that the Minecraft 1.8 update has removed the always visible nametags? :( Well, lucky you, you can give NPCs persistent nametags that will follow the NPC where ever they go with one line of code: <syntaxhighlight lang="yaml"> name: 'My awesome NPC' </syntaxhighlight>. This project is open source under the [https://www.gnu.org/licenses/gpl.html GPL v3 license] and can be found at [https://github.com/SupaHam/NPCs https://github.com/SupaHam/NPCs].

{| class="wiki-table"
!ToC
|-
| [[NPCs/Properties|Properties]]
|-
| [[NPCs/API|API]] (Not ready yet) Check the github page for now.
|}

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || npcs || npcs.cmd.reload || || Reloads the NPCs configuration file and refreshes all existing NPC entites.
|}

NPCs

2015-03-07T15:06:41Z

SupaHam: Fixed properties link

=NPCs=
NPCs is a lightweight Bukkit Plugin created by SupaHam publicly available as a free resource on [http://www.spigotmc.org/ SpigotMC] that adds the possibility of creating all sorts of NPCs. You can create NPCs that when left clicked executes a command, such as giving the player a diamond, or even ones that socialise with the Player. Are you sad that the Minecraft 1.8 update has removed the always visible nametags? :( Well, lucky you, you can give NPCs persistent nametags that will follow the NPC where ever they go with one line of code: <syntaxhighlight lang="yaml"> name: 'My awesome NPC' </syntaxhighlight>. This project is open source under the [https://www.gnu.org/licenses/gpl.html GPL v3 license] and can be found at [https://github.com/SupaHam/NPCs https://github.com/SupaHam/NPCs].

{| class="wiki-table"
!ToC
|-
| [[NPCs/Properties|Properties]]
|}

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || npcs || npcs.cmd.reload || || Reloads the NPCs configuration file and refreshes all existing NPC entites.
|}

NPCs

2015-03-07T15:06:09Z

SupaHam: Added Properties link.

=NPCs=
NPCs is a lightweight Bukkit Plugin created by SupaHam publicly available as a free resource on [http://www.spigotmc.org/ SpigotMC] that adds the possibility of creating all sorts of NPCs. You can create NPCs that when left clicked executes a command, such as giving the player a diamond, or even ones that socialise with the Player. Are you sad that the Minecraft 1.8 update has removed the always visible nametags? :( Well, lucky you, you can give NPCs persistent nametags that will follow the NPC where ever they go with one line of code: <syntaxhighlight lang="yaml"> name: 'My awesome NPC' </syntaxhighlight>. This project is open source under the [https://www.gnu.org/licenses/gpl.html GPL v3 license] and can be found at [https://github.com/SupaHam/NPCs https://github.com/SupaHam/NPCs].

{| class="wiki-table"
!ToC
|-
| [[NPCs/Properties Properties]]
|}

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || npcs || npcs.cmd.reload || || Reloads the NPCs configuration file and refreshes all existing NPC entites.
|}

NPCs

2015-03-07T14:50:18Z

SupaHam:

=NPCs=
NPCs is a lightweight Bukkit Plugin created by SupaHam publicly available as a free resource on [http://www.spigotmc.org/ SpigotMC] that adds the possibility of creating all sorts of NPCs. You can create NPCs that when left clicked executes a command, such as giving the player a diamond, or even ones that socialise with the Player. Are you sad that the Minecraft 1.8 update has removed the always visible nametags? :( Well, lucky you, you can give NPCs persistent nametags that will follow the NPC where ever they go with one line of code: <syntaxhighlight lang="yaml"> name: 'My awesome NPC' </syntaxhighlight>. This project is open source under the [https://www.gnu.org/licenses/gpl.html GPL v3 license] and can be found at [https://github.com/SupaHam/NPCs https://github.com/SupaHam/NPCs].

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || npcs || npcs.cmd.reload || || Reloads the NPCs configuration file and refreshes all existing NPC entites.
|}

NPCs/Properties

2015-03-07T14:49:21Z

SupaHam: Added examples.

Each NPC must have at least one property in order for them to properly spawn in the world. There are multiple properties to choose from, but the most important two are the location and type property.
{{example|title=Example of a PIG entity, that spawns at x: 14, y: 75, z: 149 in world 'world', with a persistent nametag called pIggy, when left clicked, and the player has the permission 'let.me.left.click', the command 'say test' is executed by the CONSOLE, and finally apply some vanilla minecraft NBT data to the piggy, making it invulnerable to damage.|text=
<syntaxhighlight lang="yaml">
npcs:
test:
type: PIG
location: world 14 75 149
name: pIggy
cmds-left-click: ~say test
cmds-left-click-perm: let.me.left.click
mc-nbt: '{Invulnerable:1}'
</syntaxhighlight>
}}
=Properties=
blah
{| class="wiki-table"
! Property Name
! width="100"| Value
! Description
|-
| type || [[Configurations#EntityType|EntityType]] || Type of the NPC to create e.g. PIG
|-
| location || [[Configurations#Location|Location]] || The location to spawn this NPC at.
|-
! class="hl2" colspan="3" | Commands
|-
| cmds-left-click || [[Configurations#String|String]] || The command to execute when this NPC is left clicked. Prefix command with ~ to execute command as CONSOLE. Available placeholders: $pname - player's name $dname - player's display name
|-
| cmds-left-click-perm || [[Configurations#String|String]] || The permission required to execute the cmds-left-click command. This value is ignored if cmds-left-click is not set.
|-
| cmds-right-click || [[Configurations#String|String]] || The command to execute when this NPC is left clicked. Read cmds-left-click for more info.
|-
| cmds-right-click-perm || [[Configurations#String|String]] || The permission required to execute the cmds-right-click command. This value is ignored if cmds-right-click is not set.
|-
! class="hl2" colspan="3" | Nametags
|-
| name || [[Configurations#String|String]] || The name to give the NPC. The nametag will always be visible above the NPC's head. Note: Having hundreds of these may start causing lag if the entity is moving around.
|-
! class="hl2" colspan="3" | Minecraft NBT
|-
| mc-nbt || NBT as [[Configurations#String|String]] || The minecraft NBT data to assign to this NPC. This is the same data as the ones used in vanilla's /summon and /entitydata commands. Please refer to this[http://minecraft.gamepedia.com/Commands#Data_tags this] and [http://minecraft.gamepedia.com/Tutorials/Command_NBT_Tags#Entities this] for more information and assistance with usage.
|-
! class="hl2" colspan="3" | Persistence
|-
| npc-max-health || [[Configurations#Boolean|Boolean]] || This configuration does not require a value, if set, the NPC will always have max health, making them vulnerable, but with infinite health.
|-
| npc-invulnerable || [[Configurations#Boolean|Boolean]] || This configuration does not require a value, if set, the NPC will be invulnerable to all damage. This is recommended over nbt to ensure the NPC's lifetime. If applied to an ITEM NPC, the item will never despawn.
|-
! class="hl2" colspan="3" | Social
|-
| npc-social || [[Configurations#Section|Section]] || This is the social section for this npc, used for verbal "interaction" from the NPC.
|-
| npc-social.nearby || [[Configurations#Section|Section]] || This is the nearby social section; used to communicate with a player approaching the NPC.
|-
| npc-social.nearby.cooldown || [[Configurations#Integer|Integer]] || This is the cooldown in between communication made by the NPC to the player.
|-
| npc-social.nearby.range || [[Configurations#Integer|Integer]] || This is the activation range in which the NPC will instantly communicate with the approaching Player.
|-
| npc-social.nearby.messages || List of [[Configurations#String|String]] || This is a list of possible messages to send to the player. Only one is chosen randomly upon approach and sent to the player.
|-
| wg-spawn-in || List of [[Configurations#String|String]] || This is a list of WorldGuard region names the NPC may spawn in. This is not really much use for a normal plugin user and is focused for developers looking to make their own custom NPCs.
|}

{{example|title=Commands|text=
<syntaxhighlight lang="yaml">
npcs:
test:
type: ZOMBIE
location: world 14 75 149
cmds-left-click: ~stop # Please don't actually do this D:
cmds-left-click-perm: i.can.stop.the.server
cmds-right-click: ~msg $pname Cool name, $name.
# Since cmds-right-click-perm isn't set, anyone can right click and execute the command.
# cmds-right-click-perm:
</syntaxhighlight>
}}

{{example|title=Nametags|text=
<syntaxhighlight lang="yaml">
npcs:
test:
type: ARMOR_STAND
location: world 14 75 149
name: Look at me! I'm cool!
</syntaxhighlight>
}}

{{example|title=Minecraft NBT|text=
<syntaxhighlight lang="yaml">
npcs:
test:
type: ARMOR_STAND
location: world 14 75 149
mc-nbt: '{Invulnerable:1,NoBasePlate:1,NoGravity:1,ShowArms:1,DisabledSlots:2039552,Rotation:[0f],
Equipment:[{id:"chest"},{id:"leather_boots"},{id:"leather_leggings"},{id:"leather_chestplate"},{id:"skull",Damage:3,tag:{SkullOwner:"Santa"}}]
}'
</syntaxhighlight>
}}

{{example|title=Persistence|text=
<syntaxhighlight lang="yaml">
npcs:
test:
type: ARMOR_STAND
location: world 14 75 149
npc-max-health: true
npc-invulnerable: true
</syntaxhighlight>
}}

{{example|title=Approaching socialization|text=
<syntaxhighlight lang="yaml">
npcs:
test:
type: PIG
location: world 14 75 149
npc-social:
nearby:
cooldown: 10
range: 7
messages:
- |
&cHello there, $pname.
&eYour display name is '$dname&e'.
- This is a second message that could be picked randomly instead of the first.
</syntaxhighlight>
}}

NPCs/Properties

2015-03-07T14:36:11Z

SupaHam: Added properties documentation \o/

NPCs/Properties

2015-03-07T12:46:44Z

SupaHam: Moved Properties section to the bottom

NPCs/Properties

2015-03-07T12:46:00Z

SupaHam: Added example of an npc in npcs.yml.

=Properties=
Each NPC must have at least one property in order for them to properly spawn in the world. There are multiple properties to choose from, but the most important two are the location and type property.
{{example|title=Example of a PIG entity, that spawns at x: 14, y: 75, z: 149 in world 'world', with a persistent nametag called pIggy, when left clicked, and the player has the permission 'let.me.left.click', the command 'say test' is executed by the CONSOLE, and finally apply some vanilla minecraft NBT data to the piggy, making it invulnerable to damage.|text=
<syntaxhighlight lang="yaml">
npcs:
test:
type: PIG
location: world 14 75 149
name: pIggy
cmds-left-click: ~say test
cmds-left-click-perm: let.me.left.click
mc-nbt: '{Invulnerable:1}'
</syntaxhighlight>
}}

NPCs

2015-03-07T12:35:05Z

SupaHam: Added commands section.

=NPCs=
NPCs is a lightweight Bukkit Plugin created by SupaHam publicly available as a premium resource on [http://www.spigotmc.org/ Spigot] that adds the possibility of creating all sorts of NPCs. You can create NPCs that when left clicked executes a command, such as giving the player a diamond, or even ones that socialise with the Player. Are you sad that the Minecraft 1.8 update has removed the always visible nametags? :( Well, lucky you, you can give NPCs persistent nametags that will follow the NPC where ever they go with one line of code: <syntaxhighlight lang="yaml"> name: 'My awesome NPC' </syntaxhighlight>. This project is open source under the [https://www.gnu.org/licenses/gpl.html GPL v3 license] and can be found at [https://github.com/SupaHam/NPCs https://github.com/SupaHam/NPCs].

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || npcs || npcs.cmd.reload || || Reloads the NPCs configuration file and refreshes all existing NPC entites.
|}

LimitedNametags

2015-03-06T02:12:18Z

SupaHam: Linked to clippy's spigotmc profile page.

LimitedNametags

2015-03-06T02:10:51Z

SupaHam: Added tip help and short description addition.

=LimitedNametags=
LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to gsand AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like. The configuration is currently per world to allow the user to change the functionality to their liking.
===config.yml===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|-
|
|}

LimitedNametags

2015-03-06T02:09:11Z

SupaHam: initial creation.

=LimitedNametags=
LimitedNametags is a Bukkit plugin created by SupaHam, that adds the possibility to limit nametag view distance. It requires almost no setup, other than installing it and ProtocolLib in your server's plugins directory. Credit goes to gsand AKA Clippy in the Spigot community for bringing this concept of a plugin to me.

==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || limitednametags || limitednametags.cmd.reload || lt || Reloads the LimitedNametags configuration file and refreshes all online players.
|}

==Configuration==
LimitedNametags provides configurable options for the user to tweak the plugin just the way they like.
===config.yml===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| worlds || [[Configurations#Section|Section]] || This section contains a list of world names that LimitedNametags should operate in.
|-
| worlds.<world> || [[Configurations#Section|Section]] || This section is named after a specific existing world that LimitedNametags should operate in. Use '*' (asterisk) to refer to all worlds.
|-
| worlds.<world>.enabled || [[Configurations#Boolean|Boolean]] || This boolean specifies whether LimitedNametags should use this world. This is simply a convenient method of telling the plugin to not use '''<world>''' without the user actually deleting the data.
|-
| worlds.<world>.nametag-radius || [[Configurations#Double|Double]] || This double specifies the view distance (in block units) that players should be able to see each other's nametags.
|-
| worlds.<world>.team-name || [[Configurations#String|String]] || This string specifies the team name that manages the nametag visibility function. This is a technical feature that you as a user do not need to worry about unless told so.
|-
|
|}

Configurations

2015-01-28T10:59:26Z

SupaHam: Organized a bit more.

=Format=

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

=Types=
==General==

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===Double===
This type is like an '''Integer''', but accepts decimals and can store 15 digits.

===Float===
This type is like '''Double''', but stores only 7 digits.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===List===
This type is a Collection, you can give it more than one '''single type'''. An example for usage of List would be player names that should be allowed to build in an area.

===String===
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.

==Minecraft==
These are Minecraft related types.

===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'
enchants:
DAMAGE_ALL: 2
repair-cost: 1

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

===Entity Type===
This type represents a Minecraft '''Entity Type''' through [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/EntityType.html#enum_constant_summary Bukkit's enum names]. These don't necessarily have to be UPPERCASE as the provided value will always be converted into uppercase letters.

Template:Tlf

2015-01-28T00:41:17Z

SupaHam: Created page with "{{{{#if:{{{1|}}}|{{{1}}}| tlf|...}}{{#ifeq:{{{2|x}}}|{{{2|}}}| |{{{2}}} | }}{{#ifeq:{{{3|x}}}|{{{3|}}}| |{{{3}}}..."

{{{{#if:{{{1|}}}|{{{1}}}| tlf|...}}{{#ifeq:{{{2|x}}}|{{{2|}}}| |{{{2}}} | }}{{#ifeq:{{{3|x}}}|{{{3|}}}| |{{{3}}} | }}{{#ifeq:{{{4|x}}}|{{{4|}}}| |{{{4}}} | }}{{#ifeq:{{{5|x}}}|{{{5|}}}| |{{{5}}} | }}{{#ifeq:{{{6|x}}}|{{{6|}}}| |{{{6}}} | }}{{#ifeq:{{{7|x}}}|{{{7|}}}| |{{{7}}} | }}{{#ifeq:{{{8|x}}}|{{{8|}}}| |{{{8}}} | }}{{#ifeq:{{{9|x}}}|{{{9|}}}| |{{{9}}} | }}}}

Template:Tl

2015-01-28T00:40:16Z

SupaHam: Created page with "{{{{{1}}}}}"

{{[[Template:{{{1}}}|{{{1}}}]]}}

Template:Table

2015-01-28T00:35:20Z

SupaHam:

<includeonly>{{#if:{{{colheaders|}}}{{{row1|}}}{{{hdrs|}}} |
| '''WARNING: You are using the {{tl|Table}} template without the parameters {{mono|colheaders}} and/or {{mono|row1}}. When applying this template, the appearance of the text "{{tnf|Table}}" in the code/markup indicates an incorrect use. Please ensure {{tnf|Table}} is used according to its documentation, ''otherwise'' use wiki markup{{\}}HTML (see [[Help:Tables]]).'''<div style="display:none;">}}</includeonly>{| {{{type|style="background:transparent;"}}}

{{#if:{{{title|}}}
|{{!}}+ {{#if:{{{titlestyle|}}}|style="{{{titlestyle}}}"{{!}}}} {{{title}}}
}}

{{!-}} {{#if:{{{valign|}}}{{{colheadersstyle|{{{hdrsstyle|}}}}}} |style="{{{colheadersstyle|{{{hdrsstyle|}}}}}} {{#if:{{{valign|}}}|vertical-align:{{{valign}}};}}"}}
{{#if:{{{colheaders|{{{hdrs|}}}}}} |! {{{colheaders|{{{hdrs|}}}}}}
{{!-}} {{#if:{{{valign|}}} |style="vertical-align:{{{valign}}};"}}
}}

{{#if:{{{row1|}}} |{{!}} {{{row1}}} }}{{#if:{{{row2|}}} |{{br!-!}} {{{row2}}} }}{{#if:{{{row3|}}} |{{br!-!}} {{{row3}}} }}{{#if:{{{row4|}}} |{{br!-!}} {{{row4}}} }}{{#if:{{{row5|}}} |{{br!-!}} {{{row5}}} }}{{#if:{{{row6|}}} |{{br!-!}} {{{row6}}} }}{{#if:{{{row7|}}} |{{br!-!}} {{{row7}}} }}{{#if:{{{row8|}}} |{{br!-!}} {{{row8}}} }}{{#if:{{{row9|}}} |{{br!-!}} {{{row9}}} }}{{#if:{{{row10|}}} |{{br!-!}} {{{row10}}} }}{{#if:{{{row11|}}} |{{br!-!}} {{{row11}}} }}{{#if:{{{row12|}}} |{{br!-!}} {{{row12}}} }}{{#if:{{{row13|}}} |{{br!-!}} {{{row13}}} }}{{#if:{{{row14|}}} |{{br!-!}} {{{row14}}} }}{{#if:{{{row15|}}} |{{br!-!}} {{{row15}}} }}{{#if:{{{row16|}}} |{{br!-!}} {{{row16}}} }}{{#if:{{{row17|}}} |{{br!-!}} {{{row17}}} }}{{#if:{{{row18|}}} |{{br!-!}} {{{row18}}} }}{{#if:{{{row19|}}} |{{br!-!}} {{{row19}}} }}{{#if:{{{row20|}}} |{{br!-!}} {{{row20}}} }}{{#if:{{{row21|}}} |{{br!-!}} {{{row21}}} }}{{#if:{{{row22|}}} |{{br!-!}} {{{row22}}} }}{{#if:{{{row23|}}} |{{br!-!}} {{{row23}}} }}{{#if:{{{row24|}}} |{{br!-!}} {{{row24}}} }}{{#if:{{{row25|}}} |{{br!-!}} {{{row25}}} }}{{#if:{{{row26|}}} |{{br!-!}} {{{row26}}} }}{{#if:{{{row27|}}} |{{br!-!}} {{{row27}}} }}{{#if:{{{row28|}}} |{{br!-!}} {{{row28}}} }}{{#if:{{{row29|}}} |{{br!-!}} {{{row29}}} }}{{#if:{{{row30|}}} |{{br!-!}} {{{row30}}} }}{{#if:{{{row31|}}} |{{br!-!}} {{{row31}}} }}{{#if:{{{row32|}}} |{{br!-!}} {{{row32}}} }}{{#if:{{{row33|}}} |{{br!-!}} {{{row33}}} }}{{#if:{{{row34|}}} |{{br!-!}} {{{row34}}} }}{{#if:{{{row35|}}} |{{br!-!}} {{{row35}}} }}{{#if:{{{row36|}}} |{{br!-!}} {{{row36}}} }}{{#if:{{{row37|}}} |{{br!-!}} {{{row37}}} }}{{#if:{{{row38|}}} |{{br!-!}} {{{row38}}} }}{{#if:{{{row39|}}} |{{br!-!}} {{{row39}}} }}{{#if:{{{row40|}}} |{{br!-!}} {{{row40}}} }}{{#if:{{{row41|}}} |{{br!-!}} {{{row41}}} }}{{#if:{{{row42|}}} |{{br!-!}} {{{row42}}} }}{{#if:{{{row43|}}} |{{br!-!}} {{{row43}}} }}{{#if:{{{row44|}}} |{{br!-!}} {{{row44}}} }}{{#if:{{{row45|}}} |{{br!-!}} {{{row45}}} }}{{#if:{{{row46|}}} |{{br!-!}} {{{row46}}} }}{{#if:{{{row47|}}} |{{br!-!}} {{{row47}}} }}{{#if:{{{row48|}}} |{{br!-!}} {{{row48}}} }}{{#if:{{{row49|}}} |{{br!-!}} {{{row49}}} }}{{#if:{{{row50|}}} |{{br!-!}} {{{row50}}} }}{{#if:{{{row51|}}} |{{br!-!}} {{{row51}}} }}{{#if:{{{row52|}}} |{{br!-!}} {{{row52}}} }}{{#if:{{{row53|}}} |{{br!-!}} {{{row53}}} }}{{#if:{{{row54|}}} |{{br!-!}} {{{row54}}} }}{{#if:{{{row55|}}} |{{br!-!}} {{{row55}}} }}{{#if:{{{row56|}}} |{{br!-!}} {{{row56}}} }}{{#if:{{{row57|}}} |{{br!-!}} {{{row57}}} }}{{#if:{{{row58|}}} |{{br!-!}} {{{row58}}} }}{{#if:{{{row59|}}} |{{br!-!}} {{{row59}}} }}{{#if:{{{row60|}}} |{{br!-!}} {{{row60}}} }}{{#if:{{{row61|}}} |{{br!-!}} {{{row61}}} }}{{#if:{{{row62|}}} |{{br!-!}} {{{row62}}} }}{{#if:{{{row63|}}} |{{br!-!}} {{{row63}}} }}{{#if:{{{row64|}}} |{{br!-!}} {{{row64}}} }}{{#if:{{{row65|}}} |{{br!-!}} {{{row65}}} }}{{#if:{{{row66|}}} |{{br!-!}} {{{row66}}} }}{{#if:{{{row67|}}} |{{br!-!}} {{{row67}}} }}{{#if:{{{row68|}}} |{{br!-!}} {{{row68}}} }}{{#if:{{{row69|}}} |{{br!-!}} {{{row69}}} }}{{#if:{{{row70|}}} |{{br!-!}} {{{row70}}} }}{{#if:{{{row71|}}} |{{br!-!}} {{{row71}}} }}{{#if:{{{row72|}}} |{{br!-!}} {{{row72}}} }}{{#if:{{{row73|}}} |{{br!-!}} {{{row73}}} }}{{#if:{{{row74|}}} |{{br!-!}} {{{row74}}} }}{{#if:{{{row75|}}} |{{br!-!}} {{{row75}}} }}{{#if:{{{row76|}}} |{{br!-!}} {{{row76}}} }}{{#if:{{{row77|}}} |{{br!-!}} {{{row77}}} }}{{#if:{{{row78|}}} |{{br!-!}} {{{row78}}} }}{{#if:{{{row79|}}} |{{br!-!}} {{{row79}}} }}{{#if:{{{row80|}}} |{{br!-!}} {{{row80}}} }}{{#if:{{{row81|}}} |{{br!-!}} {{{row81}}} }}{{#if:{{{row82|}}} |{{br!-!}} {{{row82}}} }}{{#if:{{{row83|}}} |{{br!-!}} {{{row83}}} }}{{#if:{{{row84|}}} |{{br!-!}} {{{row84}}} }}{{#if:{{{row85|}}} |{{br!-!}} {{{row85}}} }}{{#if:{{{row86|}}} |{{br!-!}} {{{row86}}} }}{{#if:{{{row87|}}} |{{br!-!}} {{{row87}}} }}{{#if:{{{row88|}}} |{{br!-!}} {{{row88}}} }}{{#if:{{{row89|}}} |{{br!-!}} {{{row89}}} }}{{#if:{{{row90|}}} |{{br!-!}} {{{row90}}} }}{{#if:{{{row91|}}} |{{br!-!}} {{{row91}}} }}{{#if:{{{row92|}}} |{{br!-!}} {{{row92}}} }}{{#if:{{{row93|}}} |{{br!-!}} {{{row93}}} }}{{#if:{{{row94|}}} |{{br!-!}} {{{row94}}} }}{{#if:{{{row95|}}} |{{br!-!}} {{{row95}}} }}{{#if:{{{row96|}}} |{{br!-!}} {{{row96}}} }}{{#if:{{{row97|}}} |{{br!-!}} {{{row97}}} }}{{#if:{{{row98|}}} |{{br!-!}} {{{row98}}} }}{{#if:{{{row99|}}} |{{br!-!}} {{{row99}}} }}{{#if:{{{row100|}}} |{{br!-!}} {{{row100}}} }}
|}<includeonly>{{#if:{{{colheaders|}}}{{{row1|}}}{{{hdrs|}}} |
| </div>[[Category:Articles using the Table template incorrectly]]
}}</includeonly>

Template:!-

2015-01-28T00:26:15Z

SupaHam: Created page with "|-<noinclude> {{documentation}} </noinclude>"

|-<noinclude>
{{documentation}}
</noinclude>

Template:Br!-!

2015-01-28T00:25:32Z

SupaHam: Created page with "<includeonly> |- |</includeonly><noinclude> {{Documentation | content = Variant of {{tlxpl|!-!}} which ensures its "start row" wikicode syntax ({{mono|{{!-}}}}) starts..."

<includeonly>
 
|-
|</includeonly><noinclude>
{{Documentation
| content =
Variant of {{tlxpl|!-!}} which ensures its "start row" wikicode syntax ({{mono|{{!-}}}}) starts on a new line (i.e. after a line reak):
<pre>
 
|-
|
</pre>
This can make it easier to e.g. use [[mw:Help:Extension:ParserFunctions|parser functions]] within wikicoded tables.

===See also===
* {{tlxpl|!-!}}, as above but without the initial newline.
* {{tlxpl|!-!!}}, as {{mono|{{braces|!-!}}}} but with a header cell as the first cell (in HTML, a <nowiki><th> rather than <td></nowiki> cell).

[[Category:Table and column templates]]
}}
</noinclude>

Template:Documentation

2015-01-28T00:24:23Z

SupaHam: Created page with "{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}<noinclude>  </noi..."

{{#invoke:documentation|main|_content={{ {{#invoke:documentation|contentTitle}}}}}}<noinclude>

</noinclude>

Template:Table

2015-01-28T00:23:45Z

SupaHam: Created page with "<includeonly>{{#if:{{{colheaders|}}}{{{row1|}}}{{{hdrs|}}} | | '''WARNING: You are using the {{tl..."

Commands

2015-01-27T22:08:13Z

SupaHam: Updated WorldEdit commands package.

A '''command''' in Minecraft starts with a '''forward slash (/)'''.

{{example|text='''/seed'''}}

The '''seed''' command is a vanilla command, meaning it comes with Minecraft without any modifications.
__TOC__
== Permissions ==
Some commands require '''permissions'''. If a player does not have the appropriate permissions for a command an error message is sent to the player. Vanilla commands that require permissions are acquired by becoming an [http://minecraft.gamepedia.com/Operator Operator].

Though Minecraft server modifications such as [http://bukkit.org/ Bukkit] have a permissions implementation that allow you to apply permission nodes (String) to players, this allows for maximum flexibility.

{{example|text=Imagine a scenario where you, as a '''server admin''', want to give a player permission to only mute other players, to help keep the chat clean. '''Without''' Bukkit this is not possible. You would have to give that player op status which gives them permission to all other commands on the server. You might not be able to trust someone with that many permissions, this is where '''Bukkit's SuperPerms''' implementation comes in. SuperPerms is a Bukkit implementation that allows for plugins to hook into Bukkit and check player permissions and with a permissions management plugin such as [http://dev.bukkit.org/bukkit-plugins/permissionsex/ PermissionsEx] you are able to manage player permissions and do much more.}}

A permission node is a '''String''' (text) usually seperated with '''fullstops/periods (.)''' instead of whitespaces.

{{example|text="'''my.command.permission'''"}}

== Arguments ==
There are commands such as /seed which are simple that tell you the seed of the current world you're in, but commands do much more than that. As a developer, you can implement '''commands with arguments''' to allow your users to insert their own values and the rest is done behind the scenes (in the code).

{{example|text=/tp [target player] <destination player> /tp [target player] <x> <y> <z>}}

The example above is copied straight out of the vanilla Minecraft which allows you to teleport around the world. Now, you might get confused since you see '''square brackets ([])''' and '''angle brackets (<>)''', those are the arguments. Any developer can implement their syntax just the way they want so don't base the following information on all plugins, though I (SupaHam) tend to make mine similar to how Minecraft and many Bukkit plugins do theirs. So with the '''tp''' command the square brackets are '''optional''' and the angle brackets are '''required'''. Usually between these brackets are a descriptive one/two words.

So, the tp command has the '''[target player]''' and the '''<destination player>''' argument for one of the usages. If you understood well then you should know that the [target player] is not required but the <destination player> is.

{{example|text=
'''A.''' SupaHam executes '''/tp Steve''' 
Minecraft then takes that 'Steve' argument and checks if it's valid 
'''Case: Steve is online''' 
* Minecraft checks if Steve is online on the same server as SupaHam. If Steve is online, SupaHam will get teleported to him.
'''Case: Steve is offline''' 
* Minecraft outputs an error to the command sender saying 'Steve' is not a valid player.

'''B.''' SupaHam executes '''/tp Steve SupaHam''' 

Notice the difference between command '''A''' and command '''B'''? Command B is making use of the optional argument ([target player]).
Minecraft then takes both 'Steve' and 'SupaHam' and check if they are both valid players, as shown with the cases above. If they are both valid Minecraft then teleports 'Steve' to 'SupaHam'.
}}

== Flags ==
A '''command flag''' is a '''hyphen (-)''' followed by a letter, these are optional. Command flags are pretty much options. '''Flags are not used with vanilla commands''' or many of the Bukkit plugins, though I make use of it when I feel it is necessary.
{{example|title=WorldEdit's brush cylinder command syntax |text=
'''/brush cyl [-h] <block> [radius] [height]''' 
In this example, the command creates a cylinder brush out of the item in your hand with a block, but if you look closely at the optional arguments, you will see there is one that starts with a hyphen, that is a flag. In this case the '''h''' flag makes your brush create hollow cylinders.
}}

As a developer, you might think "Wow, why waste so much time implementing such a complex system for my plugins?!", well here's some good news, there are frameworks already written for you to use! I personally prefer to use [http://wiki.sk89q.com/wiki/WorldEdit WorldEdit]'s command framework which can be found [https://github.com/sk89q/WorldEdit/tree/master/worldedit-core/src/main/java/com/sk89q/minecraft/util/commands here], though this requires your plugin to depend on WorldEdit, while most Minecraft servers use WorldEdit it's still not very nice to force your users to install something they don't want to install, but... there is a fork of WorldEdit's command framework by the [https://oc.tc/ Overcast Network] which can be found [https://github.com/OvercastNetwork/sk89q-command-framework here]. Unlike WorldEdit's version, you can easily ''shade'' this fork into your plugin, meaning you save up a lot of space and don't have to force your users to install WorldEdit.

MediaWiki:Common.css

2015-01-27T21:41:18Z

SupaHam: Undo revision 584 by SupaHam (talk)

/* Generic */

textarea, .wikiEditor-ui textarea#wpTextbox1 {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
border: 1px solid #aaa;
margin: 0;
padding: 4px;
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
line-height: 1.1;
}
input {
font: inherit;
font-size: 10pt;
margin: 0;
line-height: 1;
}
input[type='text'], input[type='password'], input:not([type]) {
font: inherit;
font-size: 10pt;
background: #fff;
padding: 4px;
border: 1px solid #aaa;
-webkit-transition: border-color .2s;
-moz-transition: border .2s;
-o-transition: border-color .2s;
transition: border-color .2s;
line-height: 1;
}
input[type='text']:hover, input[type='password']:hover, input#searchInput:hover {
border-color: #999;
}
input[type='text']:focus, input[type='password']:focus, input#searchInput:focus {
outline: 0;
border-color: #a7d7f9;
box-shadow: 0 0 0.3em #999;
}
button, input[type='button'], input[type='submit'] {
font: inherit;
display: inline-block;
-webkit-transition: border-color .2s;
-moz-transition: border .2s;
-o-transition: border-color .2s;
transition: border-color .2s;
background: #f3f3f3;
background: -moz-linear-gradient(linear, 0% 40%, 0% 70%, from(#F5F5F5), to(#F1F1F1));
background: -webkit-gradient(linear, 0% 40%, 0% 70%, from(#F5F5F5), to(#F1F1F1));
border: solid 1px #ccc;
border-radius: 2px;
margin: 0.3em 0;
padding: 6px 10px;
cursor: pointer;
font-size: 10pt;
line-height: 1;
}
button:hover, input[type='button']:hover, input[type='submit']:hover {
text-decoration: none;
border-color: #a7d7f9;
-moz-box-shadow: 0 2px 0 rgba(0, 0, 0, 0.3);
-webkit-box-shadow: 0 2px 5px rgba(0, 0, 0, 0.3);
box-shadow: 0 1px 2px rgba(0, 0, 0, 0.3);
}
pre {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
border: 1px solid #a7d7f9;
border-left: 0;
border-right: 0;
margin: 1em 2em;
background: #efef;
}
table pre, .wikiNote pre {
margin: 0.3em;
}
.metadata {
clear: both;
padding: 1em 2em;
}

/* Nice tables */

table.wikitable,
table.wiki-table {
margin: 1em -2px 1em -2px;
background: #fff;
border: 0;
border-collapse: separate;
empty-cells: show;
border-spacing: 1px;
border: 0;
border-radius: 0.3em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
}
table.wikitable th, table.wikitable td,
table.wiki-table th, table.wiki-table td {
border: 0;
border-bottom: 1px solid #ccc;
padding: 0.35em 0.5em;
}
table.wikitable th, table.wikitable td.hl1, table.wikitable th.hl1,
table.wiki-table th, table.wiki-table td.hl1, table.wikitable th.hl1 {
background: #f8f6eb;
padding: 0.35em 0.5em;
color: #000;
text-align: left;
border-radius: 0.3em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
text-shadow: none;
border: 1px solid #ccc;
box-shadow: 0 0.2em 0.2em rgba(0, 0, 0, 0.1);
position: relative;
}
table.wikitable td.hl2, table.wikitable th.hl2,
table.wiki-table td.hl2, table.wiki-table th.hl2 {
background: #fff;
color: #444;
text-align: center;
border: 1px solid #ccc;
border-top: 0;
}
table.wikitable td.hl3, table.wikitable th.hl3,
table.wiki-table td.hl3, table.wiki-table th.hl3 {
background: #ebf5f8;
color: #444;
text-align: center;
border: 1px solid #ccc;
border-top: 0;
}
table.wikitable caption,
table.wiki-table caption {
margin-left: inherit;
margin-right: inherit;
font-weight: bold;
}
table.wikitable td,
table.wiki-table td {
vertical-align: top;
}
table.wikitable td:nth-child(even), table.wiki-table td:nth-child(even) {
background: #f7f7f7;
}
table.wikitable tr:hover td, table.wiki-table tr:hover td {
background: #f5fafc;
-webkit-transition: all .1s;
-moz-transition: all .1s;
-o-transition: all .1s;
transition: all .1s;
}
table.wikitable tr:hover td:nth-child(even), table.wiki-table tr:hover td:nth-child(even) {
background: #eaf3f7;
}

/* Documentation blocks */

.wikiCmd {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
font-size: 95%;
display: inline-block;
margin: 0 2px;
padding: 0.01em 0.4em;
border: 1px dotted #CCC;
color: #333;
display: inline-block;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
}
.wikiNote .wikiCmd {
border: 0;
}
.wikiNote, .mw-editinginterface {
margin: 1.1em 1.5em;
padding: 0.7em 1.5em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
box-shadow: 0 0.3em 0.6em rgba(0, 0, 0, 0.1);
}
.wikiExample {
background: #ebf5f8;
border-color: #999;
}
.wikiWarning, .mw-editinginterface {
background: #ffffdf;
border-color: #dfb800;
}
.wikiTip {
background: #efefef;
border-color: #999999;
}

/* Button */

.buttons a, .buttons a:link, .buttons a:visited {
display: block;
margin: 15px 0 15px 0;
text-decoration: none;
color: #fff;
position: relative;
padding: 10px 20px;
padding-right: 45px;
background: #a50000;
border-radius: 5px;
box-shadow: inset 0px 1px 0px #ff838e, 0px 5px 0px 0px #581a27, 0px 7px 5px #999;
font-weight: bold;
font-size: 120%;
-moz-transition-property: background;
-moz-transition-duration: 0.5s;
-webkit-transition-property: background;
-webkit-transition-duration: 0.5s;
-o-transition-property: background;
-o-transition-duration: 0.5s;
border: 0;
max-width: 240px;
}
.buttons a:hover {
background: #d70014;
box-shadow: inset 0px 1px 0px #ff838e, 0px 5px 0px 0px #96000e, 0px 7px 5px #999;
}
.buttons a:active {
top: 3px;
background-image: linear-gradient(bottom, rgb(62,51,46) 100%, rgb(101,86,78) 0%);
box-shadow: inset 0px 1px 0px #ff838e, 0px 2px 0px 0px #612127, 0px 5px 3px #999;
}
.buttons a::before {
background-color: #7e1b24;
background-image: url(/images/button_arrow.png);
background-repeat: no-repeat;
background-position: center center;
content: "";
width: 20px;
height: 20px;
position: absolute;
right: 15px;
top: 50%;
margin-top: -9px;
border-radius: 50%;
box-shadow: inset 0px 1px 0px #19120f, 0px 1px 0px #827066;
}
.buttons a:active::before {
top: 50%;
margin-top: -12px;
box-shadow: inset 0px 1px 0px #ff838e, 0px 3px 0px #612127, 0px 6px 3px #34090d;
}
.buttons a img {
vertical-align: middle;
}

/* Vector skin adjustment */

div#content {
padding: 1.4em;
}
a:link {
color: #0004b2;
-webkit-transition: all .2s;
-moz-transition: all .2s;
-o-transition: all .2s;
transition: all .2s;
}
a:visited {
color: #363771;
}
a:hover {
color: #ac0000;
text-decoration: none;
border-bottom: 1px solid #999;
}
a.image:hover, #left-navigation a:hover, #right-navigation a:hover {
border: 0;
}
a.new:link, a.new:visited {
color: #dd0000;
}
h1, h1#firstHeading {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
font-size: 1.7em;
font-weight: normal;
border: 0;
}
h2 {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
font-size: 1.5em;
font-weight: bold;
margin: 1.6em 0 1em 0;
padding: 0 0 0.2em 0;
border-bottom: 1px solid #ccc;
color: #555;
}
h3 {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
margin: 1.1em 0 0.4em 0;
}
table.toc, table#toc {
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
margin: 2em 0 0 0;
padding: 1em;
border: 1px solid #ccc;
background: transparent;
white-space: nowrap;
}
table.toc h2 {
border: 0;
font-size: 1.3em;
}
.firstHeading img {
margin: 0 3px;
vertical-align: baseline;
}
.firstHeading small {
font-size: 100%;
color: #666;
}
#p-search {
margin-top: -5px;
}
#toolbar {
background: #ebf5f8;
padding: 0.8em;
-webkit-border-top-left-radius: 0.3em;
-webkit-border-top-right-radius: 0.3em;
-moz-border-radius-topleft: 0.3em;
-moz-border-radius-topright: 0.3em;
border-top-left-radius: 0.3em;
border-top-right-radius: 0.3em;
}
#editpage-copywarn {
margin: 1em 0;
background: #ebf5f8;
padding: 0.6em 1em;
font-size: 95%;
border-radius: 0.5em;
-moz-border-radius: 0.5em;
-webkit-border-radius: 0.5em;
}
.editOptions .editCheckboxes input {
margin: 0 0.01em 0 0.5em;
padding: 0;
}
.editOptions .editCheckboxes {
margin: 0.5em 0 0 0;
font-size: 90%;
float: right;
}
.editHelp {
display: none;
}
.templatesUsed {
margin-top: 5em;
}
.catlinks, #catlinks {
display: inline-block;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
margin: 10em 0 0 0;
padding: 0.6em;
border: 1px solid #ccc;
background: transparent;
}
#mw-normal-catlinks > a {
font-weight: bold;
color: #444;
}
.catlinks-allhidden, #catlinks.catlinks-allhidden, .catlinks.catlinks-allhidden {
display: none;
}
body.ns-3 dd {
border-left: 2px solid #a7d7f9;
padding: 0 0 0 1em;
margin-left: 2em;
}
body.ns-3 dl dl {
background: #fff;
margin-left: -1.5em;
}
body.ns-3 div > dl > dd {
margin-left: 1em;
}

/* Addons */

#fckTools {
background: #e4efff;
padding: 0.3em;
margin: 1em 0 0.5em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
float: right;
}

/* Specific to the wiki */

#localNotice {
background: #f8f6eb;
line-height: 1.6;
margin: 0 0 2em 0;
padding: 0.2em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
border: 1px solid #ccc;
box-shadow: 0 0.3em 0.6em rgba(0, 0, 0, 0.1);
}
#localNotice b {
color: #a50000;
}
#localNotice a:link, #localNotice a:visited {
background: transparent !important;
padding: 0 !important;
color: inherit !important;
border-bottom: 1px solid #ccc;
}
#localNotice a:hover {
color: #ac0000 !important;
border-bottom: 1px solid #999;
}
#content .visualClear {
clear: left !important;
}
#rightBar {
font-size: 0.8em;
}

div.mw-geshi {
padding: 1em;
margin: 1em 0;
border: 1px dashed #2f6fab;
background-color: #f9f9f9;
}

MediaWiki:Common.css

2015-01-27T21:40:46Z

SupaHam:

/* Generic */

textarea, .wikiEditor-ui textarea#wpTextbox1 {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
border: 1px solid #aaa;
margin: 0;
padding: 4px;
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
line-height: 1.1;
}
input {
font: inherit;
font-size: 10pt;
margin: 0;
line-height: 1;
}
input[type='text'], input[type='password'], input:not([type]) {
font: inherit;
font-size: 10pt;
background: #fff;
padding: 4px;
border: 1px solid #aaa;
-webkit-transition: border-color .2s;
-moz-transition: border .2s;
-o-transition: border-color .2s;
transition: border-color .2s;
line-height: 1;
}
input[type='text']:hover, input[type='password']:hover, input#searchInput:hover {
border-color: #999;
}
input[type='text']:focus, input[type='password']:focus, input#searchInput:focus {
outline: 0;
border-color: #a7d7f9;
box-shadow: 0 0 0.3em #999;
}
button, input[type='button'], input[type='submit'] {
font: inherit;
display: inline-block;
-webkit-transition: border-color .2s;
-moz-transition: border .2s;
-o-transition: border-color .2s;
transition: border-color .2s;
background: #f3f3f3;
background: -moz-linear-gradient(linear, 0% 40%, 0% 70%, from(#F5F5F5), to(#F1F1F1));
background: -webkit-gradient(linear, 0% 40%, 0% 70%, from(#F5F5F5), to(#F1F1F1));
border: solid 1px #ccc;
border-radius: 2px;
margin: 0.3em 0;
padding: 6px 10px;
cursor: pointer;
font-size: 10pt;
line-height: 1;
}
button:hover, input[type='button']:hover, input[type='submit']:hover {
text-decoration: none;
border-color: #a7d7f9;
-moz-box-shadow: 0 2px 0 rgba(0, 0, 0, 0.3);
-webkit-box-shadow: 0 2px 5px rgba(0, 0, 0, 0.3);
box-shadow: 0 1px 2px rgba(0, 0, 0, 0.3);
}
pre {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
border: 1px solid #a7d7f9;
border-left: 0;
border-right: 0;
margin: 1em 2em;
background: #efef;
}
table pre, .wikiNote pre {
margin: 0.3em;
}
.metadata {
clear: both;
padding: 1em 2em;
}

/* Nice tables */

table.wikitable,
table.wiki-table {
margin: 1em -2px 1em -2px;
background: #fff;
border: 0;
border-collapse: separate;
empty-cells: show;
border-spacing: 1px;
border: 0;
border-radius: 0.3em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
}
table.wikitable th, table.wikitable td,
table.wiki-table th, table.wiki-table td {
border: 0;
border-bottom: 1px solid #ccc;
padding: 0.35em 0.5em;
}
table.wikitable th, table.wikitable td.hl1, table.wikitable th.hl1,
table.wiki-table th, table.wiki-table td.hl1, table.wikitable th.hl1 {
background: #f8f6eb;
padding: 0.35em 0.5em;
color: #000;
text-align: left;
border-radius: 0.3em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
text-shadow: none;
border: 1px solid #ccc;
box-shadow: 0 0.2em 0.2em rgba(0, 0, 0, 0.1);
position: relative;
}
table.wikitable td.hl2, table.wikitable th.hl2,
table.wiki-table td.hl2, table.wiki-table th.hl2 {
background: #fff;
color: #444;
text-align: center;
border: 1px solid #ccc;
border-top: 0;
}
table.wikitable td.hl3, table.wikitable th.hl3,
table.wiki-table td.hl3, table.wiki-table th.hl3 {
background: #ebf5f8;
color: #444;
text-align: center;
border: 1px solid #ccc;
border-top: 0;
}
table.wikitable caption,
table.wiki-table caption {
margin-left: inherit;
margin-right: inherit;
font-weight: bold;
}
table.wikitable td,
table.wiki-table td {
vertical-align: top;
}
table.wikitable td:nth-child(even), table.wiki-table td:nth-child(even) {
background: #f7f7f7;
}
table.wikitable tr:hover td, table.wiki-table tr:hover td {
background: #ff;
-webkit-transition: all .1s;
-moz-transition: all .1s;
-o-transition: all .1s;
transition: all .1s;
}
table.wikitable tr:hover td:nth-child(even), table.wiki-table tr:hover td:nth-child(even) {
background: #eaf3f7;
}

/* Documentation blocks */

.wikiCmd {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
font-size: 95%;
display: inline-block;
margin: 0 2px;
padding: 0.01em 0.4em;
border: 1px dotted #CCC;
color: #333;
display: inline-block;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
}
.wikiNote .wikiCmd {
border: 0;
}
.wikiNote, .mw-editinginterface {
margin: 1.1em 1.5em;
padding: 0.7em 1.5em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
box-shadow: 0 0.3em 0.6em rgba(0, 0, 0, 0.1);
}
.wikiExample {
background: #ebf5f8;
border-color: #999;
}
.wikiWarning, .mw-editinginterface {
background: #ffffdf;
border-color: #dfb800;
}
.wikiTip {
background: #efefef;
border-color: #999999;
}

/* Button */

.buttons a, .buttons a:link, .buttons a:visited {
display: block;
margin: 15px 0 15px 0;
text-decoration: none;
color: #fff;
position: relative;
padding: 10px 20px;
padding-right: 45px;
background: #a50000;
border-radius: 5px;
box-shadow: inset 0px 1px 0px #ff838e, 0px 5px 0px 0px #581a27, 0px 7px 5px #999;
font-weight: bold;
font-size: 120%;
-moz-transition-property: background;
-moz-transition-duration: 0.5s;
-webkit-transition-property: background;
-webkit-transition-duration: 0.5s;
-o-transition-property: background;
-o-transition-duration: 0.5s;
border: 0;
max-width: 240px;
}
.buttons a:hover {
background: #d70014;
box-shadow: inset 0px 1px 0px #ff838e, 0px 5px 0px 0px #96000e, 0px 7px 5px #999;
}
.buttons a:active {
top: 3px;
background-image: linear-gradient(bottom, rgb(62,51,46) 100%, rgb(101,86,78) 0%);
box-shadow: inset 0px 1px 0px #ff838e, 0px 2px 0px 0px #612127, 0px 5px 3px #999;
}
.buttons a::before {
background-color: #7e1b24;
background-image: url(/images/button_arrow.png);
background-repeat: no-repeat;
background-position: center center;
content: "";
width: 20px;
height: 20px;
position: absolute;
right: 15px;
top: 50%;
margin-top: -9px;
border-radius: 50%;
box-shadow: inset 0px 1px 0px #19120f, 0px 1px 0px #827066;
}
.buttons a:active::before {
top: 50%;
margin-top: -12px;
box-shadow: inset 0px 1px 0px #ff838e, 0px 3px 0px #612127, 0px 6px 3px #34090d;
}
.buttons a img {
vertical-align: middle;
}

/* Vector skin adjustment */

div#content {
padding: 1.4em;
}
a:link {
color: #0004b2;
-webkit-transition: all .2s;
-moz-transition: all .2s;
-o-transition: all .2s;
transition: all .2s;
}
a:visited {
color: #363771;
}
a:hover {
color: #ac0000;
text-decoration: none;
border-bottom: 1px solid #999;
}
a.image:hover, #left-navigation a:hover, #right-navigation a:hover {
border: 0;
}
a.new:link, a.new:visited {
color: #dd0000;
}
h1, h1#firstHeading {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
font-size: 1.7em;
font-weight: normal;
border: 0;
}
h2 {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
font-size: 1.5em;
font-weight: bold;
margin: 1.6em 0 1em 0;
padding: 0 0 0.2em 0;
border-bottom: 1px solid #ccc;
color: #555;
}
h3 {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
margin: 1.1em 0 0.4em 0;
}
table.toc, table#toc {
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
margin: 2em 0 0 0;
padding: 1em;
border: 1px solid #ccc;
background: transparent;
white-space: nowrap;
}
table.toc h2 {
border: 0;
font-size: 1.3em;
}
.firstHeading img {
margin: 0 3px;
vertical-align: baseline;
}
.firstHeading small {
font-size: 100%;
color: #666;
}
#p-search {
margin-top: -5px;
}
#toolbar {
background: #ebf5f8;
padding: 0.8em;
-webkit-border-top-left-radius: 0.3em;
-webkit-border-top-right-radius: 0.3em;
-moz-border-radius-topleft: 0.3em;
-moz-border-radius-topright: 0.3em;
border-top-left-radius: 0.3em;
border-top-right-radius: 0.3em;
}
#editpage-copywarn {
margin: 1em 0;
background: #ebf5f8;
padding: 0.6em 1em;
font-size: 95%;
border-radius: 0.5em;
-moz-border-radius: 0.5em;
-webkit-border-radius: 0.5em;
}
.editOptions .editCheckboxes input {
margin: 0 0.01em 0 0.5em;
padding: 0;
}
.editOptions .editCheckboxes {
margin: 0.5em 0 0 0;
font-size: 90%;
float: right;
}
.editHelp {
display: none;
}
.templatesUsed {
margin-top: 5em;
}
.catlinks, #catlinks {
display: inline-block;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
margin: 10em 0 0 0;
padding: 0.6em;
border: 1px solid #ccc;
background: transparent;
}
#mw-normal-catlinks > a {
font-weight: bold;
color: #444;
}
.catlinks-allhidden, #catlinks.catlinks-allhidden, .catlinks.catlinks-allhidden {
display: none;
}
body.ns-3 dd {
border-left: 2px solid #a7d7f9;
padding: 0 0 0 1em;
margin-left: 2em;
}
body.ns-3 dl dl {
background: #fff;
margin-left: -1.5em;
}
body.ns-3 div > dl > dd {
margin-left: 1em;
}

/* Addons */

#fckTools {
background: #e4efff;
padding: 0.3em;
margin: 1em 0 0.5em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
float: right;
}

/* Specific to the wiki */

#localNotice {
background: #f8f6eb;
line-height: 1.6;
margin: 0 0 2em 0;
padding: 0.2em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
border: 1px solid #ccc;
box-shadow: 0 0.3em 0.6em rgba(0, 0, 0, 0.1);
}
#localNotice b {
color: #a50000;
}
#localNotice a:link, #localNotice a:visited {
background: transparent !important;
padding: 0 !important;
color: inherit !important;
border-bottom: 1px solid #ccc;
}
#localNotice a:hover {
color: #ac0000 !important;
border-bottom: 1px solid #999;
}
#content .visualClear {
clear: left !important;
}
#rightBar {
font-size: 0.8em;
}

div.mw-geshi {
padding: 1em;
margin: 1em 0;
border: 1px dashed #2f6fab;
background-color: #f9f9f9;
}

MediaWiki:Common.css

2015-01-27T21:39:37Z

SupaHam: Undo revision 582 by SupaHam (talk)

MediaWiki:Common.css

2015-01-27T21:38:31Z

SupaHam:

/* Generic */

textarea, .wikiEditor-ui textarea#wpTextbox1 {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
border: 1px solid #aaa;
margin: 0;
padding: 4px;
-webkit-box-sizing: border-box;
-moz-box-sizing: border-box;
box-sizing: border-box;
line-height: 1.1;
}
input {
font: inherit;
font-size: 10pt;
margin: 0;
line-height: 1;
}
input[type='text'], input[type='password'], input:not([type]) {
font: inherit;
font-size: 10pt;
background: #fff;
padding: 4px;
border: 1px solid #aaa;
-webkit-transition: border-color .2s;
-moz-transition: border .2s;
-o-transition: border-color .2s;
transition: border-color .2s;
line-height: 1;
}
input[type='text']:hover, input[type='password']:hover, input#searchInput:hover {
border-color: #999;
}
input[type='text']:focus, input[type='password']:focus, input#searchInput:focus {
outline: 0;
border-color: #a7d7f9;
box-shadow: 0 0 0.3em #999;
}
button, input[type='button'], input[type='submit'] {
font: inherit;
display: inline-block;
-webkit-transition: border-color .2s;
-moz-transition: border .2s;
-o-transition: border-color .2s;
transition: border-color .2s;
background: #f3f3f3;
background: -moz-linear-gradient(linear, 0% 40%, 0% 70%, from(#F5F5F5), to(#F1F1F1));
background: -webkit-gradient(linear, 0% 40%, 0% 70%, from(#F5F5F5), to(#F1F1F1));
border: solid 1px #ccc;
border-radius: 2px;
margin: 0.3em 0;
padding: 6px 10px;
cursor: pointer;
font-size: 10pt;
line-height: 1;
}
button:hover, input[type='button']:hover, input[type='submit']:hover {
text-decoration: none;
border-color: #a7d7f9;
-moz-box-shadow: 0 2px 0 rgba(0, 0, 0, 0.3);
-webkit-box-shadow: 0 2px 5px rgba(0, 0, 0, 0.3);
box-shadow: 0 1px 2px rgba(0, 0, 0, 0.3);
}
pre {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
border: 1px solid #a7d7f9;
border-left: 0;
border-right: 0;
margin: 1em 2em;
background: #efef;
}
table pre, .wikiNote pre {
margin: 0.3em;
}
.metadata {
clear: both;
padding: 1em 2em;
}

/* Nice tables */

table.wikitable,
table.wiki-table {
margin: 1em -2px 1em -2px;
background: #fff;
border: 0;
border-collapse: separate;
empty-cells: show;
border-spacing: 1px;
border: 0;
border-radius: 0.3em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
}
table.wikitable th, table.wikitable td,
table.wiki-table th, table.wiki-table td {
border: 0;
border-bottom: 1px solid #ccc;
padding: 0.35em 0.5em;
}
table.wikitable th, table.wikitable td.hl1, table.wikitable th.hl1,
table.wiki-table th, table.wiki-table td.hl1, table.wikitable th.hl1 {
background: #f8f6eb;
padding: 0.35em 0.5em;
color: #000;
text-align: left;
border-radius: 0.3em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
text-shadow: none;
border: 1px solid #ccc;
box-shadow: 0 0.2em 0.2em rgba(0, 0, 0, 0.1);
position: relative;
}
table.wikitable td.hl2, table.wikitable th.hl2,
table.wiki-table td.hl2, table.wiki-table th.hl2 {
background: #fff;
color: #444;
text-align: center;
border: 1px solid #ccc;
border-top: 0;
}
table.wikitable td.hl3, table.wikitable th.hl3,
table.wiki-table td.hl3, table.wiki-table th.hl3 {
background: #ebf5f8;
color: #444;
text-align: center;
border: 1px solid #ccc;
border-top: 0;
}
table.wikitable caption,
table.wiki-table caption {
margin-left: inherit;
margin-right: inherit;
font-weight: bold;
}
table.wikitable td,
table.wiki-table td {
vertical-align: top;
}
table.wikitable td:nth-child(even), table.wiki-table td:nth-child(even) {
background: #f7f7f7;
}
table.wikitable tr:hover td, table.wiki-table tr:hover td {
background: #f5fafc;
-webkit-transition: all .1s;
-moz-transition: all .1s;
-o-transition: all .1s;
transition: all .1s;
}
table.wikitable tr:hover td:nth-child(even), table.wiki-table tr:hover td:nth-child(even) {
background: #ff;
}

/* Documentation blocks */

.wikiCmd {
font-family: 'Consolas', 'DejaVu Sans', 'Lucida Console', monospace;
font-size: 95%;
display: inline-block;
margin: 0 2px;
padding: 0.01em 0.4em;
border: 1px dotted #CCC;
color: #333;
display: inline-block;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
}
.wikiNote .wikiCmd {
border: 0;
}
.wikiNote, .mw-editinginterface {
margin: 1.1em 1.5em;
padding: 0.7em 1.5em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
box-shadow: 0 0.3em 0.6em rgba(0, 0, 0, 0.1);
}
.wikiExample {
background: #ebf5f8;
border-color: #999;
}
.wikiWarning, .mw-editinginterface {
background: #ffffdf;
border-color: #dfb800;
}
.wikiTip {
background: #efefef;
border-color: #999999;
}

/* Button */

.buttons a, .buttons a:link, .buttons a:visited {
display: block;
margin: 15px 0 15px 0;
text-decoration: none;
color: #fff;
position: relative;
padding: 10px 20px;
padding-right: 45px;
background: #a50000;
border-radius: 5px;
box-shadow: inset 0px 1px 0px #ff838e, 0px 5px 0px 0px #581a27, 0px 7px 5px #999;
font-weight: bold;
font-size: 120%;
-moz-transition-property: background;
-moz-transition-duration: 0.5s;
-webkit-transition-property: background;
-webkit-transition-duration: 0.5s;
-o-transition-property: background;
-o-transition-duration: 0.5s;
border: 0;
max-width: 240px;
}
.buttons a:hover {
background: #d70014;
box-shadow: inset 0px 1px 0px #ff838e, 0px 5px 0px 0px #96000e, 0px 7px 5px #999;
}
.buttons a:active {
top: 3px;
background-image: linear-gradient(bottom, rgb(62,51,46) 100%, rgb(101,86,78) 0%);
box-shadow: inset 0px 1px 0px #ff838e, 0px 2px 0px 0px #612127, 0px 5px 3px #999;
}
.buttons a::before {
background-color: #7e1b24;
background-image: url(/images/button_arrow.png);
background-repeat: no-repeat;
background-position: center center;
content: "";
width: 20px;
height: 20px;
position: absolute;
right: 15px;
top: 50%;
margin-top: -9px;
border-radius: 50%;
box-shadow: inset 0px 1px 0px #19120f, 0px 1px 0px #827066;
}
.buttons a:active::before {
top: 50%;
margin-top: -12px;
box-shadow: inset 0px 1px 0px #ff838e, 0px 3px 0px #612127, 0px 6px 3px #34090d;
}
.buttons a img {
vertical-align: middle;
}

/* Vector skin adjustment */

div#content {
padding: 1.4em;
}
a:link {
color: #0004b2;
-webkit-transition: all .2s;
-moz-transition: all .2s;
-o-transition: all .2s;
transition: all .2s;
}
a:visited {
color: #363771;
}
a:hover {
color: #ac0000;
text-decoration: none;
border-bottom: 1px solid #999;
}
a.image:hover, #left-navigation a:hover, #right-navigation a:hover {
border: 0;
}
a.new:link, a.new:visited {
color: #dd0000;
}
h1, h1#firstHeading {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
font-size: 1.7em;
font-weight: normal;
border: 0;
}
h2 {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
font-size: 1.5em;
font-weight: bold;
margin: 1.6em 0 1em 0;
padding: 0 0 0.2em 0;
border-bottom: 1px solid #ccc;
color: #555;
}
h3 {
font-family: 'Trebuchet MS', Helvetica, Arial, sans-serif;
margin: 1.1em 0 0.4em 0;
}
table.toc, table#toc {
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
margin: 2em 0 0 0;
padding: 1em;
border: 1px solid #ccc;
background: transparent;
white-space: nowrap;
}
table.toc h2 {
border: 0;
font-size: 1.3em;
}
.firstHeading img {
margin: 0 3px;
vertical-align: baseline;
}
.firstHeading small {
font-size: 100%;
color: #666;
}
#p-search {
margin-top: -5px;
}
#toolbar {
background: #ebf5f8;
padding: 0.8em;
-webkit-border-top-left-radius: 0.3em;
-webkit-border-top-right-radius: 0.3em;
-moz-border-radius-topleft: 0.3em;
-moz-border-radius-topright: 0.3em;
border-top-left-radius: 0.3em;
border-top-right-radius: 0.3em;
}
#editpage-copywarn {
margin: 1em 0;
background: #ebf5f8;
padding: 0.6em 1em;
font-size: 95%;
border-radius: 0.5em;
-moz-border-radius: 0.5em;
-webkit-border-radius: 0.5em;
}
.editOptions .editCheckboxes input {
margin: 0 0.01em 0 0.5em;
padding: 0;
}
.editOptions .editCheckboxes {
margin: 0.5em 0 0 0;
font-size: 90%;
float: right;
}
.editHelp {
display: none;
}
.templatesUsed {
margin-top: 5em;
}
.catlinks, #catlinks {
display: inline-block;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
margin: 10em 0 0 0;
padding: 0.6em;
border: 1px solid #ccc;
background: transparent;
}
#mw-normal-catlinks > a {
font-weight: bold;
color: #444;
}
.catlinks-allhidden, #catlinks.catlinks-allhidden, .catlinks.catlinks-allhidden {
display: none;
}
body.ns-3 dd {
border-left: 2px solid #a7d7f9;
padding: 0 0 0 1em;
margin-left: 2em;
}
body.ns-3 dl dl {
background: #fff;
margin-left: -1.5em;
}
body.ns-3 div > dl > dd {
margin-left: 1em;
}

/* Addons */

#fckTools {
background: #e4efff;
padding: 0.3em;
margin: 1em 0 0.5em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
float: right;
}

/* Specific to the wiki */

#localNotice {
background: #f8f6eb;
line-height: 1.6;
margin: 0 0 2em 0;
padding: 0.2em;
-moz-border-radius: 0.3em;
-webkit-border-radius: 0.3em;
border-radius: 0.3em;
border: 1px solid #ccc;
box-shadow: 0 0.3em 0.6em rgba(0, 0, 0, 0.1);
}
#localNotice b {
color: #a50000;
}
#localNotice a:link, #localNotice a:visited {
background: transparent !important;
padding: 0 !important;
color: inherit !important;
border-bottom: 1px solid #ccc;
}
#localNotice a:hover {
color: #ac0000 !important;
border-bottom: 1px solid #999;
}
#content .visualClear {
clear: left !important;
}
#rightBar {
font-size: 0.8em;
}

div.mw-geshi {
padding: 1em;
margin: 1em 0;
border: 1px dashed #2f6fab;
background-color: #f9f9f9;
}

Configurations

2015-01-27T09:45:06Z

SupaHam: /* List */

=Format=

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

=Types=

==String==
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.
==General==

===List===
This type is a Collection, you can give it more than one '''single type'''. An example for usage of List would be player names that should be allowed to build in an area.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===Double===
This type is like an '''Integer''', but accepts decimals and can store 15 digits.

===Float===
This type is like '''Double''', but stores only 7 digits.

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

==Minecraft==
These are Minecraft related types.
===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'
enchants:
DAMAGE_ALL: 2
repair-cost: 1

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.
===Entity Type===
This type represents a Minecraft '''Entity Type''' through [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/EntityType.html#enum_constant_summary Bukkit's enum names]. These don't necessarily have to be UPPERCASE as the provided value will always be converted into uppercase letters.

Configurations

2015-01-27T09:44:39Z

SupaHam: Clarify that only a single Type may fit into a Collection.

=Format=

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

=Types=

==String==
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.
==General==

===List===
This type is a Collection, you can give it more than one single Type. An example for usage of List would be player names that should be allowed to build in an area.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===Double===
This type is like an '''Integer''', but accepts decimals and can store 15 digits.

===Float===
This type is like '''Double''', but stores only 7 digits.

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

==Minecraft==
These are Minecraft related types.
===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'
enchants:
DAMAGE_ALL: 2
repair-cost: 1

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.
===Entity Type===
This type represents a Minecraft '''Entity Type''' through [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/EntityType.html#enum_constant_summary Bukkit's enum names]. These don't necessarily have to be UPPERCASE as the provided value will always be converted into uppercase letters.

NPCs/Properties

2015-01-27T09:42:20Z

SupaHam: initial creation.

Configurations

2015-01-27T09:42:14Z

SupaHam: Added Entity Type as a type.

=Format=

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

=Types=

==String==
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.
==General==

===List===
This type is a Collection, you can give it more than one Type. An example for usage of List would be player names that should be allowed to build in an area.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===Double===
This type is like an '''Integer''', but accepts decimals and can store 15 digits.

===Float===
This type is like '''Double''', but stores only 7 digits.

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

==Minecraft==
These are Minecraft related types.
===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'
enchants:
DAMAGE_ALL: 2
repair-cost: 1

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.
===Entity Type===
This type represents a Minecraft '''Entity Type''' through [https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/EntityType.html#enum_constant_summary Bukkit's enum names]. These don't necessarily have to be UPPERCASE as the provided value will always be converted into uppercase letters.

Configurations

2015-01-27T09:02:08Z

SupaHam: Updated types headings and adding General and Minecraft sections.

=Format=

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

=Types=

==String==
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.
==General==

===List===
This type is a Collection, you can give it more than one Type. An example for usage of List would be player names that should be allowed to build in an area.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===Double===
This type is like an '''Integer''', but accepts decimals and can store 15 digits.

===Float===
This type is like '''Double''', but stores only 7 digits.

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

==Minecraft==
These are Minecraft related types.
===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'
enchants:
DAMAGE_ALL: 2
repair-cost: 1

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.

NPCs

2015-01-27T08:49:33Z

SupaHam: initial creation.

XChat

2015-01-17T16:40:54Z

SupaHam: /* config.yml */

XChat is a 1337 plugin for cross server communication, backend and front end.
==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}

=== config.yml ===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| server-id || [[Configurations#String|String]] || This is used to identify the server in various ways. If this is null (or unset) XChat will fallback to server.properties' server-name. If the server-name in ''server_properties'' is null, this server-id will be set to 'XChat'. If a server-id already actively exists, the id is appended with an integer that keeps incrementing until the server-id becomes unique.
|-
| databases || [[Configurations#Section|Section]] || This configuration section contains a list of databases that the instance of XChat should connect to and retrieve information from. Only '''MySQL''' and '''Redis''' are supported.
|-
| databases.mysql || [[Configurations#Section|Section]] || This configuration section contains the MySQL connection info.
|-
| databases.mysql.ip || [[Configurations#String|String]] || This is the ip address of the MySQL database to connect to.
|-
| databases.mysql.port || [[Configurations#Integer|Integer]] || This is the port of the MySQL database to connect to.
|-
| databases.mysql.user || [[Configurations#String|String]] || This is the username to use when connecting to the MySQL database.
|-
| databases.mysql.password || [[Configurations#String|String]] || This is the password to use when connecting to the MySQL database.
|-
| databases.redis || [[Configurations#Section|Section]] || This configuration section contains the Redis connection info.
|-
| databases.redis.ip || [[Configurations#String|String]] || This is the ip address of the Redis database to connect to.
|-
| databases.redis.port || [[Configurations#Integer|Integer]] || This is the port of the Redis database to connect to.
|}

XChat

2015-01-16T00:07:04Z

SupaHam: Added configuration section with config.yml.

XChat is a 1337 plugin for cross server communication, backend and front end.
==config.yml==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}

=== config.yml ===
{| class="wiki-table"
! Configuration
! width="100"| Value
! Description
|-
| server-id || [[Configurations#String|String]] || This is used to identify the server in various ways. If this is null (or unset) XChat will fallback to server.properties' server-name. If the server-name in ''server_properties'' is null, this server-id will be set to 'XChat'. If a server-id already actively exists, the id is appended with an integer that keeps incrementing until the server-id becomes unique.
|-
| databases || [[Configurations#Section|Section]] || This configuration section contains a list of databases that the instance of XChat should connect to and retrieve information from. Only '''MySQL''' and '''Redis''' are supported.
|-
| databases.mysql || [[Configurations#Section|Section]] || This configuration section contains the MySQL connection info.
|-
| databases.mysql.ip || [[Configurations#String|String]] || This is the ip address of the MySQL database to connect to.
|-
| databases.mysql.port || [[Configurations#Integer|Integer]] || This is the port of the MySQL database to connect to.
|-
| databases.mysql.user || [[Configurations#String|String]] || This is the username to use when connecting to the MySQL database.
|-
| databases.mysql.password || [[Configurations#String|String]] || This is the password to use when connecting to the MySQL database.
|-
| databases.redis || [[Configurations#Section|Section]] || This configuration section contains the Redis connection info.
|-
| databases.redis.ip || [[Configurations#String|String]] || This is the ip address of the Redis database to connect to.
|-
| databases.redis.port || [[Configurations#Integer|Integer]] || This is the port of the Redis database to connect to.
|}

XChat

2015-01-15T22:53:48Z

SupaHam: initial creation.

XChat is a 1337 plugin for cross server communication, backend and front end.

Configurations

2014-05-20T12:54:20Z

SupaHam: Added enchants and repair-cost to serialized example.

==Format==

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

==Types==

===String===
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.

===List===
This type is basically a Collection, you can give it more than one Type. An example for usage of List would be player names that should be allowed to build in an area.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===Double===
This type is like an '''Integer''', but accepts decimals and can store 15 digits.

===Float===
This type is like '''Double''', but stores only 7 digits.

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'
enchants:
DAMAGE_ALL: 2
repair-cost: 1

MassDrugs

2014-05-19T02:14:24Z

SupaHam: Made types link to their respective urls.

=MassDrugs=
MassDrugs is a plugin created by SupaHam, for the [http://www.MassMC.net MassMC server]. This plugin introduces completely configurable drugs, with overdose effects, etc.
==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || massdrugs || massdrugs || drugs || MassDrugs main command.
|-
| massdrugs || add || massdrugs.add || || Adds a drug's property value.
|-
| massdrugs || set || massdrugs.set || || Set drug properties.
|-
| massdrugs || remove || massdrugs.remove || rm || Removes a drug's property value.
|-
| massdrugs || create <drug> || massdrugs.create || c || Creates a new drug. HEISENBERG! The item in your hand will be the drug. The '''<drug>''' argument is the name of the drug you're creating. Note that this name can not change once set, though drugs can have display names, which is used for display.
|-
| massdrugs || delete <drug> || massdrugs.delete || del || Deletes a drug. The '''<drug>''' argument is the name of the drug you're deleting.
|-
| massdrugs || save || massdrugs.save || || Puts the drugs in the bag (Saves the drugs to the configuration file).
|-
| massdrugs || reload || massdrugs.reload || rl || Reloads the drugs configuration file.
|-
| massdrugs || give <drug> [player] [amount] || massdrugs.give || gib || Gives a player drugs. The '''<drug>''' argument is the name of the drug you're going to give. The '''[player]''' argument is the player you wish to give the drugs to. The '''[amount]''' argument is the amount of drugs to give.
|-
| massdrugs || list || massdrugs.list || ls || Lists all the drugs.
|-
|
|-
| massdrugs set || name <drug> <name> || massdrugs.set.name || || Set a drug's display name. The '''<drug>''' argument is the name of the drug you're modifying. The '''<name>''' argument is the display name you wish to set the '''<drug>''' to.
|-
| massdrugs set || summary <drug> <summary> || massdrugs.set.summary || || Set a drug's summary. The '''<drug>''' argument is the name of the drug you're modifying. The '''<summary>''' argument is the summary you wish to apply to '''<drug>'''.
|-
| massdrugs set || description <drug> <description> || massdrugs.set.description || desc || Set a drug's description. The '''<drug>''' argument is the name of the drug you're modifying. The '''<description>''' argument is the description you wish to apply to '''<drug>'''.
|-
| massdrugs set || message <drug> <message> || massdrugs.set.message || msg || Set a drug's message. The '''<drug>''' argument is the name of the drug you're modifying. The '''<message>''' argument is the message (sent to the consumer) you wish to apply to '''<drug>'''.
|-
| massdrugs set || item || massdrugs.set.item || || Set a drug's item to the item in your hand. The '''<drug>''' argument is the name of the drug you're modifying.
|-
| massdrugs set || use-threshold <drug> <threshold> || massdrugs.set.use-threshold || threshold || Set a drug's use threshold. The '''<drug>''' argument is the name of the drug you're modifying. The '''<use-threshold>''' argument is the use threshold, the uses before a player overdoses.
|-
| massdrugs set || use-reset-time <drug> <time> || massdrugs.set.use-reset-time || reset-time, time || Set a drug's use reset time. The '''<drug>''' argument is the name of the drug you're modifying. The '''<time>''' argument is the time (in seconds) a player's drug use decrements.
|-
| massdrugs set || overdose-percentage <drug> <percentage> || massdrugs.set.overdose-percentage || odpct || Set a drug's overdose percentage. The '''<drug>''' argument is the name of the drug you're modifying. The '''<percentage>''' argument is the chance (from 100%) that a player will overdose once they passed the use-threshold.
|-
|
|-
| massdrugs add || effect [-o] <drug> <type> <duration> <amplifier> [ambient] || massdrugs.add.effect || || Adds a potion effect. The '''<drug>''' argument is the name of the drug you're modifying. The '''<type>''' argument is the type of the potion effect you wish to apply to '''<drug>''', click here for a list of potion effect types. The '''<duration>''' argument is the duration (in minecraft ticks) that the effect will last. The '''<amplifier>''' argument is the level of the potion effect starting from 0 (level 1). The '''[ambient]''' argument is whether the effect should be ambient (barely visible). If the '''[-o]''' flag is present, the change will apply to the overdose effect instead of the normal drug use effect.
|-
|
|-
| massdrugs remove || effect [-o] <drug> <type> || massdrugs.remove.effect || || Removes a potion effect. The '''<drug>''' argument is the name of the drug you're modifying. The '''<type>''' argument is the type of the potion effect you wish to remove from '''<drug>''', click here for a list of potion effect types. If the '''[-o]''' flag is present, the change will apply to the overdose effect instead of the normal drug use effect.
|}
==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}

=== drugs.yml ===
{| class="wiki-table"
! width="240"| Configuration
! width="100"| Value
! Description
|-
| drugs || Section || This section contains all the drugs that the plugin recognises.
|-
| drugs.<drug> || Section || This section represents a single drug's configuration. '''It is very important that you do not modify the <drug> name.'''
|-
| drugs.<drug>.name || [[Configurations#String|String]] || The name of the <drug>. '''It is very important that you do not modify this.''' This and '''<drug>''' are used to identify the drug and should be hidden from the gameplay aspect.
|-
| drugs.<drug>.display-name || [[Configurations#String|String]] || The display name of the <drug>. The display name is what is used in messages. (Supports colors).
|-
| drugs.<drug>.summary || [[Configurations#String|String]] || A summary of the <drug>. (Supports colors).
|-
| drugs.<drug>.description || [[Configurations#String|String]] || A description of the <drug>. (Supports colors).
|-
| drugs.<drug>.message || [[Configurations#String|String]] || The message that is sent to the player that consumes the <drug>. (Supports colors).
|-
| drugs.<drug>.use-threshold || [[Configurations#Integer|Integer]] || The use threshold before a player overdoses of the <drug>.
|-
| drugs.<drug>.use-reset-time || [[Configurations#Integer|Integer]] || The use-reset time of the <drug>.
|-
| drugs.<drug>.overdose-percentage || [[Configurations#Float|Float]] || The chance of the consumer overdosing once they've passed their use threshold.
|-
| drugs.<drug>.drug-effects || [[Configurations#PotionEffect|Potion Effect]] || The drug effects to be applied to the consumer.
|-
| drugs.<drug>.overdose-effects || [[Configurations#PotionEffect|Potion Effect]] || The overdose effects to be applied to the consumer, if they overdose.
|-
| drugs.<drug>.item || [[Configurations#ItemStack|ItemStack]] || The item this drug represents. This is the item that is needed to be interacted with in order to consume the drug. It is extremely important that you do not modify the lore from '==START HIDDEN LORE==' to '==END HIDDEN LORE'. This is used in order for the plugin to keep track of the item, and is done like this for efficiency.
|}

Configurations

2014-05-19T02:11:50Z

SupaHam: Added Float and modified Double.

Configurations

2014-05-19T01:05:37Z

SupaHam: Added serialized example.

==Format==

Copied from: http://wiki.sk89q.com/wiki/WorldEdit/Configuration/Bukkit

The file is written in the YAML format and you must follow these guidelines:

* '''Do not use tabs.''' You MUST use spaces or Bukkit will complain. If you use an editor like Notepad++ (recommended for Windows users), you must configure it to "replace tabs with spaces." In Notepad++, this can be changed in Settings > Preferences > Language Menu.
* Don't get rid of the indents. They are indented so some entries are in categories (like "max-blocks-changed" is in the "limits" category.
* If you want to check the format of this file before putting it into WorldEdit, paste it into http://yaml-online-parser.appspot.com/ and see if it gives "ERROR:".
* Lines starting with # are comments and so they are ignored.

==Types==

===String===
This can be set to any arbitrary text.

Some strings support colour formatting. The following colour codes are:

{| class="wikitable"
|-
! Color code
! Color on white
! Color on black
|-
| &0
| style="background-color: white;" | black
| style="background-color: black;" | black
|-
| &1
| style="background-color: white;" | dark blue
| style="background-color: black;" | dark blue
|-
| &2
| style="background-color: white;" | dark green
| style="background-color: black;" | dark green
|-
| &3
| style="background-color: white;" | dark cyan/aqua
| style="background-color: black;" | dark cyan/aqua
|-
| &4
| style="background-color: white;" | dark red
| style="background-color: black;" | dark red
|-
| &5
| style="background-color: white;" | dark purple
| style="background-color: black;" | dark purple
|-
| &6
| style="background-color: white;" | dark yellow (gold)
| style="background-color: black;" | dark yellow (gold)
|-
| &7
| style="background-color: white;" | light grey
| style="background-color: black;" | light grey
|-
| &8
| style="background-color: white;" | dark grey
| style="background-color: black;" | dark grey
|-
| &9
| style="background-color: white;" | blue
| style="background-color: black;" | blue
|-
| &a
| style="background-color: white;" | green
| style="background-color: black;" | green
|-
| &b
| style="background-color: white;" | cyan/aqua
| style="background-color: black;" | cyan/aqua
|-
| &c
| style="background-color: white;" | red
| style="background-color: black;" | red
|-
| &d
| style="background-color: white;" | purple/pink
| style="background-color: black;" | purple/pink
|-
| &e
| style="background-color: white;" | yellow
| style="background-color: black;" | yellow
|-
| &f
| style="background-color: white;" | white
| style="background-color: black;" | white
|}

In addition, &k, &l, &m, &n, &o, and &r are 'obfuscated/magic', bold, strikethrough, underline, italic, and reset, respectively.

===List===
This type is basically a Collection, you can give it more than one Type. An example for usage of List would be player names that should be allowed to build in an area.

===Integer===
This type can be any '''whole''' number, negative or positive, that does not have a fraction or decimal portion.

===Double===
This type is like an '''Integer''', but accepts decimals.

===Boolean===
This type can be either 0 or 1, true or false, yes or no, etc. This type is used to toggle states.

===Location===
This type represents a '''Location''' that consists of an x, y, z coordinate and if necessary, direction too.

===String Location===
This type represents a '''Location''' converted into a '''String'''. It consists of an x, y, and z coordinate. An example of a '''String Location''' would be "10,64,30" which when parsed would create a location with the x as 10, y as 64, and z as 30.

===ItemStack===
This type represents an '''ItemStack''' that stores all properties of an item.
Data may chance depending on the item that is being serialized (stored). Here is a list of properties that can be stored with all items. The == represents the class that serialized the Object, in other words, the code that represents a Minecraft (Bukkit) Item. The '''meta-type''' is the type of metadata that belongs to the ItemStack. UNSPECIFIC represents a normal item, whereas something like LEATHER_ARMOR represents a leather armor item that contains details about its colour.
{| class="wiki-table"
! meta-type
! Special properties
|-
| '''BOOK''' || Contains '''title''', '''author''', '''pages'''
|-
| '''SKULL''' || Contains '''skull-owner'''
|-
| '''LEATHER_ARMOR''' || Contains '''color'''
|-
| '''MAP''' || Contains '''scaling'''
|-
| '''POTION''' || Contains '''amplifier''', '''ambient''', '''duration''', '''custom-effects''', '''potion-id'''
|-
| '''ENCHANTED''' || Contains '''stored-enchants'''
|-
| '''FIREWORK''' || Contains '''Fireworks''', '''power''', '''firework-effects''', '''Colors''', '''Type''', '''Trail''', '''Flicker''', '''FadeColors'''
|-
| '''FIREWORK_EFFECT''' || Contains '''firework-effect'''
|-
| '''UNSPECIFIC''' || Contains '''display-name''', '''lore''', '''enchants''', '''repair-cost'''
|-
|}
item:
==: org.bukkit.inventory.ItemStack
type: STONE
meta:
==: ItemMeta
meta-type: UNSPECIFIC
display-name: '§2Best stone in the whole world'
lore:
- '§e§lWithout this stone, mankind would not exist.'
- '§eThis stone was discovered by professor SupaHam.'

MassDrugs

2014-05-19T00:37:10Z

SupaHam: Added note for color support

=MassDrugs=
MassDrugs is a plugin created by SupaHam, for the [http://www.MassMC.net MassMC server]. This plugin introduces completely configurable drugs, with overdose effects, etc.
==Commands==
{{tip|text=Confused with command syntax or want to make the most out of them? Head over [[Commands|here]] for help.}}
{| class="wiki-table"
! width="150"| Parent
! width="200"| Command
! width="200"| Permission
! width="100"| Aliases
! Description
|-
| || massdrugs || massdrugs || drugs || MassDrugs main command.
|-
| massdrugs || add || massdrugs.add || || Adds a drug's property value.
|-
| massdrugs || set || massdrugs.set || || Set drug properties.
|-
| massdrugs || remove || massdrugs.remove || rm || Removes a drug's property value.
|-
| massdrugs || create <drug> || massdrugs.create || c || Creates a new drug. HEISENBERG! The item in your hand will be the drug. The '''<drug>''' argument is the name of the drug you're creating. Note that this name can not change once set, though drugs can have display names, which is used for display.
|-
| massdrugs || delete <drug> || massdrugs.delete || del || Deletes a drug. The '''<drug>''' argument is the name of the drug you're deleting.
|-
| massdrugs || save || massdrugs.save || || Puts the drugs in the bag (Saves the drugs to the configuration file).
|-
| massdrugs || reload || massdrugs.reload || rl || Reloads the drugs configuration file.
|-
| massdrugs || give <drug> [player] [amount] || massdrugs.give || gib || Gives a player drugs. The '''<drug>''' argument is the name of the drug you're going to give. The '''[player]''' argument is the player you wish to give the drugs to. The '''[amount]''' argument is the amount of drugs to give.
|-
| massdrugs || list || massdrugs.list || ls || Lists all the drugs.
|-
|
|-
| massdrugs set || name <drug> <name> || massdrugs.set.name || || Set a drug's display name. The '''<drug>''' argument is the name of the drug you're modifying. The '''<name>''' argument is the display name you wish to set the '''<drug>''' to.
|-
| massdrugs set || summary <drug> <summary> || massdrugs.set.summary || || Set a drug's summary. The '''<drug>''' argument is the name of the drug you're modifying. The '''<summary>''' argument is the summary you wish to apply to '''<drug>'''.
|-
| massdrugs set || description <drug> <description> || massdrugs.set.description || desc || Set a drug's description. The '''<drug>''' argument is the name of the drug you're modifying. The '''<description>''' argument is the description you wish to apply to '''<drug>'''.
|-
| massdrugs set || message <drug> <message> || massdrugs.set.message || msg || Set a drug's message. The '''<drug>''' argument is the name of the drug you're modifying. The '''<message>''' argument is the message (sent to the consumer) you wish to apply to '''<drug>'''.
|-
| massdrugs set || item || massdrugs.set.item || || Set a drug's item to the item in your hand. The '''<drug>''' argument is the name of the drug you're modifying.
|-
| massdrugs set || use-threshold <drug> <threshold> || massdrugs.set.use-threshold || threshold || Set a drug's use threshold. The '''<drug>''' argument is the name of the drug you're modifying. The '''<use-threshold>''' argument is the use threshold, the uses before a player overdoses.
|-
| massdrugs set || use-reset-time <drug> <time> || massdrugs.set.use-reset-time || reset-time, time || Set a drug's use reset time. The '''<drug>''' argument is the name of the drug you're modifying. The '''<time>''' argument is the time (in seconds) a player's drug use decrements.
|-
| massdrugs set || overdose-percentage <drug> <percentage> || massdrugs.set.overdose-percentage || odpct || Set a drug's overdose percentage. The '''<drug>''' argument is the name of the drug you're modifying. The '''<percentage>''' argument is the chance (from 100%) that a player will overdose once they passed the use-threshold.
|-
|
|-
| massdrugs add || effect [-o] <drug> <type> <duration> <amplifier> [ambient] || massdrugs.add.effect || || Adds a potion effect. The '''<drug>''' argument is the name of the drug you're modifying. The '''<type>''' argument is the type of the potion effect you wish to apply to '''<drug>''', click here for a list of potion effect types. The '''<duration>''' argument is the duration (in minecraft ticks) that the effect will last. The '''<amplifier>''' argument is the level of the potion effect starting from 0 (level 1). The '''[ambient]''' argument is whether the effect should be ambient (barely visible). If the '''[-o]''' flag is present, the change will apply to the overdose effect instead of the normal drug use effect.
|-
|
|-
| massdrugs remove || effect [-o] <drug> <type> || massdrugs.remove.effect || || Removes a potion effect. The '''<drug>''' argument is the name of the drug you're modifying. The '''<type>''' argument is the type of the potion effect you wish to remove from '''<drug>''', click here for a list of potion effect types. If the '''[-o]''' flag is present, the change will apply to the overdose effect instead of the normal drug use effect.
|}
==Configuration==
{{tip|text=Before starting to mess around with a configuration file, please head over [[Configurations|here]] and familiarise yourself.}}

=== drugs.yml ===
{| class="wiki-table"
! width="240"| Configuration
! width="100"| Value
! Description
|-
| drugs || Section || This section contains all the drugs that the plugin recognises.
|-
| drugs.<drug> || Section || This section represents a single drug's configuration. '''It is very important that you do not modify the <drug> name.'''
|-
| drugs.<drug>.name || String || The name of the <drug>. '''It is very important that you do not modify this.''' This and '''<drug>''' are used to identify the drug and should be hidden from the gameplay aspect.
|-
| drugs.<drug>.display-name || String || The display name of the <drug>. The display name is what is used in messages. (Supports colors).
|-
| drugs.<drug>.summary || String || A summary of the <drug>. (Supports colors).
|-
| drugs.<drug>.description || String || A description of the <drug>. (Supports colors).
|-
| drugs.<drug>.message || String || The message that is sent to the player that consumes the <drug>. (Supports colors).
|-
| drugs.<drug>.use-threshold || Integer || The use threshold before a player overdoses of the <drug>.
|-
| drugs.<drug>.use-reset-time || Integer || The use-reset time of the <drug>.
|-
| drugs.<drug>.overdose-percentage || Float || The chance of the consumer overdosing once they've passed their use threshold.
|-
| drugs.<drug>.drug-effects || Potion Effect || The drug effects to be applied to the consumer.
|-
| drugs.<drug>.overdose-effects || Potion Effect || The overdose effects to be applied to the consumer, if they overdose.
|-
| drugs.<drug>.item || ItemStack || The item this drug represents. This is the item that is needed to be interacted with in order to consume the drug. It is extremely important that you do not modify the lore from '==START HIDDEN LORE==' to '==END HIDDEN LORE'. This is used in order for the plugin to keep track of the item, and is done like this for efficiency.
|}