Malevolent Planet Unity2d Day1 To Day3 Public Fixed May 2026

The project began with the basics: establishing the eerie tone of a world that wants you dead. The primary goal for Day 1 was setting up the "public fixed" core architecture—the foundation that ensures the game runs smoothly for everyone, regardless of hardware.

A. Player takes damage immediately

B. Resources not spawning

// Example correct spawn for Day 1
if (day == 1 && !resourceSpawned)
Instantiate(woodPrefab, spawnPoint.position, Quaternion.identity);
    resourceSpawned = true;

C. Day counter resetting to Day 1

For those unfamiliar, Malevolent Planet uses a unique "Sentient Terrain" system. The ground itself has a NavMesh and an emotional stat (Sanity/Corruption). Between Day 1 (tutorial) and Day 3 (first boss encounter), a race condition occurs in the PlanetSentience coroutine.

The Symptom:
The game freezes during the "Planet Pulse" visual effect. The log shows:
NullReferenceException: Transform child index out of range (MalevolentPlanetTerrain.cs)

The Root Cause:
The public build attempted to dynamically reparent corrupted tilemap chunks during the day transition. Due to Unity 2D’s Tilemap rendering order, the SetParent() method was being called on a Transform that was already queued for destruction by the garbage collector. malevolent planet unity2d day1 to day3 public fixed

Day 3 was about tying the mechanics together into a playable vertical slice. This is where the atmosphere shifted from "tech demo" to "game."

Summary: In just three days, Malevolent Planet went from an empty scene to a heavy, atmospheric platformer with working AI, optimized physics, and a compelling light mechanic. The "Public Fixed" build is now live—dodge the flora, watch your step, and don't let the planet consume you.

The Problem:
Day 3 is the first major scripted event: the Malevolent Core spawns in the planet’s depths. But due to a layer collision mismatch (Unity’s 2D Physics layers vs. Sorting Layers), the Core would either spawn inside unbreakable terrain or not spawn at all. In 15% of public reports, the boss’s AI state machine froze mid-attack, leaving the player stuck in an unwinnable loop. The project began with the basics: establishing the

The Fix (Public Build v1.0.4 – hotfixed within 6 hours):

Result: The boss now spawns reliably. Players still die—but it’s their fault, not the code’s.