justRTP

[1] New: Party RTP. One player leads a party and teleports everyone with one click. /rtp party opens a menu showing every member as their player head with live online status; the leader invites people by clicking heads in a built-in invite browser (the invite lands as a clickable ACCEPT/DENY message and expires on its own), kicks with a click, and picks in the settings screen how the party lands: spread around one shared spot, everyone on the exact same block, or each member on their own random spot, plus an optional air drop so the whole group arrives under parachutes. Switching between the party view, the invite browser and the settings happens inside one menu that never closes and reopens. The landing anchor is served from the location cache like any other /rtp and every member spot is safety-verified the same way matchmaking verifies its spread positions, so party teleports are as fast and as safe as solo ones. Leader cooldown and an optional Vault cost (refunded automatically if no location is found) are configurable under the new party block in config.yml, everything works from chat too (/rtp party invite/accept/deny/leave/kick/disband/teleport), and leadership passes on automatically if the leader leaves. config-version 44, messages-version 26.

[2] The live search can race several candidate spots at once, configurable as location_cache.parallel_candidates (1 to 4). One search chain is inherently sequential (whether try five happens depends on try four failing), so a bad streak pays one full chunk generation at a time no matter how many cores the CPU has; with 2 or more, independent chains run in parallel and the first safe spot wins, the attempt budget is split across the lanes, a losing lane's good spot goes into the location cache instead of being thrown away, lanes stop the moment the race is decided, and background cache refills always stay single-lane. The default is 1, the sequential search, because that is what measured faster: in cold-terrain A/B benchmarks the concurrent generations slowed each other down by more than the racing saved, making 2 and 3 lanes about twice as slow end to end on our test hardware. If your machine has generation headroom, try 2 or 3 and compare with /rtp benchmark on an ungenerated band; whichever wins on your hardware is the right setting.

[3] Elytras can no longer break air drops. A player wearing an elytra could open it mid parachute descent (and boost away with fireworks), escaping the drop entirely, force-loading chunks far from the landing spot and leaving the parachute rig behind in a broken state. Elytra gliding is now suppressed while the parachute is active, and a player who was already elytra-gliding when the drop starts has it closed. Configurable as air_rtp.glide.block_elytra (on by default).