Can definitely recover from -- by making stable decisions. Or Confident decisions, which raises those stats in the main game.
This is literally the opposite of what you said and to what i was responding, which was "
Recover? Can't. Cracking causes stat changes that are permanent." and that it's
designed to be a downward spiral (where losing stability makes it even easier to lose it even further) eventually leading to a game over.
You gave no indication you're planning to change this design, so it shouldn't be a surprise you're getting feedback on what currently is, and not of what may or may not be.
You're basing this on no evidence. You can gain stability without being fugly, plain, average or boring.
I think you've misunderstood what i wrote. That wasn't a claim that in your game stability is tied to character's appearance, but an analogy using a theoretical, different game distilled to a single attribute. I thought it'd make it easier to get the point i was making, but evidently i was mistaken.
You can also build a confident character that has a higher number of 'cracks' before game over as well. And I think it should be self-evident how Confidence can be gained by doing things that (in alignment with what your post said) are 'fun'.
Alright, so let's put it this way: you say that the player can avoid game over by making decisions which prioritize Confidence and Stability. But does the game allow the player to win it with character who
doesn't have these attributes high (and maybe even in the negatives) as a result of making certain choices over the course of character creation?
Because if it doesn't, then we're back to the very point i was making -- if the game effectively enforces a certain build/combination of attributes in order to be playable, then the other "options" are nothing but traps for the player to avoid. (or fall into and find out they can't proceed) It puts the character creation process on rails.
TLDR - The game is in development. The code is new. The goal is to make a fun game but one that also has consequences. We're working on it and it will improve.
That's precisely why i'm offering you feedback on the code and design you're producing. To highlight what you seem to think is fun is potentially having the opposite effect, and as such it might warrant a trip back to the design board.
