agentsclimarketplace
Sign in

Minecraft crossplay ops

Skill AIKUSAN/minecraft-agent-skills-bundle/plugins/minecraft-codex-skills/skills/minecraft-crossplay-ops

Operate Java-to-Bedrock crossplay for Minecraft 1.21.x servers with Geyser and Floodgate. Use for proxy placement, online/offline authentication choices, Bedrock client connection triage, resource-pack delivery, converted-pack placement, plugin compatibility checks, port/firewall issues, and safe rollout/rollback of crossplay access.From its SKILL.md

Install
npx -y skills add AIKUSAN/minecraft-agent-skills-bundle --skill minecraft-crossplay-ops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, 638 tokens by cl100k_base, as published. Nobody here has run it

Minecraft Crossplay Operations Skill

Scope

Use this skill for Java servers that allow Bedrock Edition clients through Geyser, optionally with Floodgate authentication.

Routing Boundaries

  • Use when: the task is crossplay setup, Bedrock client access to a Java server, Geyser/Floodgate operations, crossplay resource-pack delivery, or compatibility triage.
  • Do not use when: the task is pure Java server administration (minecraft-server-admin), pure BDS administration (minecraft-bedrock-server-admin), pack conversion itself (minecraft-resource-pack-conversion), or Java plugin implementation (minecraft-plugin-dev).

Architecture Choices

Common placements:

  • Geyser as a standalone proxy in front of a Java server.
  • Geyser as a Velocity/Bungee plugin in a proxy network.
  • Geyser as a Paper plugin for small single-server setups.

Prefer proxy placement when the network already uses Velocity or when multiple backend servers need shared access.

Rollout Checklist

  1. Confirm Java server version and Geyser build compatibility.
  2. Decide whether Bedrock users must own Java accounts.
  3. If using Floodgate, install matching Floodgate components on the proxy/server.
  4. Open the Bedrock UDP listener port.
  5. Test with one Bedrock client before advertising support.
  6. Document username prefix/suffix policy for permission and moderation tools.

Authentication Modes

Use online-mode Java auth when Bedrock players will sign in with Java accounts. Use Floodgate when Bedrock players should join with Bedrock identities.

Operational guardrails:

  • Keep Floodgate key files private.
  • Align permission plugin contexts with Bedrock-prefixed names.
  • Test staff commands against a Bedrock account before granting broad access.

Resource Pack Delivery

For Java packs served to Bedrock clients:

  1. Convert the Java pack with minecraft-resource-pack-conversion.
  2. Place the converted Bedrock pack where Geyser expects packs for the chosen deployment mode.
  3. Restart or reload Geyser as documented by the local install.
  4. Join with a Bedrock client and confirm download, UI, item, and block visuals.

Keep the Java pack and converted Bedrock pack versioned together.

Compatibility Triage

For login failures:

  • Check Bedrock client version support.
  • Check UDP firewall rules.
  • Check Geyser startup logs for bind or remote-address errors.
  • Check Floodgate key and forwarding configuration.

For gameplay differences:

  • Identify whether the issue is protocol translation, plugin behavior, or pack conversion.
  • Reproduce with a vanilla Java account and a Bedrock account.
  • Disable optional plugins in staging to isolate plugin compatibility.

For permission problems:

  • Confirm the exact Bedrock username shown to the Java server.
  • Check LuckPerms user records and inherited groups.
  • Avoid wildcard staff grants to Bedrock test users.

Rollback

Rollback should be a reversible config change:

  • Disable public Bedrock port exposure.
  • Stop or unload Geyser.
  • Leave Java server data untouched.
  • Keep converted pack artifacts for post-incident review.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 638 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • Prefer proxy placement when the network uses Velocity
  • Confirm Java server version and Geyser build compatibility
  • Decide whether Bedrock users must own Java accounts
  • Install matching Floodgate components on the proxy and server
  • Open the Bedrock UDP listener port
  • Test with one Bedrock client before advertising support

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.