| Doig, Gavin on 11 Jan 2002 13:10:57 -0000 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| RE: spoon-discuss: Re: spoon-business: Proposal: Titles, and a be tter bandwidth limit |
> In any event, I'm sure that you can come up with a way to attempt to
> circumvent that as well. Doesn't matter.
>
There's no way you can stop a proosal from being able to (change the game in such a way that it is able to) change as much as it likes.
> My point is I'd rather deal with
> the odd player trying to circumvent what's regulated, than to attempt to
> manage proposal spam via deterrence.
>
It wouldn't be the odd player. It'd be a lot of the players, a lot of the time. Being able to do more than 1 change per proosal isn't some weird arcane thing that only happens once in a while; it's absolutely essential in any number of cases, unless you want to submit dozens of tiny proosals instead, which may not be a sensible thing to do if one change wouldn't make sense without another. On the current ballot, proosals 222, 230, 232, 233, 235, 236, and 238 all contain more than one change (some of them are a mix of rule and gamestate changes). That's 7 out of 26 proosals. Yes, some of them are long, but p233 certainly isn't, and anyway, just because a proosal is long, doesn't mean it's *too* long. Sometimes you just want to change or add a lot of stuff.
Like I say, though, people proosing too much stuff isn't likely to be a problem. Most nomics end up having problems with lack of activity, not with being overactive.
uin.
DISCLAIMER:
This message is intended only for the use of the person(s) ("the intended recipients(s)") to whom it is addressed. It may contain information which is privileged, proprietary and/or confidential within the meaning of applicable law. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender of this message as soon as possible.
The views or opinions expressed in this message are those of the author and may not necessarily be the views held by Azurgroup Limited