Open mlevison opened 3 years ago
Hm, with the system we have in place now it seems to me as if this is best implemented as yet another hidden score similar to gremlins.
I think this can not be implemented as using the gremlin system because
We can not implement it as per-round side effect because
Ok - in theory this can occur multiple times. If we add another "hidden mechanism" we should design so I could rework at a later date for newly weird and random things.
If we add another "hidden mechanism" we should design so I could rework at a later date for newly weird and random things.
You mean building it so that it can be re-used for future ideas?
I'd strongly advise to not predict the future and don't build stuff for ideas you haven't had yet.
Let me know when you'd like to talk about this or if I should implement s.th.
I'd strongly advise to not predict the future and don't build stuff for ideas you haven't had yet.
It's funny - I'm normally the one giving people that advice. Let's just stick to the plan and make it a hidden effect score similar to gremlins.
@Xiphe I'm finally at the stage we're I'm ready to code this.
The scenario. In round 7 - their product goes live and so by round 8 they could be hit by production support issues.
Is this best handled as a per round side effect in rounds 8 and higher? Or a gremlin? or Magic?