Arcane Teleport 0.6.0 — now a single jar (server and client)

The big change: Arcane Teleport is now one jar that works on both sides. Until now this download was the optional Client FX companion to a separately-distributed server mod. As of 0.6.0 the server-side /tpa ritual and the client-side FX live in the same jar, side-gated by Fabric's environment system — install it on a server, on a client, or both.

Already running the Client FX (0.1.x)?

Drop 0.6.0 into your client mods/ and you get the same client features as before:

• The dramatic fullscreen portal swirl during a /tpa ritual — no portal block, no purple plane
• The version handshake so server ops can see your install via /tpa debug clients
• Auto-close chat after clicking a [✦ Accept] / [✗ Deny] button
• Keep chat open after a self-confirm /tpa coords / /tpa waystone / /tpa bed (toggle in Mod Menu)

It stays fully compatible with any server running Arcane Teleport — the network protocol is unchanged, so 0.6.0 talks to old and new servers alike.

Why the jump from 0.1.4 → 0.6.0? The client and server were on separate version lines; merging them into one jar unified the numbering onto the server's line (which was at 0.5.1), so the combined release is 0.6.0.

New: the full server mod ships in the same jar

Server owners now install one mod instead of two (the client half stays inert on a dedicated server):

• Channeled player-to-player /tpa: XP cost from both players, a levitation + glyph-particle ritual, and a lightning finale; the cast breaks if either player moves or takes damage
• Solo destinations: /tpa coords <x y z> [dim], /tpa bed, and /tpa waystone (with Waystones installed)
• Safe-landing on arrival, /tpaccept / /tpdeny, permission nodes, hot-reloadable config, and the client-install audit (/tpa debug clients)
• Vanilla (unmodded) clients still get a graceful nausea-warp fallback; only modded clients see the swirl

Under the hood

• Single jar: fabric.mod.json environment: "*", with all client code gated by @Environment(CLIENT) and a client-scoped mixin config — client mixins are never applied on a dedicated server
• The two networking payloads are now a single shared source of truth (no more byte-for-byte duplication across two separate jars)

Requirements

• Minecraft 26.1.2 · Fabric Loader 0.19+ · Fabric API · Java 25
• Optional: Mod Menu (config toggle) · Waystones (for /tpa waystone)