If any are found feel free to report them here, I and will try and fix them in the future.
I know the late game is very buggy, and i will be working to fix all issues as soon as possible.
To be precise, these are all event logic bugs; the character art issue is a switch error.
Also, a common problem with engines from RPG 2003 to the present: A delay buffer (i.e., event waiting for sorting) must be added to events. Otherwise, processing two events concurrently will cause soft locking or the second event to become invalid.
Even if the event needs to be activated later, an empty event prerequisite should be added according to the layer, and then enabled using a switch to prevent the "no prerequisite refreshed" bug.
Let me tell you a trick I used in game development.
Since the main game menu is useless, why not remove it? Yes, make it so that players can't view items or this setting in-game. In my game, even the protagonist can't open the menu... saving and such require going to a fixed location.
Why? I want to talk about a game I made during my RPG 2003 days. I encountered errors in game detection and some numerical calculations... not because I miscalculated, but because this type of game engine caused a "parallel processing" problem... I discussed this issue with AAAA (the uthor of Resident Evil Doraemon). I finally decided to use certain detection items as "keys."
In other words, the items the player carries are used for plot detection. When the player obtains a specific "key" item, many events revolve around this item detection. And by simply setting a concept like "only one type can be carried" or "items are limited to a certain quantity," different character states at different stages can be achieved.
This method is rather silly, but it's indeed a simple one. I've been using it for many years.
In this way, you can use item value judgments to flexibly save the protagonist's state, and even "manipulate items" to achieve event rewind and restart the game.And the difficulty of controlling the game.
Let me give you my example...
This is a character from an older game; she can store special items. There are also two others… like the Treasure Dragon.
In the game, her character art and movement animations are linked to "items." Due to the nature of RPG engines, I can assign each character a judgment item instead of a "judgment value." Although internally there's no difference, for beginners, items are easier to control and adjust… and also cater to some "cheaters" and "adjustment players."
At the start of each story segment, a judgment is performed to determine her movement animation. When the item count is higher than 10, a "Cracked Armor" animation appears. After that, there are six different animations for 30, 50, 70, 90, and 90+. When it's 90+, she becomes an "airship" and completely immobilized…
Besides 90+, the number of items changes the dialogue animations, dialogue, and some events. In certain story segments, exceeding a certain number can even lead to special events.Therefore, whether it's this character, Treasure Dragon, or a Broodmother their condition won't affect the main storyline; it will only cause trouble at specific times (like not being able to enter a house). However, this will still create some Gwent-like effects.
Some storylines feature a "pregnant woman" whose item acquisition is tied to a countdown timer. When the countdown reaches 0, an item is added, and a check is performed. Reaching a certain number of items triggers a birth event, considered a "percentage of births." If the percentage is successful, the player's location is "remembered," and the player is "moved to the story map." Afterward, the pregnant woman's items are cleared, the clock is turned off, and the player is "teleported back to the remembered location."
I also tried creating a system for the Broodmother but its skills required separate event design for each map, and global events had to be avoided, so I ultimately abandoned that approach.
I just want you to know you are a legend for offering feedback. I would have never thought of that. Doing so right now would require a complete rework of the framework of this project, but its good stuff to keep in mind and I will sure to use those tricks in the future.
Also just for my own curiosity I'm not familiar with the project that your were providing examples for?
This project is from 12 years ago...
I can easily describe an example verbally; let's take the alien girl Ella as an example.
Each time you wake up, a check is performed (note that facial expressions are created separately so they can be directly applied):
Event Branch:
Ella is in the party: true
[Item check "Ellabelly"]
IF item count is 0-10, then display image EllaB1
Display image EllaF2
Use text: "XXXXX"
IF item count is 11-30, then display image EllaB2
Display image EllaF2
Use text: "XXXXX"
IF item count is 31-50, then display image EllaB3
Display image EllaFB2 (facial position shifted due to different images)
Use text: "XXXX"
Character speed is -1
The protagonist turns to the side (because the belly is too big to wash from the front)
IF item count is 51-70, then display image EllaB4
Display image EllaFB2 (facial position shifted due to different images)
Use text: "XXXX"
Character speed is -1
The protagonist turns to the side
IF item count is 71-90, then display image EllaB5
Displays image EllaFB4 (face position shifted due to image difference)
Text: "XXXX"
Character speed -2
IF Item count 91+ or less, then display image EllaB6
Displays image EllaFA1 (face position shifted due to image difference)
Text: "XXXX"
Special event: Character leaves the party. Ella airship switch is NO.
(The above can be applied to other events. Note the speed setting for deletion. Each character needs a set of cluster judgments; otherwise, images may appear even when the character is not in the party.)
Image deleted!
...Specific room door:
IF Ella in party true
IF Ellabelly count 51-70, then display image EllaB4
Displays image character name FB2
Text: "Hope the door frame doesn't break..."
Sound effect
Map relocation
IF Ellabelly count 71-90, then display image EllaB5
Displays image EllaFB4
Text: "Too big, can't get in..."
Image deleted!
IF Ishura in the team::true
IF Ishura's belly count is between 51 and 70, then display image Ishura B4
Display image Ishura FB2
Text: "I need... to squeeze a little harder"
Image deleted!
Sound effect
Map relocation
IF Ishura's belly count is between 71 and 90, then display image Ishura B5
Display image Ishura FB4
Text: "Even if I break down the door, I still can't get in..."
IF Quinn in the team: true
IF Quinn's belly count is between 51 and 70, then display image Quinn B4
Display image Quinn FB3
IF Quinn's belly count is between 71 and 90, then display image Quinn B5
Display image Quinn FB3
Text: "You think I can squeeze through a door the size of a human?"
Image deleted!
(She's an anthropomorphic dragon, so she can't enter most doors; only her character portrait needs to be checked.) Character Action: The protagonist takes one step back (Note this is the final check; otherwise, the protagonist will retreat three times due to multiple characters in the party).
Important: Delete the image!
Oh, by the way, this is something I helped another author create... The "pregnant woman's" walking image isn't simply "adding a sphere," but rather requires adjusting the upper body to move back slightly. Because of the pressure on the pelvis, the legs walk more like a penguin or a duck.
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
