Malevolent Planet Unity2d Day1 To Day3 Public Fixed ((link))

🌌 Malevolent Planet 2D: Dev Sprint Retrospective (Days 1–3)

We’ve just wrapped up a high-intensity three-day sprint to stabilize the core of Malevolent Planet 2D

, and the results are finally ready for public consumption. This phase wasn't just about adding content—it was about architectural fixing

and restoring the "ME-genes" that first drew players to our alien world. Day 1: The Foundation & Visual Clarity

The first 24 hours were dedicated to overcoming "direction fatigue." We pivoted back to the game's original hook: survival and exploration on a hostile alien frontier. Full Resolution Art:

We’ve officially enabled full-resolution asset rendering. No more blurred sprites; the alien flora and tentacle-laden landscapes are now as sharp as intended. Resolution Fixes:

Addressed a critical bug where UI elements (like the ship's legend and town maps) were getting cut off on mobile and 4:3 displays. Day 2: Content Restoration & Scene Logic

Day 2 focused on "un-breaking" what was lost during previous iterations. Re-enabling Legacy Scenes:

Two major scenes that were previously disabled due to logic conflicts have been overhauled and re-integrated into the demo build. The Alien Tentacle Scene:

We’ve added a deep-dive preview into one of the more "malevolent" encounters, emphasizing the darker, atmospheric themes players have been asking for. Day 3: Public Stability & "Fixed" Build Deployment The final day was about ensuring the build actually for the community. Input & Interaction Polish:

Fixed a recurring combat lock-out bug where players would get stuck during specific encounters (like the "Blackmailing Creep" at the bar) if they didn't choose a specific option. Multi-Platform Parity: We successfully deployed the fixed build across Windows, MacOS, Android

, and a browser-playable version to ensure maximum accessibility. Why This Matters

In early development, it’s easy to lose sight of the "original goal"—repairing the ship and exploring the unknown. These three days were a commitment to traceable logic

and zero assumptions. We’re moving away from "floating" development and back into a structured, episodic release cycle. The April 2025 Public Build is now live. expand on the technical Unity2D implementation

(like the C# manager scripts used for the scene restoration) or draft the patch notes for the next update? Dev Log 01 - My First Dev Log - DEV Community

Day 2: Stabilizing Malevolence with FixedUpdate

Goal: Ensure the planet’s hostile actions occur at predictable, physics-aligned intervals.

Key Concept – FixedUpdate:
Unity’s physics system runs at a fixed timestep (default 0.02 seconds). FixedUpdate is called exactly once per physics tick, regardless of frame rate. For a malevolent planet affecting Rigidbody2D gravity, this is mandatory.

Revised Script – PlanetMalice.cs (Day 2):

using UnityEngine;

public class PlanetMalice : MonoBehaviour
public float gravityIncreasePerSecond = 0.5f;
public float maxGravity = 15f;
public float shakeInterval = 3f;
public float shakeIntensity = 0.2f;


private Rigidbody2D playerRb;
private float originalGravity;
private float shakeCooldown;
void Start()
playerRb = GameObject.FindGameObjectWithTag("Player").GetComponent<Rigidbody2D>();
    originalGravity = playerRb.gravityScale;
    shakeCooldown = shakeInterval;
void FixedUpdate() // ← Physics-step aligned
// Increase gravity in fixed steps
    if (playerRb.gravityScale < maxGravity)
playerRb.gravityScale += gravityIncreasePerSecond * Time.fixedDeltaTime;
// Shake timer using fixed delta
    shakeCooldown -= Time.fixedDeltaTime;
    if (shakeCooldown <= 0f)
ShakePlanet();
        shakeCooldown = shakeInterval;
void ShakePlanet()
// Apply positional shake (visual only, not affecting physics)
    transform.localPosition = Random.insideUnitCircle * shakeIntensity;
    // Reset position next FixedUpdate (simplified)

Why FixedUpdate is essential:
If gravity increased in Update() (frame rate dependent), a player on 144 FPS would experience slightly different gravity deltas than one on 60 FPS, even with Time.deltaTime, due to floating-point accumulation over many small steps. FixedUpdate guarantees consistency across all devices. The malevolent planet becomes deterministic—hostile in the same way for every player.

Public variables still in use:
gravityIncreasePerSecond remains public. Now it works with Time.fixedDeltaTime, meaning “increase gravity by 0.5 per second” is physically accurate.

Essay: Architecting a Malevolent Planet in Unity 2D – A Three-Day Iteration on Public and Fixed Variables

Day 2 — Implement gameplay fixes, UX polish, and quality improvements (8–10 hours)

Objectives

Tasks

  1. Apply priority bug fixes (address top 3–5 user-reported issues)
    • Examples: collision glitches, enemy AI stuck states, player invulnerability bugs, save/load corruption.
    • Write clear commits referencing changelog.
  2. Input & responsiveness
    • Verify Input settings (old Input Manager vs. Input System). Ensure controls are responsive on keyboard/controller.
    • Adjust fixed-update vs update usage for movement physics to reduce jitter (use FixedUpdate for Rigidbody2D physics).
  3. Camera & view
    • Check Camera follow (Cinemachine or custom); confirm bounds and smoothing are stable.
    • Ensure camera doesn’t reveal off-level artifacts.
  4. UI/UX fixes
    • Ensure health/hud updates correctly and without flicker.
    • Add lightweight feedback: hit flashes, sound cues for critical actions.
  5. Performance tuning
    • Use Unity Profiler to identify major spikes.
    • Address common 2D issues: excessive dynamic batching breaks, too many SetActive toggles, heavy per-frame allocations (avoid Linq in Update).
  6. Playtesting
    • Run through first 3 levels/scenes to reproduce previously-reported issues.
    • Log steps to reproduce any remaining bugs.
  7. Build & test
    • Produce a new Public Fixed build (increment version).
    • Run on target platform; verify fixes and UX improvements.

Deliverables by EOD Day 2

Fixed Encounter Design

Originally, The Lithovore spawned directly on the player’s position, leading to instant death. Now, it emerges from a designated fissure 20 units away, giving you 8 seconds to prepare.

Lithovore Stats (Unity 2D Inspector Values):

Day 1–Day 3 guide — "Malevolent Planet" (Unity2D) with Public Fixed build

This is a concise, practical 3-day plan to implement and test a Unity2D build named “Malevolent Planet” using the Public Fixed configuration (assumed: a build intended for public release with prior critical fixes). Assumptions made: 2D top-down or side-scroller game, small team or solo developer, existing project skeleton. Adjust time estimates to your pace.

5.1 Finite State Machine (FSM)

The game switches between

This guide covers the essential progression for the early days of Malevolent Planet 2D

, focusing on the "public fixed" version (v0.2.3 and later). 🚀 Getting Started (Public Fixed Version)

The "fixed" builds (often discussed in community forums) primarily address inventory bugs and resolution issues.

Optimization: Use the new quality settings if you experience lag during combat scenes.

Mobile Tip: If playing on Android, the Joiplay emulator is recommended to fix resolution bugs where the map legend or North Gate area might be cut off.

Save Often: Public versions are prone to choice-locks during specific combat encounters. 🗓️ Day-by-Day Walkthrough Day 1: Arrival and Orientation

The Tutorial: Do not skip it. It introduces vital mechanics like spawn points and class switching that are difficult to learn on the fly.

Survival Basics: Your primary goal is to gather basic resources. Focus on navigating the initial ship area and the main town map.

Combat: Expect to die. Even veterans have low survival rates early on. Use the respawn button to stay in the fight and gain experience. Day 2: Exploration and Quests

Medicine Questline: You must access the North Gate to progress this path. If the gate is invisible or unclickable, it is likely a resolution bug (see the Joiplay fix above).

Interactions: Engage with NPCs in the bar. Be careful with "Blackmailing" encounters; some players report combat locks if specific "caress" options aren't used, though recent fixes aim to resolve this. Day 3: The G-Test and Expansion malevolent planet unity2d day1 to day3 public fixed

New Content: Day 3 introduces the G-test scenario, new illustrated scenes, and a brand-new map.

Dialogue: There is a significant increase in dialogue branches. Choices made here often lead to the "Cult Dream" sequence. Major Boss: You will likely encounter the Sharnah-thing.

Tip: Losing this fight is often a scripted path into the Cult Dream.

Bug Alert: If the game freezes when you choose to "get up" or "stay on the ground," ensure you are on the latest "public fixed" version, as this was a known progression blocker. 🛠️ Critical Troubleshooting Inventory Bugs

Inventory is occasionally disabled by the developer until fully stable. Map Cut Off

Adjust resolution settings or use the Joiplay emulator for mobile. Combat Lockup

Ensure "Tool Tips" are disabled if they prevent choice selection. If you'd like, I can help you with: Specific boss strategies for the Sharnah-thing. A detailed list of choices to reach specific endings.

How to install and configure Joiplay for the best experience.

Let me know which part of the story you're currently stuck on! Malevolent Planet 2D - Day3.1 G-test Gone Wrong | Patreon

) and supports cross-platform play across Windows, MacOS, Android, and web browsers. Protagonist : Players follow

, whose story begins at the International Space Academy as she prepares for her departure into space. Gameplay Mechanics

: The Unity version introduced mouse and keyboard-driven movement, a gallery system, and a branching narrative where choices determine the character's "purity" or submission to planetary temptations. Development Progression: Day 1 to Day 3 In the context of the April 2025 Public Build

and earlier devlogs, the initial "days" or stages of the demo focus on establishing the setting and core loops: Day 1: The Academy & Foundations

: Establishing the narrative "gaps" missing from the original text game.

: Emma’s adventures within the International Space Academy, serving as a tutorial for movement and basic interaction. Day 2: Exploration & Encounter Introductions

: Expanding the open-world village map and introducing the primary conflict.

: Introduction of the game's choices-matter system. Players encounter early NSFW previews, such as "Shower Content" and "Erotic Posing," which were enabled in recent public builds. Day 3: The "Malevolent" Shift : The transition from the Academy to the alien environment. Highlights

: In recent fixed builds, this includes the "Alien Tentacle" scene preview and high-resolution art updates. It marks the point where the player must choose between "establishing themselves" on the planet or focusing on the main story plot of ship repair. Technical "Fixed" Updates Optimization : Recent public builds fixed issues regarding

to prevent hardware strain (coil whine) and improved art resolution to full HD. Save System

: In current public demos, saving is often disabled or "fixed" to specific scenes to prevent technical bugs when loading across different versions. You can track further updates or play the demo through the Malevolent Planet 2D Patreon Steam Community Hub available during the Academy phase? Malevolent Planet Unity 2D Teaser Screenshots + Early GIF 🌌 Malevolent Planet 2D: Dev Sprint Retrospective (Days

The public releases for "Malevolent Planet 2D," a project built in Unity2D, follow a structured "Day" system reflecting in-game progression. The following report summarizes the key fixes and content added during the public releases for Day 1 through Day 3. Day 1: Garden Public Release

This release centered on the initial environment and foundational gameplay mechanics. Fixes & Technical Updates:

Resolved various WebGL-specific bugs to ensure stable browser play.

Implemented a new Inventory Menu and Character Screen for better item management. Content Additions: New Map: Introduced the ISA Garden area.

Art Upgrades: Updated "Chibi" character art and added two new animations. Day 2: The Reassembly

Development during this phase focused on refining character interactions and fixing visual glitches in the academy setting. Fixes & Technical Updates:

Character Outfits: Fixed an issue where the character would mistakenly wear the academy outfit instead of the night dress when returning from the showers on the first night.

Quest Markers: Fixed a bug where the "Pheromone Bush" quest marker remained visible after completion.

Visual Clipping: Addressed character clipping issues in the ISA Garden where sprites would walk through flower pots. Content Additions:

Introduced a Ship Facilities Upgrade Menu to advance specific questlines.

Added the Ship's Gym as a new location, including unique gym-related outfits. Day 3: Blackmail Letter Release

The Day 3 update significantly expanded the narrative scope and improved backend performance. Fixes & Technical Updates:

Performance Optimization: Implemented substantial changes to memory management and CPU usage to improve stability.

Save/Load System: Enabled the "Save to File" and "Load from File" features for Windows users. Content Additions:

New Questline: Introduced the "Blackmail Letter Part 1" quest. Animations: Added two new narrative-driven animations.

You can track future updates or download the latest builds via the Malevolent Planet 2D Patreon or the Steam Community Hub. Malevolent Planet 2D - The Reassembly - Patreon

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.

Day 2: Adding Visual Effects and Basic Movement

Step 1: Adding Visual Effects

Step 2: Basic Movement

using UnityEngine;
public class PlanetMovement : MonoBehaviour
public float speed = 2.0f;
void Update()
transform.Rotate(Vector3.forward * speed * Time.deltaTime);