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?