SupaHam - New pages [en]

MCBall

2015-03-24T20:35:42Z

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-06T02:09:11Z

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>
}}

NPCs/Properties

2015-01-27T09:42:20Z

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

2015-01-27T08:49:33Z

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.
|}

XChat

2015-01-15T22:53:48Z

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.
|}