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.
To handle the "Malevolent" aspects (random encounters or stat changes), the system likely employs a ScriptableObject-based Event Bus or a C# Action system.
// Example of a decoupled event trigger
public class GameEvent : ScriptableObject
public void Raise()
// Notify all listeners that a planet event occurred
If you want, I can:
The project Malevolent Planet 2D is an adult-oriented sci-fi exploration game developed in Unity. Recent "Day" updates (such as Day 3.1) focus on bug fixes, performance optimizations, and expanding the story content. Guide: Navigating Day 1 to Day 3 (Public Fixed)
The "Public Fixed" versions are released to address critical issues found in earlier builds. If you are starting from Day 1 and progressing to Day 3, follow this roadmap: Day 1: Arrival & Initial Exploration
Focus: Establish your base and begin exploring the immediate surroundings.
Goal: Interact with the environment and the first set of characters to trigger the opening narrative.
Tip: Save frequently in early builds, as some public versions of Day 1 had interaction bugs that were fixed in subsequent "Fixed" patches. Day 2: Resource Gathering & Narrative Progression
Focus: Utilize what you have gathered to expand your presence on the planet.
Goal: Trigger deeper story beats and more complex character interactions.
Critical Note: Pay attention to dialogue choices; these versions started introducing "memory" descriptions to hint at future content. Day 3 / Day 3.1: Expansion & Stability
Key Updates: The "Day 3.1" patch is the most stable version of this phase.
Inventory Bugfix: The inventory system was previously a major source of bugs. In many "Fixed" public builds, it remains disabled until specifically required to prevent game-breaking errors.
New Content: Includes a new map, approximately 3–5 new illustrated scenes, and a "G-test" scenario.
Optimization: Use the 3 new Quality Settings added in this version if you experience performance lag on the larger maps. General Gameplay Advice
Save System: In public demos, saving might be restricted or "locked" during certain teleportation scenes to prevent loading bugs that could occur in the full build.
Performance: If the game stutters during the new Day 3 scenes, check the Performance Optimizations menu to adjust your quality settings.
Progression: If you are stuck, look for "Flora" encounters; these often signal deeper, darker story themes that are central to the game's exploration loop. Malevolent Planet 2D - Day3.1 G-test Gone Wrong | Patreon
This report outlines the development and release status of the Malevolent Planet 2D project, focusing on the public releases covering the narrative timeline from Day 1 to Day 3. Project Overview
Malevolent Planet 2D is an adult-oriented sci-fi adventure game developed in Unity. The project features a mix of exploration, dialogue-heavy narrative, and illustrated/animated scenes. Recent efforts have focused on "The Reassembly," a significant structural overhaul to consolidate the game's episodic content into a cohesive build. Public Release Content: Day 1 to Day 3
The public build covering the "Day 1 to Day 3" arc is a milestone release that allows non-patrons to experience the early-to-mid-game content, including major story beats and mechanical fixes.
Day 1 Content: Focuses on the initial crash-landing, exploration of the alien environment, and meeting the core crew members.
Day 2 Content: Includes the "Classroom" update, which introduced NPC interactions, 6 new scenes (5 illustrations, 1 animation), and a dedicated map for the academy/classroom setting.
Day 3 Content: Covers critical plot developments including "Day 3.1 G-test Gone Wrong" and "Day 3.3 Blackmail Letter Part 1". Technical Fixes and Optimizations
The "fixed" public builds specifically address stability and performance issues encountered in earlier episodic releases.
Critical Inventory Bugfix: A known source of soft-locks and crashes, the inventory system was overhauled and, in some versions, temporarily disabled to ensure game stability during the Day 3 narrative flow.
Performance Optimizations: Integration of three new quality settings to support a wider range of hardware.
Memory Management: Significant changes to CPU usage and memory allocation to prevent "out of memory" errors during high-resolution scene transitions.
UI Enhancements: Added Quality of Life (QoL) features such as Auto Play, Skip, and Hide buttons for dialogue sequences. Feature Summary Update/Status Animation malevolent planet unity2d day1 to day3 public fixed
1-2 new animations per major sub-day (e.g., G-test, Blackmail). Illustrations
HD resolution art enabled for all scenes in the April 2025 build. Maps Forest, Lakeshore, Classroom, and Simulation Room. Platforms Android, Windows, MacOS, and Web/Browser. Project Direction
The developer is currently shifting focus back toward the "main story plot," which involves repairing the ship to escape the planet, following a period of "lack of direction" where development focused heavily on side-content and open-world village elements. Malevolent Planet 2D - Day3.1 G-test Gone Wrong | Patreon
🌌 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
) 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 Surviving the Abyss: A Post-Mortem Guide to Fixing
: 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
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
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: Minimal example changelog (template)
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
It looks like you're referencing a specific bug or issue in a Unity 2D project—likely a game about surviving on a "malevolent planet" over days (Day 1 to Day 3). The phrase "public fixed" suggests you may have seen a patch note or forum post.
Below is a general troubleshooting guide for fixing common unity 2D bugs related to a time‑based (day 1–3) survival game on a hostile planet.
If you share more specific error messages or code, I can tailor this further.
Step 1: Interactive Elements
Sprite, name it "Cursor".Mouse Joint to it if you want to use a physics-based interaction.Step 2: Enhancing Visuals and Atmosphere
Step 3: Testing and Publishing
File > Build Settings, selecting your desired platform, and clicking "Build".This guide provides a basic overview. A malevolent planet project could involve complex modeling, detailed texturing, and programming sophisticated behaviors. However, this should give you a starting point for exploring Unity2D and game development concepts.
Based on the context of the Malevolent Planet 2D project, which has been transitioning from a text-based adventure to a Unity-based 3/4 top-down game, the "Day 1 to Day 3" period typically focuses on foundational mechanics and the protagonist Emma's early experiences at the International Space Academy.
If you are looking for a feature to implement or fix in this specific public build version, here is a breakdown of the most relevant options: 🛠️ Core Feature: Interaction & Choice System
Since the game is a narrative-driven RPG with "VN-like scenes," a robust interaction system is essential for the early days of the story.
Dialogue Branching: Implement a system where Day 1 choices (e.g., being "pure" vs. "giving in to temptation") set persistent flags that change Day 3 interactions.
Contextual Interaction: Use a ProximityTrigger on the Space Academy NPCs so Emma can interact only when near them, triggering different dialogue based on her current "Day" progress. 🧭 Quality of Life: Grid-Aligned Movement Fix
A common complaint in the public community builds is inconsistent movement and clipping through vegetation in areas like the garden.
Pixel-Perfect Pathfinding: Ensure the 2D Collider shapes match the tilemap grid exactly to prevent "sticky" corners.
Normalized Speed: Fix the bug where horizontal movement is faster than vertical by using vector2.Normalize() in your movement script.
V-Sync Toggle: As requested by players on Itch.io, adding a simple V-Sync toggle in the settings menu helps with GPU coil whine and screen tearing. 🎒 Mechanic: Academy Quest Tracker
Day 1 to Day 3 involves several "orientation" tasks at the Academy.
Quest Hints: Add a simple UI overlay that gives Emma hints for exploration quests (like the "Medicine questline" or "Garden Exploration").
Time-Specific Events: Implement a Day/Night or Shift-based system (e.g., the "Nurse Shift" mod) that locks or unlocks specific Academy rooms based on the current day. 🔒 Technical Fix: Save System Stability
The public builds often have locked saving to prevent bugs during scene transitions.
Checkpoint Saving: Instead of a "save anywhere" system (which causes issues when teleporting between scenes), implement Day-End Saving. This ensures the game state is only recorded when Emma returns to her quarters at the end of Day 1 or Day 2. Which area should we develop first? To help you build this out, let me know:
Are you focusing on the narrative/dialogue logic or the character physics?
Do you need a C# script template for one of these specific features?
Are you trying to fix the infinite loop crash mentioned in recent status reports?
I can provide the specific code blocks or logic flow for any of these!
The tutorial introduces ScriptableObjects to define characters and events.
The Architecture:
Why this matters: This separation allows a developer to create 100 different planet exploration events without writing a single new line of C# code. The "Deep" realization here is that the code becomes an engine for reading data, rather than the game itself.