Skip to content

[codex] support Folia hotload through Shiroha 26.2 - #1

Draft
heoduling wants to merge 2 commits into
1.21.11from
codex/folia-hotload-2.6.21
Draft

[codex] support Folia hotload through Shiroha 26.2#1
heoduling wants to merge 2 commits into
1.21.11from
codex/folia-hotload-2.6.21

Conversation

@heoduling

Copy link
Copy Markdown
Owner

Summary

  • retain the custom Folia-safe Bukkit hotload lifecycle, player-owned scheduling, bounded cleanup, packet limiting, and post-hotload handshake recovery
  • accept standard Bukkit plus dotted and dashed Paper/Shiroha 26.2 version strings
  • select the existing 1.21.5+ compatibility implementation for 26.1 through 26.2 regardless of local build revision
  • cover the reported 26.2.local-SNAPSHOT and 26.2-local-SNAPSHOT formats in the plugin self-test

Root cause

The inherited Bukkit version parser only accepted legacy x.y[.z]-R... strings. Shiroha 26.2 reports a Paper-style local build string, so Simple Voice Chat disabled before compatibility initialization.

Impact

The 2.6.21-hotload Bukkit plugin now initializes compatibility version 20 and starts its UDP service on Shiroha/Folia 26.2 while preserving the existing hotload-specific safety fixes.

Validation

  • :bukkit:pluginSelfTest passed
  • :bukkit:shadowJar passed
  • normal Shiroha 26.2 startup selected compatibility version 20 and started UDP 24454
  • forced -Dvoicechat.compatibility=26.2-local-SNAPSHOT startup passed
  • occupied UDP 24454 path disabled SVC without UnsupportedOperationException
  • package inspection found no duplicate entries, signatures, or test classes and retained folia-supported: true

Remaining live checks

A real voice-chat client was not available for UDP audio and fresh-player post-hotload handshake verification. PlugManX 3.0.4 could not execute the unload/load cycle because PlugManX itself fails to parse the Shiroha local build token.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant