- check_circle Advancements
- check_circle Functions
- 9,684 views, 6 today
- 570 downloads, 0 today
24
This will allow players to teleport using triggers (or not depending on the options set by the admin).
There will be a link on /reload to the options, or the admin can just run /function teleport:options
Only tested on 1.15, but should work in 1.13+ (if someone tests this, please confirm).
To install, just drop teleport.zip into your world's datapacks folder.
Currently implemented:
There will be a link on /reload to the options, or the admin can just run /function teleport:options
Only tested on 1.15, but should work in 1.13+ (if someone tests this, please confirm).
To install, just drop teleport.zip into your world's datapacks folder.
Currently implemented:
- Fully functional (clickable) options menu (function teleport:options)
- /trigger teleport_spawn (teleports you to the set spawn point)
- /trigger teleport_player (shows the error message telling you how to use the command)
- /trigger teleport_player set # (teleports you to the player numbered #)
- Player list shows the score to see the player's number
- Will ignore players with the following tags: global.ignore, global.ignore.pos
- Will play nice with certified datapacks
Compatibility | Minecraft 1.13 |
to | Minecraft 1.16 |
Tags |
3 Update Logs
Update #3 : by mrurl42 05/02/2020 2:07:04 pmMay 2nd, 2020
Added conventions to ignore anyone with the global.ignore tag or the global.ignore.pos tag. Also added the "installed datapacks" advancement.
LOAD MORE LOGS
4576174
119
Create an account or sign in to comment.
I'm having an odd issue, where the teleport_spawn command won't work if I'm over 300ish blocks away from spawn..
I can't figure out what might be causing it, cause spawn should always be loaded in memory, and nothing in the code mentions that distance, so I dono why that would happen.. even with other players standing near spawn, I can't use this command to tp to spawn if I'm over 300 away.
Maybe the armor_stand for teleporting the player to spawn, can't be created more than 300 blocks away from the player? Maybe instead, just place a Marker entity at the user-inputting spawn location, and leave it there, as a reference?
Also, side note, have you thought of changing some of the armor_stands to Marker entities?
BTW, I found a better way to disable people from TPing to certain players.. Just setting those player's tele_player_num to a negative number, seems to work! ;)
edit: Just curious, what's the diff between the tags global.ignore and global.ignore.pos I can't tell from looking at the code, since both tags are always checked?..
Also, is there a way to prevent players from teleporting TO a specific user? For example, if I want to prevent players from teleporting to ops.. (I assume it could be done by tagging those users, then checking whether the destination user has those tags, before sending players to them.)
Well, so far it's working pretty good. Tho I'm still trying to figure out how to have it ignore destination players if they're in spectate mode, or who have a special tag marking them as an op.
It might as well ignore teleporting people to Ops, cause ops can use the normal teleport commands. ;)
edit: In the tick.mcfunction file, does it make sense to exclude my Op-team from the "Handle adding new players" line, like so?
scoreboard players add @a[team=!Ops] tele_player_num 0
as well as the following execute line maybe..
edit2: well.. that seems to half work..
Thanks!
/scoreboard objectives setdisplay list tele_player_num
Alternatively, you could just turn off the player teleport option and turn it back on. This would reset the objective display like the above command would.