ВЕРСИИ (13)

Added Minecraft 26.3 support. RTP and Wild now search over server ticks so large searches no longer kick players. New safe_mode and enabled options for rtp and wild. TPA requests show clickable Accept and Deny buttons. Home and warp lists have delete buttons. All chat messages restyled.

Added Minecraft 26.3 support. RTP and Wild now search over server ticks so large searches no longer kick players. New safe_mode and enabled options for rtp and wild. TPA requests show clickable Accept and Deny buttons. Home and warp lists have delete buttons. All chat messages restyled.

Added Minecraft 26.3 support. RTP and Wild now search over server ticks so large searches no longer kick players. New safe_mode and enabled options for rtp and wild. TPA requests show clickable Accept and Deny buttons. Home and warp lists have delete buttons. All chat messages restyled.

Added Minecraft 26.3 support. RTP and Wild now search over server ticks so large searches no longer kick players. New safe_mode and enabled options for rtp and wild. TPA requests show clickable Accept and Deny buttons. Home and warp lists have delete buttons. All chat messages restyled.

**1. Autosuggest — replaced custom with vanilla.** `/tpa` and `/tpahere` now use Mojang's `EntityArgument.player()` (Yarn: `EntityArgumentType.player()`), the exact same argument vanilla commands like `/msg` and `/tp` use. Player-name suggestions now come from the game itself, not our custom provider — there's no custom code left that could break them. Offline names are rejected by Brigadier automatically. **2. Buttons.** They use the vanilla `RunCommand` click event (verified against Mojang mappings — identical to how vanilla buttons work), so a click runs `/tpaaccept <name>` / `/tpadeny <name>` as the clicking player with zero typing. The old `/tpaaccept` / `/tpadeny` commands still exist as fallback. **3. Proof logging.** Since I can't see your server, I added console logs: `[Teleport] TPA request: Alice -> Bob`, `[Teleport] TPA accepted: ...`, `[Teleport] TPA denied by ...`. After deploying: - Type `/tpa <Tab>` — names should complete (needs 2+ players online to really prove it; solo only shows yourself). - Have someone click ACCEPT — you should see the accept line in the **server console**. If the line appears but no teleport happens, send me that console output and I'll pinpoint it. If no line appears on click, the click never reached the server (client/proxy issue).

**1. Autosuggest — replaced custom with vanilla.** `/tpa` and `/tpahere` now use Mojang's `EntityArgument.player()` (Yarn: `EntityArgumentType.player()`), the exact same argument vanilla commands like `/msg` and `/tp` use. Player-name suggestions now come from the game itself, not our custom provider — there's no custom code left that could break them. Offline names are rejected by Brigadier automatically. **2. Buttons.** They use the vanilla `RunCommand` click event (verified against Mojang mappings — identical to how vanilla buttons work), so a click runs `/tpaaccept <name>` / `/tpadeny <name>` as the clicking player with zero typing. The old `/tpaaccept` / `/tpadeny` commands still exist as fallback. **3. Proof logging.** Since I can't see your server, I added console logs: `[Teleport] TPA request: Alice -> Bob`, `[Teleport] TPA accepted: ...`, `[Teleport] TPA denied by ...`. After deploying: - Type `/tpa <Tab>` — names should complete (needs 2+ players online to really prove it; solo only shows yourself). - Have someone click ACCEPT — you should see the accept line in the **server console**. If the line appears but no teleport happens, send me that console output and I'll pinpoint it. If no line appears on click, the click never reached the server (client/proxy issue).

**1. Autosuggest — replaced custom with vanilla.** `/tpa` and `/tpahere` now use Mojang's `EntityArgument.player()` (Yarn: `EntityArgumentType.player()`), the exact same argument vanilla commands like `/msg` and `/tp` use. Player-name suggestions now come from the game itself, not our custom provider — there's no custom code left that could break them. Offline names are rejected by Brigadier automatically. **2. Buttons.** They use the vanilla `RunCommand` click event (verified against Mojang mappings — identical to how vanilla buttons work), so a click runs `/tpaaccept <name>` / `/tpadeny <name>` as the clicking player with zero typing. The old `/tpaaccept` / `/tpadeny` commands still exist as fallback. **3. Proof logging.** Since I can't see your server, I added console logs: `[Teleport] TPA request: Alice -> Bob`, `[Teleport] TPA accepted: ...`, `[Teleport] TPA denied by ...`. After deploying: - Type `/tpa <Tab>` — names should complete (needs 2+ players online to really prove it; solo only shows yourself). - Have someone click ACCEPT — you should see the accept line in the **server console**. If the line appears but no teleport happens, send me that console output and I'll pinpoint it. If no line appears on click, the click never reached the server (client/proxy issue).

- **Fixed /rtp bugs** - **Command GUI improvements**

- **Fixed /rtp bugs** - **Command GUI improvements**

- **Fixed /rtp bugs** - **Command GUI improvements**