#(bmobonk) Random Nether Surface Location
16 messages · Page 1 of 1 (latest)
(bmobonk) Random Nether Surface Location
Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>
it's for a /rtp command if anyone has any other ideas
There's no difference between a two surface like spots in the nether, so there's no one line tag for it. That being said, for an rtp command, I'd do something like ```yaml
#Get 0,0,0 in whatever world the player is in
- define location <location[0,0,0,<player.world>]>
#Find a random location in said world - define location <[location].random_offset[100000]>
#Roughly set that new location in the middle Y of the nether
#(Since the nether is only 128 blocks tall, if they ever change
#that you'd want to change this number) - define location <[location].with_y[64]>
#Find the closest location the player could reasonably be,
#using the logic of is_spawnable - define location <[location].find_spawnable_blocks_within[16]>```
Obviously, this could be shortened quite a bit, but I wanted to make it clear what each part of the tag was for.
Also, to avoid using a constructor, you could also do <player.location.with_x[0].with_y[0].with_z[0]>, but it's a little unwieldy. I believe this one of the few legitimate uses for a constructor (although another helper can call me out if they don't think so)
why not start the location at y 64 and then make the offset 10000,0,10000 or whatever
Like I mentioned, there's ways to make this shorter. It's only broken up so I can point to the things to be aware of. Like y should be roughly in the middle of the nether (y64). There's a number of ways that can be handled.