Hello! I’d like to share my impressions and some advice about your game. I really like the project, it’s clear that you’re putting effort into it, and that’s exactly why I decided to write this — maybe my thoughts will help you develop the game further.
Right now, a lot of your content either doesn’t work because of poor code, or players will never see it simply because they don’t know it exists. The longer you postpone refining the system, the more work you’ll have later. More content means more things that need to be fixed.
1. Story and Character Routes
Think through the story routes and write them down. This will help both you and the players understand the direction of the gameplay.
For example, the main character could be:
Strong Dominant — dominates everyone.
Weak Dominant — himself dominated by the father.
Strong Lover — a path of trust and love.
Weak Lover — a more vulnerable storyline.
Similarly, you can develop routes for other characters. Yes, it’s a lot of work, but it will bring clarity and structure.
2. Love and Corruption System
Avoid using a numerical system (20, 30 points, etc.). You yourself get confused about whether content unlocks at 20 points of love or 30.
Use levels instead — this way it will be simpler and clearer when new content becomes available.
3. Mother and Sister Characters
Work out their development routes and possible events.
Create a weekly schedule to remove dependence on randomness.
Add events that mark transitions to a new level of love or corruption.
Consider splitting the characters: the player interacts with one girl, while the father takes the other. This could create either a challenge for the player to keep both girls, or easier gameplay through an agreement with the father to divide spheres of influence.
4. Father Character
The current Father’s behaviour system looks repetitive — you have four identical phases.
You could replace it with a tension scale (for example, in percentages).
Tie the father’s interest to a specific character for a week — this will make the game more engaging. For instance, if the player ignores the situation, the character’s attachment to the father will increase.
5. Programming
Don’t repeat code: if something occurs more than twice, move it into a function.
Avoid nested if statements: use switch case instead, it will simplify the logic.
Function naming: be careful with case sensitivity (e.g., MomEvent and momEvent are different).
Code structure: dialogues and text are better stored in separate functions/events rather than in general places.
$person_kidnapped is false — this check appears too often. An event shouldn’t even be considered if the character is absent from the location.
Read about OOP principles — even basic ideas will help make your code cleaner.
6. Game Mechanics
Transformation into a girl is interesting but complicated. It might be better to make it a separate option.
The main plot (zombie apocalypse) doesn’t feel present. Characters live calmly, without threat. If you want to keep this setting, add survival elements: gathering food, defending against zombies, events tied to danger.
Conclusion
I genuinely like your project. I wouldn’t spend time writing such a detailed comment if I thought it was “trash.” You already have a solid foundation, and if you focus on code quality and story development, the game will become much stronger.
Good luck with development! If you have questions, feel free to reach out — I’ll try to help.