EmbeddedMan
commented
3 years ago Oh, I LOVE this idea David. You win by not being embarrassed and not making your wife/daughters embarrassed by you. And yes, this is absolutely appropriate to discuss in an issue. Issues do not have to directly result in code changes. They can simply be the team working through the best answer or solution to a question. It's just a good way to organize "the team's" thoughts on the project.
This issue won't directly result in code changes. But it will make us create other issues that will cause code changes. For example, based on this direction one issue might be "Add state information to allow the player to need to turn the soldering iron on before they can burn themselves on it (even if they leave the room and come back)". Stuff like that.
I like all of your ideas above, and think they should all go into the game. It needs a unified feeling to the content, which it doesn't have yet. This could be the ticket to making it fun.
I think the design would be easier if we had a sense of the overall objective of the game.
The way it's written now it would be easy to make it into a game of avoiding humiliation. Since a lot of the ways to lose involve some sort of embarrassment (losing in minecraft, annoying the birds, falling asleep in hottub etc.). Having teenage daughters and a wife at home create ample opportunities for being an embarrassing dad and its something we can both relate to (except for Isabella not being a teenager). It also makes it a challenge to be cool, because no one ever thinks their dad is cool.
Possible ways to win if we go this route:
And more ways to lose:
I think going this route wouldn't involve much change to what we have already but it probably brings up other challenges as well. Like, if we're trying to be funny then that takes effort.
If we went the route of an adventure or horror game we'd have to make some changes but then we could lean on some of those cliches and tropes.
Is this an appropriate issue by the way? Or are they just for technical issues?