Re: [s-d] [s-b] Amended Proposal "Rule Tag"

[Daniel Lepage <dpl33@xxxxxxxxxxx>]

On Dec 16, 2006, at 5:07 AM, shadowfirebird@xxxxxxxxx wrote:

> Amended Proposal "Rule Tag":
>
> Create a new rule "Elements":
> {{
> There is an attribute "element".  Its scope is all players; its range
> is the four values: "Earth", "Air", "Fire", "Water"; its default value
> is "Earth".

I kind of like Iain's style of attribute definition:
=== Element ===
Element is an attribute with the following properties:
* Scope: Players
* Range: Earth, Air, Fire, or Water
* Default Value: Earth

> Players may change their element with an "element change" game action.

If you just say "Any player may change eir element", this implicitly  
makes it a game action.
If you say "Any player may change eir element, but only once per  
nweek and only before the end of nday 8.", then you also eliminate  
the need for the next two sentences.

Or, better yet, you could make this a rule tag action, in which case  
it would fall under your later rule that says that rule tag actions  
in general can't be taken if the nday is greater than 8.

> Only one element change game action can be made by a player in an
> nweek; subsequent such declarations in the same nweek will be ignored.
>
> Element change game actions must be made before the end of nday 8.
> [[So that the rule tag moderator has a chance to do his thing.]]
> }}
>
>
> Create a new rule "Rule Tag":
> {{
> [[DEFINITIONS]]
> A "rule tag object" is a game object.  It can be referred to as an
> "RTO".  Each RTO has a unique name.

I've always preferred pluralizing the definitions, as in "Rule tag  
objects are game objects". Also, you could combine the nickname into  
the definition, as in "Rule tag objects, or RTOs, are game objects."

> There is an attribute "rule tag location".  Its scope is all players
> and all RTO's.  Its range consists of the list of rule numbers, and
> the value "null".  Its default value is null.  The rule tag location
> may be referred to as the "RTL".  The rule pointed to by an RTL may be
> referred to as the "RTL rule".

I don't think I like this syntax. I'd rather make it not an  
attribute; instead say "Every player and every RTO has a rule tag  
location (RTL), which is either an existing rule or the special  
location "null". All objects are initially at null."

> Players with an RTL of null cannot lose points as a result of rule tag
> actions or rule tag objects [[because they are not on the "game
> board".]]
>
>
> [[GAME ACTIONS - GENERAL]]
> A "rule tag action" is a game action which forms part of the game  
> of rule tag.
>
> All rule tag actions must be made before the end of nday 8.  [[To give
> the rule tag moderator a chance.]]

I'd prefer "rule tag actions cannot be taken after nday 8 of each  
nweek". That makes it clear that it applies to each nweek separately.

> All rule tag actions may be made by emailing the rule tag moderator
> with a subject line starting "[rule tag]".  They may also be made by
> the normal method of declaring them on the public forum.
>
> Each player may only make one rule tag action of each type in a single
> nweek.  Only the last rule tag action ey makes of a given type in a
> given nweek shall be counted as having meaning in the rules.

There is no spivak pronoun "ey", though this is a common mistake. The  
word you want is "e", which replaces "he" or "she". Also, referring  
to the "type" of a rule tag action is a bit ambiguous. Maybe you  
could formalize this? "Some Game Actions are Rule Tag Actions. Each  
Rule Tag Action has a type." Alternately, don't make them a form of  
Game Action, because they are fundamentally different. Create special  
objects, "Rule Tag Events" or something (that's a bad name, but I  
can't think of a better one right now). Then each event has a type,  
and each player may declare up to one event of each type during a  
given nweek; the last one each player declares in each type is what  
takes effect at the end of the nweek.

> The Rule Tag Moderator decides whether any given ruletag action is  
> valid.

Does this give the moderator the power to cancel actions that would  
otherwise be valid? E.g., can I try to enter the game from null and  
be rejected on the Moderator's whim?


I think this next section could be phrased more elegantly. I would  
separate the linking of rules from movement. Make a section that says  
that two rules are "linked" if one defines a term used in the other,  
or vice versa, and put all the extra text defining what that means in  
that section. Then say (using my rule tag event notion from above):
{{
The following are rule tag events:
== Enter ==
Type: Location
Restrictions: The player is on null.
Targets: A rule of the player's choice.
Effect: The player moves to that rule.

== Move ==
Type: Location
Restrictions: The player occupies a rule.
Targets: A rule of the player's choice that links to eir RTL
Effect: The player moves to that rule.

== Evacuate ==
Type: Location
Restrictions: The player occupies a rule.
Targets: None.
Effect: The player loses 10 points and moves to null.

== Grab ==
Type: Inventory
Restrictions: None.
Targets: A number of points in the possession of the player, and a  
RTO within the player's RTL.
Effect: The player attempts to grab the targeted object (see below)

Etc.
}}

> [[GAME ACTIONS - MOVE]]
> Players may make a "rule tag move" action.  This is a rule tag action
> [[obviously]].  Valid moves are as follows:
>
> (i) If eir current RTL is null, then ey may choose any rule number.
>
> (ii) Ey may choose the rule number of a rule that defines one of the
> game terms used in eir current RTL rule.
>
> (iii) Ey may choose the rule number of a rule that uses one of the
> game terms defined in the current RTL rule.
>
> (iv) Ey may choose null.  [[But this costs you points, see below.]]
>
> For the purposes of rule tag, a "game term" is a term used in the
> rules with one specific meaning within the game.  A specific meaning
> can have more than one game term associated with it, but a game term
> can only have one specific meaning.
>
> For the purposes of rule tag, a rule that defines a game term is a
> rule that explains what that specific meaning is. More than one rule
> can define a single game term.
>
> As part of the rule tag move action, the player must clearly show eir
> current RTL, new RTL and the game term that links them.
>
>
> [[GAME ACTIONS - GRAB/DROP]]
> A player may make a "rule tag grab" rule tag action on an RTO in the
> same RTL as the player.  This must include the name of the RTO ey
> wishes to grab and how many points ey wishes to spend.  Ey may not
> declare more points than ey has.  Ey may not declare less than 0
> points.
>
> If an RTO has been successfully grabbed by a player then it moves
> whenever the player moves, and to the same RTL.  The player is said to
> be in "possession" of the RTO.
>
> If the player has possession of an RTO then ey may make a "rule tag
> drop" rule tag action.  Ey must name the object ey is dropping.
>
> [[END OF TURN]]
> At the end of the nweek, after passed proposals have been enacted into
> the rules, the rule tag moderator changes the state of each player and
> object as follows and in the order shown:

"after passed proposals have been enacted" is tricky - it means the  
moderator has to wait until the admin updates the ruleset and  
restarts the clock before posting these results. It also means that  
if the rules changed that nweek, the moderator has to redo any  
calculations e did during the Voting period, which negates the  
benefit of disallowing actions during that time. Resolving actions  
before proposals would probably be a good idea.

> 1) Players who made rule tag move actions have their RTL changed to
> their new location.
>
> 2) Players who made rule tag drop actions are no longer in possession
> of the RTO that they dropped.
>
> 3) All rule tag grab actions are resolved.  Firstly, any grab actions
> where the player and the RTO have different RTL's are declared invalid
> and play no more part in the game.
> Then, for each RTO in turn:
> (i) If the RTO is in possession, it is dropped, and nothing else
> happens to it this turn.
> (ii) Otherwise if there is only one grab action for the RTO, then the
> player making the grab action gains possession.
> (iii) Otherwise, if of all the players who declared a grab action on
> this RTO, there is a player who declared more points than any other;
> then that player gains possession and loses the number of points ey
> declared, so long as he can actually pay out that many points.
> (iv) Otherwise, nothing happens.
> [[So if two players make a grab for the same, non-possessed RTO then
> the one that declared the most points gets the RTO and loses the
> points; and nothing happens to the other.]]
>
> 4) Players on the same (non-null) RTL as another player lose or gain
> points based on their elemental precedence.  This works as follows:
> Earth beats Water; Water beats Fire; Fire beats Air; Air beats Earth;
> all other combinations are neutral.
> Whenever a player has a losing elemental precedence to another player
> then ey loses 15 points; these points go to the player with the
> winning elemental precedence.  Where there are more than two players
> on an RTL, each combination of players is honoured.
> [[So given three players with elements Earth, Air and Fire, on the
> same RTL: Air gives Fire 15 points; Earth gives Air 15 points.]]

I feel like this should be in a different rule. The subgame breaks  
into a few components: 1) Linking rules, 2) Moving between rules, 3)  
Grabbing/Dropping objects, 4) Elements, and 5) Basketball. I feel  
that putting each in its own rule, or at least in its own subsection,  
would make the subgame as a whole easier to understand.

