Find commonly used commands here
Arguments in "[" and "]" are optional. Arguments in "<" and ">" are required for the command to work!
This is nowhere near a complete list of commands, just some of the basics!
See who is online
Check your platime stats
Check your ping time in ms!
Hat yourself with the block you gave! Only works in creative worlds!
Request to teleport to the specified player. Said player will have to then accept the teleport request for it to complete.
Request to teleport the specified player to you. Said player will have to then accept the teleport request for it to complete.
Use this after someone has requested a teleport to you to accept and bring them to your position.
Return to the last location before your last teleport.
Warps you to the warp with the given name
Shows all the warps of the given category
Private message a user.
Shortcut command to reply to private messages.
Send an action message.
Express your feelings to the target.
Some feelings are gated behind certain ranks:
Senior+: Slap, bite, punch, scorn, stalk
Elder+: Lick, Stab, Kiss, Murder, Yell
Staff+: Has access to all feelings (Spook is the only staff restricted feeling currently)
This list might be out of date. Check
/feelings for an up to date list of all feelings.
YC allows limited forms of nicknames for community members. There is no command you can run to set one. Instead, you need to contact a staff member who will then take it up with the rest of the staff body. If we find that your request is in good faith, and you aren’t continually requesting a new nickname, we might grant it to you.
Check the real name of a player.
Creates a public protection. Anyone can use a Public protection, but no one can protect it.
Password-protect a block. Each time you login you need to enter the password to access it. (If someone else knows the password, they can access it too.)
Create a private protection. Private means private: you can also allow other users or groups to access the block as well. This is done by adding them after “private”. You can add more than one group and/or user per command. When you prefix a User or Group with an ‘@’, this User/Group will be able to modify the block and add other users. They cannot disable the owner from modifying it.
Modify an existing protection, adding or removing users and/or groups. See /lwc create, the example for private protections. The same syntax is used for this command. There’s an additional prefix however. Writing a ‘-’ infront of a User or Group removes the access from the block.
Unlock a password-protected block.
Punch a protection to view information on it.
View the amount of protections you are allowed.
Persistent mode will let you perform your last command on multiple blocks, untill you turn it off.
Select: Select the chest drops go to. On: Enable droptransfers. Off: Disable droptransfers. Status: Display the status of the droptransfers.
So finally we have HomeSweetHome 2.0 (technically 2.2) on the server. So, what’s special about this version of HSH, how do you use it, what cool features does it have, and so on. First off, for the most part, if you’re used to the old HSH, then not much (if any) has changed in how you use the old features. If you only care about that, then everything will continue to work like it always has. For those that want to see what’s new, and for those that don’t know how to use HSH, read on.
First off, let’s go over the basics, like how to set a home, and then teleport to that home, delete it, and see the list of all, homes, in addition to going over the interface.
Use this command to set some home at your current location with
homeName as it’s name. Note that
homeName can have spaces in it. For this reason, the home name for commands is ALWAYS the last argument. If you already have a home named
homeName, then it will move that home to your new location.
Use this command to actually go to your home. You can autocomplete by using tab. If you do not specify a home, it will bring up the home interface (
Use this command to delete a home. Note that this is not reversible.
Use this command to view your current homes. Here is however one of the major things that separate HSH 2.x from both other home plugins and HSH 1.x. While you would expect to just see your homes when you use that, and that is true, but you also get a lot more information and buttons. Buttons in HSH are things that you can click on and that suggests commands to you.
The first line here tells you how many homes you can have in total, you can also get this information from the
/home limit command. On the next line is a button create a new home. You just have to replace
<homeName> with the desired name.
Next are the home list itself, in addition to buttons for teleporting to the home, moving it, inviting someone to it (more on invites later), bringing up residents interface (more on residents later), and finally a button to delete the home.
If there is something you don’t quite remember how to do, you can most likely use the home interface to do it.
HSH also features invites and requests. Invites is something that the home owner can send to other players, so that they get a one time ticket to that home for a limited amount of time. Requests are the opposite. They allow a normal player to ask to be allowed to go to another player’s home. Note that tab complete does not work for these commands (that would allow you to see another persons homes, even though they might not want that). Both invites (unless you are a resident, more bellow) and requests can only be used when the home owner is online.
Use this to invite another player to your home. Once they use the invite, they need to get a new one before they can go to the home again.
This command has two specific meanings, depending on if you have been invited to that home or not.
If you already have been invited to that home, you will teleport to that home, and the invite will be used up.
If you have not been invited to the home before, you instead send a request to the player for that specific home. You then have to wait for the request to be accepted. You can only have one request for each player (Meaning that if you did
/home goto Clownpiece_ HakureiNew, followed by
/home goto Clownpiece_ HumanNew, the request for
HakureiNew would no longer be valid).
If you have received a request from a player, you can use this to accept the request. Once you do they will be teleported to the home.
Both invites and requests are a one time thing. They can’t be reused. What if you have a home that has multiple people living in it? Residents solve this problem, they are like a permanent invite to a home that can also be used when the home owner is offline. For the players that are residents of the home, they use the goto command just like as if it was another invite.
Residents also have a seperate interface similar to the home interface. If you do not specify a home name, you get a overview of all of your homes and their residents.
If you specify a home, you get a list off all the residents in that home, in addition to buttons to manipulate this info.
Add a player as a resident to a home
Remove a player as a resident from a home