# [Bug] “Book Processing” button visible during gameplay in WASM Voxel Game #283

New Issue

2026-06-28T16:17:05Z

enjin2310 commented

2026-06-28 16:17:05 +00:00

Summary

While playing the WASM Voxel Game, the Book Processing button remains visible in the bottom-right corner of the screen. This disrupts immersion and can lead to accidental clicks during gameplay, especially when players are focused on movement or building.

Issue Description

The Book Processing button appears as part of the interface even when the player is in active Game Mode. Its presence is visually distracting and functionally problematic, as it can be clicked unintentionally. This breaks the flow of gameplay and may trigger unintended actions or UI overlays.

Observed Behavior

The Book Processing button is visible during gameplay.
Clicking near the bottom-right corner can accidentally activate it.
The button overlaps with the game’s visual field, reducing immersion.

Expected Behavior

The Book Processing button should be hidden or disabled while in Game Mode.
It should only appear in menus, editors, or non-interactive contexts.

Environment

Property	Value
Application	SpikerSoft Learning Platform
Module	WASM Voxel Game
Environment	Production
Browser	Firefox
Operating System	Windows 11
Version	v2026.06.28c
Device	Desktop PC

Steps to Reproduce

Navigate to learn.spikersoft.com/wasm-voxel-game.
Enter Game Mode.
Observe the Book Processing button in the bottom-right corner.
Attempt to play normally — accidental clicks may occur.

Expected Result

The Book Processing button should be hidden or disabled during gameplay.

Actual Result

The button remains visible and clickable, disrupting immersion and gameplay.

Evidence

Screenshot shows the Book Processing button visible in the bottom-right corner while the player is actively exploring the voxel world.

Impact

Reduces player immersion.
Increases risk of accidental clicks.
Interrupts gameplay flow and testing experience.

Frequency

Always

Reproducibility

100%

Severity

Medium

Notes

Hiding or disabling the Book Processing button during active gameplay would improve user experience and prevent unintended interactions.

## Summary While playing the **WASM Voxel Game**, the **Book Processing** button remains visible in the bottom-right corner of the screen. This disrupts immersion and can lead to accidental clicks during gameplay, especially when players are focused on movement or building. ## Issue Description The **Book Processing** button appears as part of the interface even when the player is in active **Game Mode**. Its presence is visually distracting and functionally problematic, as it can be clicked unintentionally. This breaks the flow of gameplay and may trigger unintended actions or UI overlays. ### Observed Behavior - The **Book Processing** button is visible during gameplay. - Clicking near the bottom-right corner can accidentally activate it. - The button overlaps with the game’s visual field, reducing immersion. ### Expected Behavior The **Book Processing** button should be **hidden or disabled** while in **Game Mode**. It should only appear in menus, editors, or non-interactive contexts. ## Environment | Property | Value | |-----------|--------| | Application | SpikerSoft Learning Platform | | Module | WASM Voxel Game | | Environment | Production | | Browser | Firefox | | Operating System | Windows 11 | | Version | v2026.06.28c | | Device | Desktop PC | ## Steps to Reproduce 1. Navigate to `learn.spikersoft.com/wasm-voxel-game`. 2. Enter **Game Mode**. 3. Observe the **Book Processing** button in the bottom-right corner. 4. Attempt to play normally — accidental clicks may occur. ## Expected Result The **Book Processing** button should be hidden or disabled during gameplay. ## Actual Result The button remains visible and clickable, disrupting immersion and gameplay. ## Evidence - Screenshot shows the **Book Processing** button visible in the bottom-right corner while the player is actively exploring the voxel world. ## Impact - Reduces player immersion. - Increases risk of accidental clicks. - Interrupts gameplay flow and testing experience. ## Frequency Always ## Reproducibility 100% ## Severity Medium ## Notes Hiding or disabling the **Book Processing** button during active gameplay would improve user experience and prevent unintended interactions.

Screenshot 2026-06-28 121354.png

907 KiB

spikerj commented

2026-06-30 23:14:50 +00:00

Confirmed and fixed in spikersoft-angular PR #84 (open, not yet merged). Root cause: the global "Book Processing" FAB (showBookFab() in app.component.ts) is shown purely based on profile/role (reading interest, or Staff/Admin) with no route awareness, so it floats over every route — including full-bleed game canvases like WASM Voxel. Made it route-aware via a small immersive-route allowlist that currently covers /wasm-voxel-game. Will close once the PR is merged. Flagging for awareness: the same FAB-over-canvas issue likely applies to other immersive game routes (space-game, chess, etc.) if a reading-interest/staff user visits them — happy to file a follow-up to extend the allowlist if that's wanted, but scoping this fix to the reported route for now.

Confirmed and fixed in spikersoft-angular PR #84 (open, not yet merged). Root cause: the global "Book Processing" FAB (`showBookFab()` in `app.component.ts`) is shown purely based on profile/role (reading interest, or Staff/Admin) with no route awareness, so it floats over every route — including full-bleed game canvases like WASM Voxel. Made it route-aware via a small immersive-route allowlist that currently covers `/wasm-voxel-game`. Will close once the PR is merged. Flagging for awareness: the same FAB-over-canvas issue likely applies to other immersive game routes (space-game, chess, etc.) if a reading-interest/staff user visits them — happy to file a follow-up to extend the allowlist if that's wanted, but scoping this fix to the reported route for now.

spikerj commented

2026-07-01 01:23:15 +00:00

Resolved in spikersoft-angular PR #84 (merged to master). Root cause: the global "Book Processing" FAB (showBookFab() in app.component.ts) is shown purely based on profile/role (reading interest, or Staff/Admin) with no route awareness, so it floated over every route — including full-bleed game canvases like WASM Voxel. Made it route-aware via a small immersive-route allowlist that currently covers /wasm-voxel-game. Closing.

Flagging for awareness: the same FAB-over-canvas issue likely applies to other immersive game routes (space-game, chess, etc.) for reading-interest/staff users — happy to file a follow-up to extend the allowlist if that's wanted.

Resolved in spikersoft-angular PR #84 (merged to `master`). Root cause: the global "Book Processing" FAB (`showBookFab()` in `app.component.ts`) is shown purely based on profile/role (reading interest, or Staff/Admin) with no route awareness, so it floated over every route — including full-bleed game canvases like WASM Voxel. Made it route-aware via a small immersive-route allowlist that currently covers `/wasm-voxel-game`. Closing. Flagging for awareness: the same FAB-over-canvas issue likely applies to other immersive game routes (space-game, chess, etc.) for reading-interest/staff users — happy to file a follow-up to extend the allowlist if that's wanted.

spikerj closed this issue

2026-07-01 01:24:11 +00:00

spikerj referenced this issue

2026-07-14 20:16:59 +00:00

[Bug][Backend][Quality] QuizGenerationService validation is fail-open — if the validation LLM call throws, the unvalidated question ships in the quiz #564

spikerj referenced this issue

2026-07-14 20:17:13 +00:00

[Bug][Tests][QuizGeneration] ValidRequest_IsConsumedAcked_QuizCompletesWithFakedQuestions_AndNotifies fails on master — quiz contains questions from pages other than the expected page 4 #586

spikerj referenced this issue

2026-07-14 20:24:25 +00:00

[Bug][Backend][Quality] QuizGenerationService validation is fail-open — if the validation LLM call throws, the unvalidated question ships in the quiz #564

spikerj referenced this issue