Reply to thread

Message: <blockquote data-quote="loverdrive" data-source="post: 8234774" data-attributes="member: 7027139">There was a structure, but it lead to "scores" often being two or three session long, so I've decided to drop it. Freeplay -> Score -> Downtime works really well when it all can be handled within a single session, but I feel like it starts to feel apart.There is a possibility I'll add it back, though. I generally start my design process with throwing out things that I'm not 100% sure I'll need.The most limiting factor of downtime is, well, time. Yeah, you can spend days and weeks tinkering with a long-term project, but Tot-Amon wouldn't wait for you to execute his schemes.When both I or someone else ran the game I've never heard that someone had a problem with no downtime cap. The problem I ran into and now looking for a way to address is that people tend to not take downtime at all.I didn't find a use for it, honestly.I think it's boring <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />Services and equipment list is something that is in progress, but it wasn't on my priority list for playtesting materials.</blockquote>