spikerj/spikersoft-issues
1
0 Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases Wiki Activity

wasm-voxel chat formatter: §o applies bold instead of italic #799

New Issue
Closed
opened 2026-07-22 11:38:23 +00:00 by spikerj · 1 comment
spikerj commented 2026-07-22 11:38:23 +00:00
Owner
Copy link
Copy source

Component: libraries/game/wasm-voxel/src/_components/wasm-voxel/ts/libraries/chat.ts (convertOld)

The Minecraft italic formatting code §o maps to c.bold = true instead of c.italic = true (see case "o"). As a result, italic-coded chat text renders bold, and italic is never produced by convertOld at all. The bold code §l is handled correctly on its own line, so §o should read c.italic = true.

Upstream reference (janispritzkau/mc-chat-format, cited at the top of the file) maps o → italic.

Impact: cosmetic — italic-styled voxel-game chat shows as bold. Low priority.

Fix: one line — case "o": c.italic = true;.

Test: chat.spec.ts currently pins the buggy behavior (annotated LATENT BUG) in increment 45 of the frontend coverage wave (PR #540). When fixed, flip that assertion to { text: "Hi", italic: true }.

Found during the frontend test-coverage expansion (tests-only wave, so not fixed in that PR).

**Component:** `libraries/game/wasm-voxel/src/_components/wasm-voxel/ts/libraries/chat.ts` (`convertOld`) The Minecraft italic formatting code `§o` maps to `c.bold = true` instead of `c.italic = true` (see `case "o"`). As a result, italic-coded chat text renders **bold**, and `italic` is never produced by `convertOld` at all. The bold code `§l` is handled correctly on its own line, so `§o` should read `c.italic = true`. Upstream reference (`janispritzkau/mc-chat-format`, cited at the top of the file) maps `o` → italic. **Impact:** cosmetic — italic-styled voxel-game chat shows as bold. Low priority. **Fix:** one line — `case "o": c.italic = true;`. **Test:** `chat.spec.ts` currently pins the buggy behavior (annotated `LATENT BUG`) in increment 45 of the frontend coverage wave (PR #540). When fixed, flip that assertion to `{ text: "Hi", italic: true }`. Found during the frontend test-coverage expansion (tests-only wave, so not fixed in that PR).
spikerj commented 2026-08-07 13:47:25 +00:00
Author
Owner
Copy link
Copy source

Migrated to spikerj/spikersoft-angular#635 as part of the umbrella-tracker breakup.

Verified 2026-08-07 against the synced default branch.

  • Code: spikersoft-angular@8e5a4048 — still broken. libraries/game/wasm-voxel/src/_components/wasm-voxel/ts/libraries/chat.ts:97-99 still reads case "o": c.bold = true; break;.
  • Live: Cosmetic only — italic-coded voxel chat renders bold. Not separately probed.
  • Remaining: One line: case "o": c.italic = true;. Then flip the LATENT BUG assertion in chat.spec.ts to { text: "Hi", italic: true }.

Status: still broken — full detail carried over to the new issue.

Closing here. Work now lives in the repo that holds the fix, so fixes #635 in a PR will
auto-close it on merge. The umbrella tracker keeps cross-repo epics only.

— Opus 5 Agent

Migrated to **spikerj/spikersoft-angular#635** as part of the umbrella-tracker breakup. Verified 2026-08-07 against the synced default branch. - **Code:** `spikersoft-angular@8e5a4048` — still broken. `libraries/game/wasm-voxel/src/_components/wasm-voxel/ts/libraries/chat.ts:97-99` still reads `case "o": c.bold = true; break;`. - **Live:** Cosmetic only — italic-coded voxel chat renders bold. Not separately probed. - **Remaining:** One line: `case "o": c.italic = true;`. Then flip the `LATENT BUG` assertion in `chat.spec.ts` to `{ text: "Hi", italic: true }`. Status: still broken — full detail carried over to the new issue. Closing here. Work now lives in the repo that holds the fix, so `fixes #635` in a PR will auto-close it on merge. The umbrella tracker keeps cross-repo epics only. — Opus 5 Agent
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
agentic
Actionable surfaced by the agentic architecture & security review
 bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 epic
Cross-repo epic — children live in per-repo trackers
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 sonarqube
Code quality issue surfaced by SonarQube (bug / code smell)
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
spikerj (Joseph Spiker)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spikerj/spikersoft-issues#799