Malevolent Planet Unity2d Day1 To Day3 Public Fixed 'link' May 2026

The transition from a text-based adventure to a 2D engine in Unity has been a major pivot. The goal is to move away from heavy environmental descriptions and focus more on visual storytelling, character dialogue, and the game’s unique NSFW encounters Day 1: Foundation & The Ship The Engine Pivot

: Migration to Unity 2D is officially underway. The focus has shifted from writing about the "yellow sun torching the soil" to actually showing it through atmospheric visual effects. Core Systems

: Initial work on the ship and hub area logic. Much like the Citadel in Mass Effect

, the player's ship will serve as the primary hub for exploration and character interaction. Asset Prep

: Beginning to integrate full-resolution art into the Unity build to ensure the game’s aesthetic "oozes" the original dark theme. Day 2: Exploration & UI World Building

: Started work on the open-world village map. The gameplay is diverging from the original text version to make exploration more centric and rewarding. Menu Mechanics : Implemented the pause menu (

) at the top left. This menu is crucial for adjusting graphic quality and resolution, though early feedback shows it still needs better visibility on Android. Resolution Support

: Addressed bugs where the screen would stretch in non-fullscreen modes, aiming for better compatibility across different device sizes. Day 3: Interaction & Public Build Fixes Combat Logic

: Fixed a critical bug in the "Blackmailing Creep" encounter where combat would lock if specific options (like "caress") weren't used. Save System Development

: Tackled the technical hurdle of save files. Currently, saving is locked in the demo to prevent bugs during teleportation scenes, but work is ongoing to ensure full build compatibility. Public Demo Content : Enabled two previously disabled scenes for the Public Build

, bringing the current total to roughly 7–8 available scenes that hint at the game's full narrative scope. Proactive Follow-up: specific platform format , such as a Patreon update or an Itch.io developer log?

Post by SugarMint in Malevolent Planet v0.2.3 comments - itch.io

Viewing post in Malevolent Planet v0.2.3 comments. ↑ View parent post. SugarMint3 years ago(+2)(-1) Thanks, it definitely helps :) Post by Alwiane in Malevolent Planet 2D Demo - itch.io malevolent planet unity2d day1 to day3 public fixed

Surviving the Abyss: A Post-Mortem Guide to Fixing "Malevolent Planet" in Unity 2D (Days 1–3 Public Build)

Target Keyword: malevolent planet unity2d day1 to day3 public fixed
Audience: Indie Game Developers, Unity 2D Programmers, Game Jam Participants
Focus: Debugging, public build stability, early-game progression locking.

The "Public Fixed" Save System

A major complaint was corrupted Day 2 saves. The new build implements dual-slot autosaving – every 5 minutes, the game writes to an alternate file. If the malevolent planet triggers a crash (e.g., too many concurrent particle effects), the previous stable save loads without progress loss.

Day 1: Exposing Hostility with Public Variables

Goal: Establish core planetary hostility—e.g., gradual gravity increase or periodic ground shakes.

Key Concept – public variables:
By declaring variables as public, they appear in the Unity Inspector. This allows designers to tweak values without recompiling scripts. For a malevolent planet, hostility must be adjustable: too weak feels passive; too strong feels unfair.

Example Script – PlanetMalice.cs (Day 1):

using UnityEngine;
public class PlanetMalice : MonoBehaviour
public float gravityIncreasePerSecond = 0.5f;
public float maxGravity = 15f;
public float shakeIntensity = 0.2f;
public float shakeInterval = 3f;
private Rigidbody2D playerRb;
private float originalGravity;
private float shakeTimer;
void Start()
playerRb = GameObject.FindGameObjectWithTag("Player").GetComponent<Rigidbody2D>();
    originalGravity = playerRb.gravityScale;
    shakeTimer = shakeInterval;
void Update()
// Increase gravity over time (malevolent pressure)
    if (playerRb.gravityScale < maxGravity)
playerRb.gravityScale += gravityIncreasePerSecond * Time.deltaTime;
// Periodic shake
    shakeTimer -= Time.deltaTime;
    if (shakeTimer <= 0f)
ShakePlanet();
        shakeTimer = shakeInterval;
void ShakePlanet()
// Apply random offset to planet sprite or camera
    transform.position = (Vector2)transform.position + Random.insideUnitCircle * shakeIntensity;

Why public matters here:
On Day 1, the developer can adjust gravityIncreasePerSecond from 0.5 to 0.2 (easier) or 1.0 (nightmare mode) directly in the Inspector. shakeIntensity and shakeInterval are also exposed. Without public, these values would be hardcoded, requiring script recompilation for every balance test.

Limitation discovered: Using Update() for gravity changes ties hostility to frame rate. On a fast PC, gravity increases more frequently per second? No—Time.deltaTime corrects for that. But a bigger issue: physics interactions (jumping, sliding) become inconsistent if gravity changes mid-physics step. This leads to Day 2.

Day 1: Setting Up the Unity Project and Basic Scene

Step 1: Create a New Unity Project

• Open Unity Hub and create a new 2D project. Name it "MalevolentPlanet".

Step 2: Setting Up the Scene

• Create a new scene by going to File > New Scene. Name it "MainScene".
• Add a basic background. You can use a simple color or a texture. For simplicity, let's use a color: Add a Sprite game object by right-clicking in the Hierarchy panel, selecting 2D Object > Sprite. Name it "Background".
• Change its Sprite Renderer color to a dark or ominous color representing the malevolent planet's atmosphere.

