Page 1 of 1

teleport function - new ideas

PostPosted: Thu Feb 09, 2012 19:33
by Michael Eh?
So far, those who have teleport priv has only this option

/teleport {x,z,y}

Ideas which I've seen used on MUCKs and MUDs (text based dungeons and communities)'

/teleport sethome - set your current location as 'home'

/teleport home - if not 'sethome' default is a respawn point.

/teleport last - teleport to last teleport also could be default of just typing /teleport

/teleport return - return to place last teleported 'from'

more advance ideas...

/teleport {name} - teleport to a 'named' teleport location. Nice for setting up communities or locals

/teleport {name} {x,z,y} - create or set a 'named' location

/teleport {name} delete - remove teleport destination

/teleport list - list the named destinations

/teleport {username} - teleport to username's location.

Possible Abuses:
============

Griefers could use /teleport home, /teleport return as a means of quickly jumping to location or home then jump back grabbing spoils without users noticing. Also /teleport {username} could be abused this way. Possible ways to counter this is to add time delay before next teleport or health penalties.

The list of /teleport destinations could end up being fairly long if user created. Having the same destination only a few blocks away. On MUDs, setting /teleport destinations are an admin function and they have to be requested.

The other real problem to 'named' destinations is safety. A 'griefer' could dig out a named teleport location causing a user without 'free_move' or fly set and that user would fall and be injured or die.

Possible Benifits:
============
This could also OPEN UP the map to building away from main area, (0,0,0) to develop elsewhere. It would encourage builders to work together to setup areas together. Setting up new towns centers with some development of mines or attractions. The admin could using creative mode setup a teleport pad using white cloud (which is indistructable by users) at the 'named' destination to prevent vandalism of the teleport coordinates.

/teleport {username} could be helpful to invite users community builds. Debate practicallity of this over someone just giving their coordinates or setting up a clumsy permission prompt.

Implimentation:
===========
There is already a 'sethome' 'home' mod so reworking that into teleport code is easily done. 'Home' value can be set along username, password. Destinations would be another thing. It would have to be an admin function storing destination name and coordinates. 'last' and 'return' would have to require storing these values as user varibles like last or current position. These values would be removed or re-initialized when logged off or relogging on. Error catching to 'home not set' or 'unable to return to last destination' or 'destination not valid'.

What do you folks think?

PostPosted: Fri Feb 10, 2012 00:42
by randomproof
You could give players the option if they wanted "/teleport {username}" to work for them. Say, something like this: "/teleport {my username} on/off" You would just need a way to save the settings between server loading, or have it default to off and players that wanted it on would have to turn it on every time they log on to the server.

I also think the functions relating to home should also set the re-spawn location.

PostPosted: Fri Mar 02, 2012 03:36
by Death Dealer
i think if our going to go that far with it ,wait til someone can make a ui for it.

PostPosted: Thu Mar 22, 2012 17:57
by daniel
You said that you could have both of these

/teleport {name}

/teleport {username}

but what would happen if your named location had the same name as another persons username? where would it go to?

PostPosted: Thu Mar 22, 2012 19:23
by sfan5
maybe change that to:
/teleport location [name]
/teleport player [name]

PostPosted: Fri Mar 23, 2012 09:05
by Calinou
My ideas about command names:
/teleport player1 - teleports you to player1, requires "teleport-self-to-player" permission
/teleport player1 player2 - teleports player1 to player 2, requires "teleport-player-to-player" permission
/teleport X,Y,Z - coordinate teleport, requires "teleport-to-coordinates" permission
/warp set name - sets warp name, requires "warp-set" permission
/warp name - teleports you to warp name, requires "warp-goto" permission
/warp delete name - delets warp name, requires "warp-delete" permission, except for your own warps
/warp info name - info on the warp, coordinates, player who created it, creation date, requires "warp-info" permission
/warp list page - lists warps, requires "warp-list" permission
/home set - sets your home, requires "home-set" permission
/home - goes to your home, requires "home-set" permission
/back - undoes the last teleport, requires "undo-teleport" permission
/spawn - goes to spawn, requires "spawn" permission

EDIT: since there are a lot of teleport permissions, "teleport-all-perms" would give you all teleport, warp and home permissions. Useful for moderators/admins.

PostPosted: Fri Mar 23, 2012 13:26
by sfan5
+1

PostPosted: Thu Apr 05, 2012 13:05
by Michael Eh?
I believe someone is working on portals/transporters (warps). I suspect that transport means it has to be activated while portal is autoamtic. There is already a mod called sethome.

The problem is the admin would have to 'set' a whole lot of permissions with this implimentation where as the other, he just has to set a name with coordinates. Useful for people who want to build a big project or community and wants users to visit.

As for the MUCKs, there is a 'meetme' command which send a request to the player asking if they want to be teleported. This might be more easier to impliment.

My idea was to add useful features to an existing command.