> 5) Players who moved to null this turn lose 10 points.
>
> 6) Players whose RTL no longer points to a valid rule have their RTL
> set to null and lose 25 points.
>
> 7) Players whose RTL points to a rule that has just changed lose 10  
> points.
>
>
> [[MISCELANEOUS]]
> Rule tag is a sub-game, if such a term has meaning in the Rules; but
> where this rule conflicts with any other rule regarding sub-games,
> then this rule takes precedence.

What does this mean?

> }}
>
> Create a new rule titled "rule tag invalid paths"
> {{
> The following game terms are not valid for use as game terms in the
> game of rule tag: "Object", "Game Object", "Player".
> }}
>
> Create a new rule titled "rule tag moderation":
> {{
> There will be a post titled "Rule Tag Moderator".  Ey may also be
> known as "The Bearer of the Wobbly Hat of Justice."
>
> Restrictions:
> 1) The rule tag moderator may not make rule tag actions, except to
> rule tag move to null.
> 2) Should the post holder ever have an RTL that is not null, ey must
> move to null as soon as possible.
>
>
> Responsibilities:
> 1) To post a notification to the public forum no earlier than nday 9
> and no later than nday 2, showing:
> (i) valid rule tag actions made by each player.
> (ii) Each players' current RTL and element.
>
> 2) To post a notification to the public forum no later than nday 2  
> showing:
> (i) The changes in score of each player due to rule tag.
> (ii) The location of each RTO and who, if anyone, is in possession  
> of it.
> (iii) Any other rule tag specific changes of state.
>
> [[Note that (1) and (2) could be a single post.]]
>
>
> Powers:
> 1) The rule tag moderator is the arbiter as to who loses points and
> gains them as a result of the game of rule tag.
> 2) The rule tag moderator is the arbiter of what constitutes a valid
> rule tag action and what the result of a rule tag action is.
> 3) The rule tag moderator is the arbiter of any other game event or
> object solely regarding the sub-game of rule tag.
> 4) The rule tag moderator does not pay points for moving to null.
> In the exectution of these powers ey must not break the Rules.
>
>
> Censure: If in a given week the rule tag moderator fails to post the
> required notifications by nday 2, ey shall lose 20 points.

No punishment for missing the nday 9 update?

> Award: 10 points per week.
> }}
>
> Create a new rule "rule tag basketball":
> {{
> There is an RTO "rule tag ball".
> There is an RTO "rule tag goal".
>
> At the end of the nweek, after passed proposals have been enacted into
> the rules, if a player is in possession of the ball and in the same
> RTL as the goal then the following things happen:
>
> 1) The player in possession of the rule tag ball gains 25 points.
>
> 2) Both the rule tag ball and the rule tag goal become no longer in
> possession of any player; they are relocated to two different
> (non-null) RTL's, chosen at random by the rule tag moderator.
> }}
>
>
> The rule tag moderator must assign random (but non-null) starting
> RTL's to all RTO's.
> _______________________________________________
> spoon-business mailing list
> spoon-business@xxxxxxxxx
> http://lists.ellipsis.cx/mailman/listinfo/spoon-business

Daniel Lepage
dpl33@xxxxxxxxxxx



_______________________________________________
spoon-discuss mailing list
spoon-discuss@xxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/spoon-discuss