I've used game engines for many years.
Actually, most unused music and sound effects, as well as the main title image and enemy images, can be deleted. However, it's important to note that simply deleting them from the directory isn't enough… You need to locate the map, enemy groups and enemy settings, magic, animations, etc., pages in the system settings and clear all unnecessary settings. Only keep one enemy group, one enemy setting, and one magic effect.
I know a lot about strange occurrences… at least before I suffered half of the body broken bone in an accident, I often shared various experiences and special cases in the RPG community.
Since RPG2003, the biggest strange problem has been "parallel event processing." This is both an engine bug and a player setting issue, mainly due to events stacking and failing to be processed synchronously, or getting frozen in the synchronous processing stage. There's also the classic "clock hard problem"—the countdown system has always been a difficult setting to operate. Ultimately, this leads to incorrect results, either because parallel event processing conflicts cause a soft lock, or because it overrides another time.
Secondly, there's "event processing too fast." This is an old problem, so you must manually add a 0.1-second delay before some variable or numerical checks to resolve it; otherwise, the next event might jump directly before the previous one is finished processing.
Incorrect event activation or stacking is also an old engine problem. If an author creates an event and then directly creates a new event and sets an activation switch or event processing check, it causes the event to lack a pre-check, leading to a bug. In practice, it's best to create a blank page before activating any event. AAAAchan (author of Doraemon: Resident Evil) used numerous blank pages to avoid this bug. Simply put, the first page is empty, a "no event" page; the second page is used to activate the switch or other event triggers.
Another classic bug is the "Gwent effect," caused by globally allocated fixed events. Lazily making events globally triggered results in numerous bugs due to simultaneous calls.
Finally, there's the issue of asset handling. Many careless authors directly modify the game's basic settings but forget to remove default enemy groups, settings, magic effects, map settings, etc., from the settings menu. They only delete the assets in the package directory, not the related settings in the program group… ultimately leading to bugs.
Another less common bug is where level and attributes become "1," the cause of which remains unknown. This usually occurs when player A leaves the party, variables are saved, and player B inherits all of player A's experience, skills, and items.
ya I tried the v.02 version transferring the save files over and that seemed to work, still get an issue where having contraction mini game happen while fixing mini game makes the timer bug out
Didn't realize the v.02 was the up to date once since they were both posted the same day
But despite the bugs VERY good,who made the artwork? the simplicity of the number of characters probably makes it a lot more manageable, but good preggo sci-fi stuff
The game does not have a voluntary price donation download option... I can only go to ko-fi to buy you 5 cups of coffee recently.For a 20-year hobby!
Also, many years ago, didn't you draw a kobold comic strip about a female kobold mage who laid eggs due to a HYPER PREGNANT caused by using a magic scroll?
Bug:
Phase 4/Level 4: During repairs, the player will enter the final repair phase twice. The computers in the infirmary are unaffected, but those in the embryology room on the left are affected.
If repairs are completed prematurely and not ended, the infirmary will experience a power outage, preventing entry.
After repairs are completed, a power outage will prevent the generator from being restarted, trapping the player in the corridor.
Solution: Prioritize repairing the infirmary, then repair other areas as needed, completing all repairs before the power outage.
Additionally, the following will not cause fatal bugs:
Level 5 During the final repair, the computer on the right side of the middle screen will freeze after repair, requiring save/load (SL).
Level 5 Before the final repair, during the communication phase when restoring communication, the protagonist may lose textures due to the rapid transitions between puzzle scenes.
Level 5 After the final repair, if you don't reach the central room in time, you will be blown up… the countdown will not stop.
Balance Adjustment Suggestions:
1. The birthing event seems to be randomly determined by the number of clicks, with an occasional trigger rate that's too high.
2. Some events on the spaceship might be overlooked without deliberate investigation; more "flashes" are needed.
3. In parts of the fourth level, after completing repairs and returning to the crew quarters, you can't leave. I'm not sure if I overlooked the medical room and whether there's any story content there.
4. Moving the upper body slightly backward by 1-3 pixels in the walking image would better reflect the character's state.
5. Referring to my previous suggestion regarding the final return journey (the post-game entertainment section), create CG cutscenes and event cabins, inflation events, and conversations with the AI about experiences and opinions.
6. The protagonist's abdomen penetrates the hibernation pod in L5…XD
