Hello everyone!

I'm currently working on a video where I do a 100% speedrun of Everlife! if you wish to see the video when it releases, be sure to sub to MaseMaster2K's YouTube channel!

But unfortunately, while recording, I discovered a few new issues, which this patch is meant to address. There were also some additional patches that fixed bugs during the recording section, but this is meant to take care of the rest of them.

With all that said, here are the changes in patch 1.2.1...

-The "hint" text now fades at the same time as the rest of the "death screen" interface.

-In the disclaimer when launching the game for the first time, the "E to skip" text now fades at the same speed as every other instance in the game.

-The collision in Murky Mansion's "dark room" is now identical to the floor of the rest of the level

-Fixed a bug where the projectile can get stuck floating after hitting an enemy's model.

-Fixed a bug where Everon wouldn't say a voice line if you were spotted in Tsundere Terror (causing confusion with the "You Didn't See Nothing" achievement.

Edit: OOPS!!! I implemented it a bit wrong, and the "run" line triggers immediately in patch 1.2.1. This is fixed in 1.2.11, so ensure you are on that version! (It will say in the title screen)

-Attempted to fix a bug with the glitchese freezing in the top corner of the map (this is a different version from the one before)

This time though, I would like to provide some clarification on why I keep saying "attempted" fix on the last bug. For that, I would like to provide some info on how I classify bugs (It's game dev lesson time! :D)

I classify bugs as four different categories, each differing in severity.

Green🟩: These are bugs that look goofy or unpolished, but ultimately don't impact the game experience for the player. Most players will likely disregard these bugs, or not notice them at all.

Examples: An interface's fading jumping to a different opacity in a janky manner, or the "enemy hit" particle effect showing behind the enemies or objects they hit.

Yellow🟨: Very few bugs qualify into this category. These are bugs that disrupt the play of the game, but in a very subtle way that almost no player will ever notice. As a side effect, their existence is the hardest to discover, which can allow some to stay in the game for a long time during development.

Examples: The tsunderes not being able to hear the metal doors, or the glitchese not retreating to the corner like they are supposed to.

Red🟥: These are noticeable bugs that actively disrupt gameplay in a way that players will notice. These bugs could actively mess with, or ruin a player's experience with the game, and as such, are almost always at the top of the priority list.

Examples: Stephanie teleporting outside the map with her ability, or the ghosts getting stuck in a certain area and never being able to escape.

Black⬛: These are bugs that would crash, permanently freeze, or softlock the game. In my experience, these bugs have only appeared when a certain change I make ends up being implemented wrong, and they are almost always fixed as soon as they appear in development, never making it into a packaged build.

Example: A poorly arranged function infinitely looping with no delay, causing the game to freeze indefinitely.

Bugs not only have differing severity, but they also differ in how often they appear. Some bugs appear every single time, others when a criteria is met, and some appear in a manner that feels random, or very rarely.

The glitchese freezing bug not only qualifies as a Red🟥 bug, but it also appears/appeared super rarely, and in a manner that feels random. As such, there isn't really a clear method of knowing if the bug is actually removed. All I can do it play the level several times and use probability of appearance to judge the success of a fix. If you ever see this bug, please report it!

Thanks for reading! I hope you also enjoyed my little insight on bug fixes ;)