Skip to content

Release 1.19.1 - #166

Merged
tastybento merged 16 commits into
masterfrom
develop
Jul 30, 2026
Merged

Release 1.19.1#166
tastybento merged 16 commits into
masterfrom
develop

Conversation

@tastybento

Copy link
Copy Markdown
Member

No description provided.

tastybento and others added 16 commits May 29, 2026 17:27
The floating jitpack snapshot v1.21-SNAPSHOT resolves to an ephemeral
git-described build whose jar/POM get evicted, breaking CI even on
unchanged commits. Switch to the equivalent stable Maven Central
coordinates (org.mockbukkit.mockbukkit:mockbukkit-v1.21:4.110.0).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Publish the jar attached to each GitHub release to CurseForge via the shared
BentoBoxWorld/.github reusable workflow, downloading the release asset instead of
rebuilding from source. Mirrors the BentoBox core setup.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pin bentoboxworld/.github publish-platforms.yml to commit e0c5d98f5e6ef9ea7c9a28afad05f4c07bcde898 (Sonar
githubactions:S7637) and set the Hangar slug so releases publish to Hangar
alongside CurseForge.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…944b98b9

Picks up the split into independent CurseForge and Hangar jobs so neither
platform can block the other.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pin publish workflow to SHA and enable Hangar
…e4b1f0

ci: bump pinned reusable workflow to fe4b1f0
…ca2dcd1

ci: bump pinned publish-platforms.yml to ca2dcd1
The pinned SHA predates BentoBoxWorld/.github#13, which moved the CurseForge
metadata and Hangar versionUpload JSON out of inline curl -F values and into
files. curl treats a ';' in an inline -F value as the start of a type=
attribute, so a release body containing a semicolon truncates the JSON and
both platforms reject the upload.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SAQ3YQkcfRoCZEwa6SPJcp
warpPlayer(world, user, owner) has two teleport paths: the normal one,
used when the spot in front of the sign is safe, fires WarpInitiateEvent,
respects vanished players, and tells the sign owner that someone warped
to them; and a fallback, used when no safe spot in front exists, which
teleported the visitor directly onto the sign's own block and did none of
that. Owners silently missed warp visits whenever the fallback ran.

The fallback is common on cramped islands — a ChunkBlock island starts as
a single chunk, so warp signs often sit at the platform edge with void in
front, which fails isSafeLocation and always takes the silent path. That
is how this surfaced: owners got warp messages in AOneBlock but never in
ChunkBlock.

The fallback now routes through the same warpPlayer completion path as a
normal warp, so the event, the vanish check, the sounds, and the owner
notification behave identically wherever the visitor lands. The sign's
facing is used for the arrival yaw, matching normal warps.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y7xSdVPS5vRu6wqf6XshRq
ci: bump publish-platforms pin to the multipart-JSON fix
…ck-warp

Notify the sign owner when a warp falls back to the sign block
@sonarqubecloud

Copy link
Copy Markdown

@tastybento
tastybento merged commit c6d853e into master Jul 30, 2026
5 checks passed
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