Step 3: Create the Planet

• Create another Sprite and name it "Planet". You can use a circle sprite for simplicity.
• Scale it to represent a planet. You might want to add a Rigidbody2D and a collider (like Circle Collider 2D) to it if you plan to add physics.

6. If the bug persists after “public fixed” version

• Clear Unity Cache (Delete Library/ folder, reopen project).
• Check if the bug exists only in WebGL builds – some public fixes target PC only.
• Search your exact error code (e.g., NullReferenceException: Day2Spawner) in forums with "malevolent planet unity2d patch".

Let me know if you have:

• The exact error message or console log.
• A snippet of your DayController or GameManager script.
• The Unity version (e.g., 2022.3 LTS).

I can then give you a precise fix for the Day 1–3 public release bug.

The Malevolent Planet Unity2D (Day 1 to Day 3 Public Fixed) build represents a significant transitional phase for the project as it moves from its original text-based roots into a visual, 2D top-down exploration game. This "Public Fixed" version addresses critical stability issues from earlier prototypes, specifically fixing infinite loops and graphical crashes by migrating to Unity 2022 LTS.

Below is a detailed review of the gameplay, technical improvements, and narrative content found in this three-day development cycle. 🕹️ Core Gameplay and Exploration

The 2D version shifts focus toward environmental storytelling and active exploration, moving away from the dense text descriptions of the original version.

Perspective & Controls: The game utilizes a 3/4 top-down view. It supports both keyboard and mouse-driven movement, making it accessible for various playstyles.

Day 1: The Garden Release: This initial public milestone introduced the Inventory Menu and Character Screen, alongside upgraded "Chibi" art style for the world map.

Day 2 & 3: Expansion: Development shifted toward the Human Camp and Village Map, introducing a hub-centric exploration style inspired by games like Mass Effect.

Ship Repair Mechanics: While exploration is central, the primary gameplay loop involves gathering resources to repair your ship to escape the planet. 🛠️ Technical Fixes and "Public Fixed" Features

The "Fixed" designation is vital for this build, as earlier iterations suffered from severe engine-level bugs.

Engine Migration: The developer moved the project from Unity 2020 to 2022 LTS to solve "infinite loop" crashes that haunted previous versions. The transition from a text-based adventure to a

WebGL Performance: Significant work was put into fixing WebGL bugs, allowing for a smoother browser-based experience on sites like Itch.io.

Resolution and UI: The "Fixed" build enables full resolution art display. It also attempted to fix UI scaling issues where the fullscreen toggle would occasionally break the click-detection on Android devices.

Save System Constraints: Note that the public demo often has locked saving. This is a technical choice to prevent save-file corruption when players are teleported between different story scenes. 🔞 Narrative and Adult Content

The game is explicitly designed as an adult experience, blending survival horror themes with NSFW encounters.

Prequel Elements: The Unity2D version starts earlier than the text game, following protagonist Emma’s training at the International Space Academy.

Branching Choices: The game emphasizes that choices matter. Players can choose to remain "pure" or succumb to the temptations of the alien flora and crew members.

New Animations: The Day 1–3 builds introduced specific high-quality animations, including the Alien Tentacle scene and encounters within the Human Camp.

This essay assumes “Malevolent Planet” refers to a 2D game where the planet (or environment) actively works against the player (e.g., shifting gravity, hostile terrain, or a corrupted world core).

Day 3 — QA, polish, optimization, and release checklist (6–8 hours)

Objectives

• Thorough QA pass, finalize optimizations, complete release checklist for Public Fixed release.

Tasks

1. QA pass
   • Smoke test all menus, scene transitions, save/load, and options.
   • Test critical flows: start → die → respawn, pause/resume, audio toggles.
   • Test on at least one other machine or emulator for platform parity.
2. Bug triage
   • Fix any critical/severe bugs found; defer minor cosmetic items to future patch.
   • Update changelog with final list of fixes.
3. Final optimizations
   • Strip unused assets via Addressables or Resources cleanup.
   • Ensure build size is reasonable: compress textures, set proper sprite import settings (Max Size, Compression).
   • Confirm audio clips are compressed appropriately.
4. Accessibility & settings
   • Verify key options: volume sliders, key remapping (if supported), windowed/fullscreen toggle.
   • Ensure graphics options match 2D needs.
5. Packaging & metadata
   • Update version number, build number, and release notes.
   • Create a release build via automated script; sign binaries if required.
6. Release checklist
   • Sanity-run installer or zipped build.
   • Confirm checksum/signature if needed.
   • Prepare short release notes summarizing Public Fixed changes and known issues.
7. Post-release monitoring plan
   • Add a task to monitor crash reports and player feedback for 48–72 hours after release.

Deliverables by EOD Day 3

• Final Public Fixed build ready for distribution.
• Release notes & changelog.
• QA report and post-release monitoring plan.

Goals by day

• Day 1: Stabilize core systems & get a reproducible Public Fixed build exporting successfully.
• Day 2: Implement/verify gameplay fixes and polish critical UX.
• Day 3: QA, optimize, final export and release checklist.

Unity 2D Specific Optimizations for Days 1-3

Because Malevolent Planet relies heavily on Tilemap.renderer and SpriteShape, the public build suffered from memory spikes. Here is how to keep Days 1 through 3 running at 60 FPS. Why public matters here: On Day 1, the