FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

fix(community-poi): point the maze BlueMap link at the actual build by TheMeinerLP · Pull Request #325 · OneLiteFeatherNET/launchpad · GitHub

fix(community-poi): point the maze BlueMap link at the actual build - #325

Merged
TheMeinerLP merged 1 commit into
mainfrom
fix/maze-bluemap-coordinates
Sep 6, 2026
Merged

TheMeinerLP merged 1 commit into
mainfrom
fix/maze-bluemap-coordinates

Conversation

Copy link
Copy Markdown
Collaborator

What

The maze POI listed -1465 / 61 / 792 as its coordinates. CommunityPoiBluemap.vue builds the BlueMap deep link and the copy-to-clipboard coordinate label straight from that block, so both sent visitors to empty terrain instead of the build.

Corrected to -2209 / 61 / 35 in both locales. y was already correct and stays at 61.

before after
x -1465 -2209
y 61 61
z 792 35

Files: content/community-poi/de/labyrinth.md, content/community-poi/en/maze.md.

What this does not touch

The schematic paste origin further down the same frontmatter still reads -1465 / 61 / 792, and its setupNotes line repeats it. Until now it matched the POI coordinates; after this change it no longer does.

That value is where the schematic has to be pasted, which is not necessarily where the build stands, so changing it on inference would put everyone's paste in the wrong place. It needs confirming with B3nNy separately.

Testing

Frontmatter-only change, no code touched. Verified the coordinates block is the source of the BlueMap link in components/features/community-poi/CommunityPoiBluemap.vue, and that the schematic origin block is unchanged in the diff.

The maze POI carried -1465 / 61 / 792 in its `coordinates` block, which is
what CommunityPoiBluemap.vue turns into the BlueMap deep link and the
copyable coordinate label. Visitors following either landed nowhere near
the build. Corrected to -2209 / 61 / 35 in both locales; y was already
right and stays at 61.

The schematic paste origin further down the frontmatter still reads
-1465 / 61 / 792 and is deliberately untouched: that is where the
schematic has to be pasted, and it needs confirming separately before it
is changed.

Copy link
Copy Markdown

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
launchpad e91a790 Commit Preview URL

Branch Preview URL
Sep 06 2026, 10:22 AM

TheMeinerLP merged commit 84963ad into main Sep 6, 2026
7 checks passed
TheMeinerLP deleted the fix/maze-bluemap-coordinates branch September 6, 2026 10:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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


Back | FazBrowse Home | New Git URL