Thursday, October 25, 2012

Proposal: That’s Enough

Self-killed. Failed by Kevan.

Adminned at 26 Oct 2012 02:11:58 UTC

Add a new rule titled “Numeric Limits”, with the following text:

This Rule takes precedence over other Dynastic Rules, unless otherwise specified by another Rule.
Whenever a change to a numeric Gamestate data would cause it to be over the maximum value, make it the maximum value instead. Also, whenever a change to a numeric Gamestate data would cause it to be below the minimum value, it is the minimum value instead.

So we don’t have to state it in every numeric implementing rule.

On a side note, if I wrote just “Whenever a change to a numeric Gamestate data would cause it to be over the maximum (or below the minimum) value, it is the maximum (or minimum) value instead.” would it work, or would it be ambiguous enough for exploitation?

Comments

Josh: he/they

25-10-2012 07:52:50 UTC

for

Cpt_Koen:

25-10-2012 10:42:11 UTC

Doesn’t that mean, for instance, “if a change causes the Public Opinion on a subject to be 150, then the maximum for the Public Opinion on that subject is 150 instead of 100”?

IceFromHell:

25-10-2012 12:31:09 UTC

Hum… I guess you’re right, it’s ambiguous anyway… I’ll try again.

against

Bucky:

26-10-2012 06:13:25 UTC

Isn’t this already in the glossary?