| Age | Commit message (Collapse) | Author |
|---|
|
The v1.3.0 entry listed three changes out of the roughly forty that landed since
paper/v1.2.2, so the config.yml resilience work and every performance fix went
unrecorded.
Its Velocity note also predated moving Ktor out of the shared module and
understated the JAR reduction as roughly 1 MB. Measured against the released
asset it is about 5.6 MiB, from 8.2 MiB down to 2.6 MiB.
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
support
Velocity moved to the 4.x generation while platform-velocity still compiled
against 3.5.1, so the debug environment had to pin an older proxy than the one
most users now run.
The migration needed no source changes. Comparing every one of the 213 classes in
the API jar with javap shows 4.0.0 is identical to 3.5.1 in its public
signatures; the supported protocol range is unchanged too. The one real
difference is the POM, which moves adventure-bom from 4.26.1 to 5.2.0.
Support for 3.5.x is dropped even though the JAR would still load there, because
keeping it meant Adventure 4.26.1 could be the runtime and engine had to stay
inside the API surface both Adventure majors share -- a constraint no build step
could check. Narrowing to 4.x makes every supported runtime ship Adventure 5.2.0,
matching what engine already compiles against, so the constraint is gone rather
than merely documented. Nothing enforces the requirement in code, matching how
dropping 3.4.0 was handled in v1.1.0.
Also drops two dead dependencies: kaml, declared but never imported, worth about
1 MB of shaded JAR, and the velocity-api annotationProcessor, which does nothing
without Java sources or kapt.
|
|
Paper 26.2 bundles Adventure 5.2.0, a major bump from the 4.26.1 shipped by 26.1.
Adventure 5 makes ClickEvent generic, so the raw type in
CommandContext.replyWithEvent no longer compiled. Auditing the rest of the
Adventure 5 removals found no other affected usage.
api-version is raised to 26.2, dropping 26.1 support: the two Adventure majors
are not binary compatible, so claiming 26.1 compatibility would be a lie.
Also fixes two problems found while verifying on a real server: the Velocity
healthcheck invoked mc-health, which does not exist in the mc-proxy image, so the
container had never once passed its check; and the debug environments pinned no
build at all, which meant the proxy came up as 4.1.0-SNAPSHOT while the plugin is
compiled against velocity-api 3.5.1. Server versions are now derived by x from
the Gradle coordinates so they cannot drift from what the plugin targets.
|
|
|
|
|
|
|
|
Dependency-only release. Bump paperVersion to 1.2.1 and document
Paper API, library, Gradle, and Shadow plugin updates.
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
- Bump paperVersion to 1.2.0
- Update docker compose files to Paper/Folia 26.1.2
- Add v1.2.0 entry to CHANGELOG
- Drop "LunaticChat" prefix from release titles
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
Closes #173
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
|
|
|
|
PlayerChatListener was not registered unless channel chat or Velocity
cross-server chat was enabled, causing romaji conversion to silently
not work when used standalone.
Co-Authored-By: Claude <noreply@anthropic.com>
|
|
|
|
|
|
messages
|
|
|
|
|
|
- Fix invalid language key "general.formattedMessage" to "general.spyMessage" in ChannelMessageHandler
- Remove unused romajiConverter parameter from initializeChannelManager
- Update KDoc @throws to match ChannelAlreadyExistsException
- Reorganize CHANGELOG for v1.0.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
