Several UI elements in the Space Ship Game remain untranslated when the platform language is set to Spanish. The interface displays English text such as “SELECT YOUR SHIP,” “Create New,” “Select Ship,” and “Delete,” instead of their localized equivalents.
Issue Description
When accessing the Space Ship game module, the interface fails to apply Spanish translations to multiple labels and buttons. The issue affects both static text and dynamic content within the ship selection panel. The problem persists across sessions and browsers, suggesting missing localization keys or incomplete translation mapping.
Environment
Property
Value
Application
SpikerSoft Learn
Module
Space Ship Game
Environment
Production
Browser
Firefox
Operating System
Windows 11
Version
v2026.08.27b
Device
Desktop
Preconditions
User must be logged in and have Spanish selected as the display language.
Steps to Reproduce
Log in to the SpikerSoft platform.
Navigate to Games > Space Ship Game.
Observe the ship selection interface.
Check the text labels and buttons.
Expected Result
All interface elements should appear in Spanish, consistent with the selected language setting.
Actual Result
Several elements remain in English:
“SELECT YOUR SHIP”
“Create New”
“Select Ship”
“Delete”
“Class: Unknown”
“No weapons equipped”
“Play time: 0h 0m”
Evidence
The screenshot shows the ship selection interface with untranslated English text while the global UI (navbar) is correctly localized to Spanish.
The version label v2026.08.27b confirms the environment.
Impact
Breaks language consistency across the platform.
Reduces accessibility for Spanish-speaking users.
Suggests incomplete localization coverage in the game module.
Frequency
Always
Reproducibility
100%
Severity
Medium
Notes
The issue likely stems from missing translation keys in the Space Ship game’s localization file. It is recommended to review the language resource bundle and ensure all UI strings are mapped to Spanish equivalents.
## Summary
Several UI elements in the **Space Ship Game** remain untranslated when the platform language is set to Spanish. The interface displays English text such as “SELECT YOUR SHIP,” “Create New,” “Select Ship,” and “Delete,” instead of their localized equivalents.
## Issue Description
When accessing the Space Ship game module, the interface fails to apply Spanish translations to multiple labels and buttons. The issue affects both static text and dynamic content within the ship selection panel. The problem persists across sessions and browsers, suggesting missing localization keys or incomplete translation mapping.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft Learn |
| Module | Space Ship Game |
| Environment | Production |
| Browser | Firefox |
| Operating System | Windows 11 |
| Version | v2026.08.27b |
| Device | Desktop |
## Preconditions
User must be logged in and have Spanish selected as the display language.
## Steps to Reproduce
1. Log in to the SpikerSoft platform.
2. Navigate to **Games > Space Ship Game**.
3. Observe the ship selection interface.
4. Check the text labels and buttons.
## Expected Result
All interface elements should appear in Spanish, consistent with the selected language setting.
## Actual Result
Several elements remain in English:
- “SELECT YOUR SHIP”
- “Create New”
- “Select Ship”
- “Delete”
- “Class: Unknown”
- “No weapons equipped”
- “Play time: 0h 0m”
## Evidence
- The screenshot shows the ship selection interface with untranslated English text while the global UI (navbar) is correctly localized to Spanish.
- The version label **v2026.08.27b** confirms the environment.
## Impact
- Breaks language consistency across the platform.
- Reduces accessibility for Spanish-speaking users.
- Suggests incomplete localization coverage in the game module.
## Frequency
Always
## Reproducibility
100%
## Severity
Medium
## Notes
The issue likely stems from missing translation keys in the Space Ship game’s localization file. It is recommended to review the language resource bundle and ensure all UI strings are mapped to Spanish equivalents.
Confirmed and fixed — good catch, and it turned out to be broader than the seven strings you listed.
Cause. The ship-selection panel is not HTML: it is drawn into the game's own WebGL scene as 3D text. Our translation directive only reaches HTML templates, so every label in that panel was a hardcoded English string. The rest of the page localises correctly, which is exactly why the navbar in your screenshot was Spanish while the panel was not.
Fixed, in spikerj/spikersoft-angular#892 — all of your reported strings plus the ones you would have hit next: the ship class names (Fighter/Frigate/Cruiser/…), the delete confirmation dialog, the SHIPS/HULL/SHIELD/ENERGY/HEAT/LOCATION/WEAPONS/CARGO headers, and the empty states. English and Spanish both added.
One deliberate detail: if a translation key is ever missing, the panel falls back to English rather than painting the raw key onto the screen — a failure mode that would look far worse than what you reported.
Follow-up filed: this game has ~20 more HUD panels built the same way (weapons, target, telemetry, options, ship creation…). They will have the identical problem; I have noted it so they get the same treatment rather than being discovered one bug report at a time. If you want to keep testing in Spanish, those are fertile ground.
Will close once it merges and deploys.
Confirmed and fixed — good catch, and it turned out to be broader than the seven strings you listed.
**Cause.** The ship-selection panel is not HTML: it is drawn into the game's own WebGL scene as 3D text. Our translation directive only reaches HTML templates, so every label in that panel was a hardcoded English string. The rest of the page localises correctly, which is exactly why the navbar in your screenshot was Spanish while the panel was not.
**Fixed**, in spikerj/spikersoft-angular#892 — all of your reported strings plus the ones you would have hit next: the ship class names (Fighter/Frigate/Cruiser/…), the delete confirmation dialog, the SHIPS/HULL/SHIELD/ENERGY/HEAT/LOCATION/WEAPONS/CARGO headers, and the empty states. English and Spanish both added.
One deliberate detail: if a translation key is ever missing, the panel falls back to English rather than painting the raw key onto the screen — a failure mode that would look far worse than what you reported.
**Follow-up filed:** this game has ~20 more HUD panels built the same way (weapons, target, telemetry, options, ship creation…). They will have the identical problem; I have noted it so they get the same treatment rather than being discovered one bug report at a time. If you want to keep testing in Spanish, those are fertile ground.
Will close once it merges and deploys.
The ship-selection HUD is drawn as WebGL text, so it never went through the normal translation path. It is now localised (spikerj/spikersoft-angular#892).
The change is on master and deployed. Please re-test when you get a chance; if you still see it, reopen this issue rather than filing a new one so the history stays together.
Fixed and merged — closing.
The ship-selection HUD is drawn as WebGL text, so it never went through the normal translation path. It is now localised (spikerj/spikersoft-angular#892).
The change is on `master` and deployed. Please re-test when you get a chance; if you still see it, reopen this issue rather than filing a new one so the history stays together.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Several UI elements in the Space Ship Game remain untranslated when the platform language is set to Spanish. The interface displays English text such as “SELECT YOUR SHIP,” “Create New,” “Select Ship,” and “Delete,” instead of their localized equivalents.
Issue Description
When accessing the Space Ship game module, the interface fails to apply Spanish translations to multiple labels and buttons. The issue affects both static text and dynamic content within the ship selection panel. The problem persists across sessions and browsers, suggesting missing localization keys or incomplete translation mapping.
Environment
Preconditions
User must be logged in and have Spanish selected as the display language.
Steps to Reproduce
Expected Result
All interface elements should appear in Spanish, consistent with the selected language setting.
Actual Result
Several elements remain in English:
Evidence
Impact
Frequency
Always
Reproducibility
100%
Severity
Medium
Notes
The issue likely stems from missing translation keys in the Space Ship game’s localization file. It is recommended to review the language resource bundle and ensure all UI strings are mapped to Spanish equivalents.
Confirmed and fixed — good catch, and it turned out to be broader than the seven strings you listed.
Cause. The ship-selection panel is not HTML: it is drawn into the game's own WebGL scene as 3D text. Our translation directive only reaches HTML templates, so every label in that panel was a hardcoded English string. The rest of the page localises correctly, which is exactly why the navbar in your screenshot was Spanish while the panel was not.
Fixed, in spikerj/spikersoft-angular#892 — all of your reported strings plus the ones you would have hit next: the ship class names (Fighter/Frigate/Cruiser/…), the delete confirmation dialog, the SHIPS/HULL/SHIELD/ENERGY/HEAT/LOCATION/WEAPONS/CARGO headers, and the empty states. English and Spanish both added.
One deliberate detail: if a translation key is ever missing, the panel falls back to English rather than painting the raw key onto the screen — a failure mode that would look far worse than what you reported.
Follow-up filed: this game has ~20 more HUD panels built the same way (weapons, target, telemetry, options, ship creation…). They will have the identical problem; I have noted it so they get the same treatment rather than being discovered one bug report at a time. If you want to keep testing in Spanish, those are fertile ground.
Will close once it merges and deploys.
Fixed and merged — closing.
The ship-selection HUD is drawn as WebGL text, so it never went through the normal translation path. It is now localised (spikerj/spikersoft-angular#892).
The change is on
masterand deployed. Please re-test when you get a chance; if you still see it, reopen this issue rather than filing a new one so the history stays together.