Saturday, July 22, 2017

Proposal: You’re It!

Self-killed. Failed by card.

Adminned at 24 Jul 2017 15:52:50 UTC

Change the “Tags” rule to

Tags are put in the title of the votable matter with the format “[X]” where X is the tag. Votable matters with tags in their titles are considered to have those tags. Votable matters cannot have tags which are not defined anywhere.

Votable matters have at least one tag, if no tags are given the defaults are used. Proposals default to [Dynastic] and [Gamestate], DoV default to [Victory] and [Gamestate] and other Votable matters default to the [Gamestate] tag. CfJ default to every tag.

Some valid tags are:
*Victory
*Dynastic
*Gamestate
*Core
*Appendix

Tags, other than [Victory] and [Gamestate], correspond to rules which are not subrules of any rule. For each tag which corresponds to a section in the ruleset, votable matters can only make changes to that tag’s corresponding ruleset section if they have that tag. Votable matters can only affect the gamestate if they have the [Gamestate] tag. Votable matters can only give a Pactmaker victory if they have the [Victory] tag.

A proposal which specifically names a rule’s title to change and doesn’t have the correct tag for that rule is considered to have the correct tag for that rule. In case multipul rules have the same name but are in different tag spaces (such as a Dynastic rule “Pactmakers” and the Core rule “Pactmakers”) the order of precedence for which tag is added, and therefore which rule is edited, is [Dynastic], [Core], [Appendix]. So if a proposal were to name a rule to change that does not appear in the Dynastic rules but there are two rules with the same name in both the Core and Appendix rules, it would change only the Core rule.

The partial list of valid tags is maintained as follows:

  tags, other than [Victory] and [Gamestate], which do not have a section in the ruleset they correspond to are not valid and should be removed from the list.
  rules which don’t have any subrules and don’t have a corresponding tag should have a tag added to the list. Adding a tag to the list is done by taking the section name that needs a tag and adding it to the list of valid tags. Then if the most recently added tag has the word “Rules”, remove that word from the tag unless that is the only word in the tag.

Changed some problems that were recurring with the tags rule.
Might be a good idea to use http://cemerick.github.com/jsdifflib/demo.html to look at the changes.

Comments

Madrid:

22-07-2017 16:59:37 UTC

Ah. I see the problem, same name for multiple things.

I think it’s a very good catch. Not related to the proposal itself, but I believe we should figure out a way to write the same stuff but with less words. Combos and Tags are great candidates imo for Core Rules, but they’re pretty huge.

But that polish can be done after we cover the holes. for

card:

22-07-2017 18:09:41 UTC

Yeah I was thinking about simply rewriting all of the nonDynastic rules since they seem to get larger and larger.

pokes:

22-07-2017 19:10:43 UTC

Would it be an okay compactification of Tags to only have [Core], where without the tag a Proposal can’t touch Core or Appendix? That could shrink this quite a bit, and how often do we really want control as fine-grained as we have it now?

pokes:

22-07-2017 19:14:58 UTC

The Tags rule in that case could be simply:

When a Proposal is enacted, any steps that would change text in the Core or Appendix sections of the Ruleset are skipped, unless the title of the Proposal contains “[Core]”.

 

card:

23-07-2017 02:50:19 UTC

I think that sounds like a better idea.  against