So I'm planning out a project to make a simple text adventure game (think of an old Goosebumps choose your own adventure book) and I've got started with some basic signup/login features and character creation.
Before advancing any further I've been working on my ERD and trying to simplify it.
The main loop of the game will be within the Story/Storyline/Option associations.
Story being the container for all of the storylines. I am planning 3 different stories based around your character's background.
StoryLine being the dialogue presented at each new step of the story.
Option being the User choice's that navigate you to different storylines (with certain options being able to hop into different a Story entirely)
Each Story will have 2 possible EndStates, a good and a bad.
So an EndState will belong to Story, but the final option picked along the Storyline will be what leads you to the EndState.
So EndState should also belong to Option I believe.
So my main question here is, would Option HAS_ONE endstate, or would it HAS_MANY? And if that's the case, then should Story just has_one end_state, through option?
Sorry if this is a little contrived, wanted to give some context. Any other tips or opinions for my current layout would be greatly appreciated!
