# [Bug] Unable to Land After Planet Conquest in Space Game #1180

Closed
opened 2026-10-03 17:23:20 +00:00 by enjin2310 · 1 comment

Summary

In Space Game, after successfully conquering a planet through the Hextile Defense event, the player receives a message confirming the planet is conquered and available for landing. However, when attempting to Land, the game incorrectly displays a message stating that the planet must be conquered first. This prevents players from landing on planets they have already won.

Issue Description

The conquest sequence works correctly up to the completion of the Hextile Defense event. After defeating all 9 waves of enemies, the game confirms the planet is conquered. Despite this, the Land button remains locked, and the system still treats the planet as unconquered. This suggests that the conquest state is not being properly updated or saved in the game logic.

Environment

Property Value
Game Space Game
Module Planet Conquest / Landing
Environment Production
Platform PC
Version v2026.10.02a
Device Desktop

Preconditions

Player must complete the Hextile Defense event and receive the conquest confirmation message.

Steps to Reproduce

  1. Approach a planet (e.g., Mars) and trigger the Conquest event.
  2. Complete all 9 waves in Hextile Defense.
  3. Receive the message confirming the planet is conquered.
  4. Attempt to press Land.
  5. Observe that the game displays “You must conquer the planet first.”

Expected Result

After conquering the planet, the Land button should become active, allowing the player to land and interact with the planet.

Actual Result

  • The Land button remains inactive.
  • The game incorrectly reports that the planet is not conquered.
  • Player cannot proceed to land despite successful conquest.

Evidence

  • Screenshot shows the Mars interface with “Not conquered” displayed even after completing conquest.
  • The Land button remains disabled.

Impact

  • Blocks progression for players who have completed conquest events.
  • Prevents access to post-conquest gameplay features.
  • Breaks the intended reward loop of planetary conquest.

Frequency

Always

Reproducibility

100%

Severity

High

Suggested Fix

  • Verify that the conquest completion event correctly updates the planet’s ownership state.
  • Ensure the Land button checks the updated conquest flag rather than the initial state.
  • Add a post-event validation to confirm the planet’s conquered status before enabling landing.
## Summary In **Space Game**, after successfully conquering a planet through the **Hextile Defense** event, the player receives a message confirming the planet is conquered and available for landing. However, when attempting to **Land**, the game incorrectly displays a message stating that the planet must be conquered first. This prevents players from landing on planets they have already won. ## Issue Description The conquest sequence works correctly up to the completion of the **Hextile Defense** event. After defeating all 9 waves of enemies, the game confirms the planet is conquered. Despite this, the **Land** button remains locked, and the system still treats the planet as unconquered. This suggests that the conquest state is not being properly updated or saved in the game logic. ## Environment | Property | Value | |-----------|--------| | Game | Space Game | | Module | Planet Conquest / Landing | | Environment | Production | | Platform | PC | | Version | v2026.10.02a | | Device | Desktop | ## Preconditions Player must complete the **Hextile Defense** event and receive the conquest confirmation message. ## Steps to Reproduce 1. Approach a planet (e.g., Mars) and trigger the **Conquest** event. 2. Complete all 9 waves in **Hextile Defense**. 3. Receive the message confirming the planet is conquered. 4. Attempt to press **Land**. 5. Observe that the game displays “You must conquer the planet first.” ## Expected Result After conquering the planet, the **Land** button should become active, allowing the player to land and interact with the planet. ## Actual Result - The **Land** button remains inactive. - The game incorrectly reports that the planet is not conquered. - Player cannot proceed to land despite successful conquest. ## Evidence - Screenshot shows the **Mars** interface with “Not conquered” displayed even after completing conquest. - The **Land** button remains disabled. ## Impact - Blocks progression for players who have completed conquest events. - Prevents access to post-conquest gameplay features. - Breaks the intended reward loop of planetary conquest. ## Frequency Always ## Reproducibility 100% ## Severity High ## Suggested Fix - Verify that the conquest completion event correctly updates the planet’s **ownership state**. - Ensure the **Land** button checks the updated conquest flag rather than the initial state. - Add a post-event validation to confirm the planet’s conquered status before enabling landing.
Owner

Root cause (engine): winning the conquest did take the planet. The zone updated its own copy of the universe and re-sent the planet list. But LandOnPlanet is checked by the engine's router against a copy of the universe loaded from Redis when the process started, and nothing ever updates that copy. So any planet conquered since the last engine restart still looked unowned to the landing check, and the engine answered VoxelRefused "Not conquered". The landing only started working after the next engine restart or deploy, because the backend persists the owner and the next start reads it. A planet handed over with Cede had the same problem.

Fix: spikerj/spikersoft-gaming-engine#245. The surfaces directory, which the router and the zone already share, now records every change of owner and applies it on top of the startup copy for both the landing check and world creation. Cede now updates it too. The new regression test plays a conquest to victory and then lands. It fails on main with "Not conquered" and passes with the fix. There is no protocol change. The fix ships with the engine deploy that runs on merge.

Secondary (same screenshot): the boxes are ⊕ (U+2295, the reticule), ▰▱ (the BIO/ROBOTIC meters) and → (U+2192, the JOB line). Neither Orbitron nor Godot's fallback font has these glyphs, and a browser has no system font to fall back on. spikerj/spikersoft-games-godot#190 adds a DejaVu symbols fallback font. That change reaches players with the next web client publish.

🤖 Generated with Claude Code

**Root cause (engine):** winning the conquest did take the planet. The zone updated its own copy of the universe and re-sent the planet list. But `LandOnPlanet` is checked by the engine's router against a copy of the universe loaded from Redis when the process started, and nothing ever updates that copy. So any planet conquered since the last engine restart still looked unowned to the landing check, and the engine answered `VoxelRefused "Not conquered"`. The landing only started working after the next engine restart or deploy, because the backend persists the owner and the next start reads it. A planet handed over with Cede had the same problem. **Fix:** spikerj/spikersoft-gaming-engine#245. The surfaces directory, which the router and the zone already share, now records every change of owner and applies it on top of the startup copy for both the landing check and world creation. Cede now updates it too. The new regression test plays a conquest to victory and then lands. It fails on `main` with "Not conquered" and passes with the fix. There is no protocol change. The fix ships with the engine deploy that runs on merge. **Secondary (same screenshot):** the boxes are `⊕` (U+2295, the reticule), `▰▱` (the BIO/ROBOTIC meters) and `→` (U+2192, the JOB line). Neither Orbitron nor Godot's fallback font has these glyphs, and a browser has no system font to fall back on. spikerj/spikersoft-games-godot#190 adds a DejaVu symbols fallback font. That change reaches players with the next web client publish. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.