Hello all, Shirley here. I'll be using this post to document errors you may or may not come across when trying to run the game. Hopefully the solutions I provide work for you. I'll try my best to sort them from simplest to most complex.
"import: command not found"
This is an issue with your Python installation. You'll most likely need to re-install or upgrade (if possible). If this doesn't fix the problem, there is something wrong with Python.
"ModuleNotFoundError: No module named '[module]'"
This means you do not have the module installed. Try running "pip install -r requirements_(your platform).txt" (win if Windows, mac if MacOS). If you get an error for a specific module, try installing the others individually and run "pip install [problematic module]" last to see if that changes anything. If you still get an error regarding the module that won't install, that's probably an issue with the module itself.
Entering numbers when attacking on MacOS causes the game to crash
Don't enter numbers there... I don't know what's causing this at the moment :(
ToneChecker["Global"] throwing a KeyError
The contents of Pinori.ini are invalid. You'll need to delete it and re-run the game, where a new one will be created for you.
Non-Fatal Errors
This section will document bugs you are likely to come across that do not cause the game to crash, but just hinder the experience.
Attacks frequently missing (even on weaker enemies)
This is because I have yet to balance the damage formula. It's very quirky at the moment. Not necessarily a bug, it just makes gameplay more frustrating. The feminine urge to just abuse the God Mode quirk...
Stats resetting at random
Sometimes they do, sometimes they don't. Just when I thought v1 was done too...
Accidental Permadeath A (instant Game Over when encountering enemies)
I'm as confused as you are. My best guess as to why this is happening is because something's not reloading properly. As long as you don't save when your party is in a state where everyone is dead, you'll be fine if you reload the game. (I also rediscovered this issue because of the new feature explained below, but I'm pretty sure under rare circumstances it's possible without it.)
Accidental Permadeath B (instant Game Over on final boss)
This is a weird bug relating to a feature I recently added: a flag called --auto_continue. It basically tells the Game Over functions to automatically reload the game instead of asking you what you want to do (or in the final boss' case, exit the game). For some reason there's an unreasonably high chance that you'll get trapped in an infinite loop of the final boss monologuing and "Oh... I guess that's game over.". I'll have to have someone look into this for me...
Patched Issues
Issues that have been fixed or I'm confident have been fixed.
Population stays the same when switching areas
Original description:
A relatively minor issue I just spotted. Reloading the game fixes the population, but it shouldn't take a reload, it should fix it itself.
Cause: Nothing??? It fixed itself somehow. How ironic.
Items do not reload after a Game Over
This was because I programmed the item system to read directly from Inventory.ini and not use the in-game variable to store items. This has been fixed as of 5/22/2024. (It was surprisingly easy to reprogram, I was just lazy.) Changes are now only made to inventory.ini when saving.
No follow-up message after "You take a step forward..."
Original description:
Even I'M curious as to what's causing this. Most likely I missed a condition in the massive condition tree, so a very specific condition that I never accounted for is being met. I'll try to figure this out, but it'll be difficult.
Cause: Missing else statement (great job, me)
Stats resetting to their default when reloading the game
Original description:
My fault again. This is because a failsafe is going off; I have yet to figure out what's going on but I'm sure it's a simple fix. Hang in there!
Cause: flawed code (no shit!)
Returning to the Battle Menu after sending an invalid attack may confuse the game into thinking you're still in the Attack Menu
Original description:
Another really bizarre bug that I don't know how to patch. This has only sometimes happened to me, and I feel like it's just Python being Python rather than a fault of my own. About as "common" as "You chose Invalid input." and its other variants.
Cause: Python itself (hooray)
Solution: Require player to type a keyword to exit the attack menu, although this returns the player to BattleMenu() instead of BattleActions() because it apparently doesn't like that function very much.
Encountering an enemy that was already killed; HP is 0 or less
Original description:
This is a REALLY weird bug. Something has to be skipping past the stat initialisation function for this to occur, and I don't recall programming anything that skips it. I'm going to name this bug the "Corpse Encounter".
Cause: I have NO clue, but I haven't encountered this bug in ages. Hopefully it's not my "step mode" that's making the game more stable.
Infinite Yami
Somehow, some way, it was possible to infinitely trigger the Yami battle. How? Good question. Obviously, you can't anymore. Yay, no more level 55 with 400+ defense!
Solution: Give Yami her own key in Pinori.ini so that when she dies during an Omnicide route, said key is updated when the player saves and proceeding to Tanpopo Town is possible again.
That's all I have at the moment, but I will update this post with more as development continues.
Issues regarding Linux usage will NOT be documented.
Linux support is not on my mind as of now, so if any bugs you come across are because you're using Linux, I will not do anything to fix it at this time. I may in the future, but don't get your hopes up.