Saturday, November 01, 2014

Emergency maintenance required this weekend

Hi, everyone, your friendly neighborhood hosting sponsor here.

Dreamhost has notified its customers that they will be forcibly upgrading everyone to a minimum PHP version of 5.4 starting on Monday. The recent brokenness here of a few weeks ago was caused by their first attempt to do this, but that time was reversible; this time will not be. So, we’re going to have to upgrade our software this weekend.

Upgrading the main blog will hopefully not be a huge ordeal; I believe ExpressionEngine has a solid upgrade path to their most recent version, and I already have a license for it.

The larger problem is the wiki. A few other folks and I have talked about upgrading it sporadically over the years, but I never acted on it because it wasn’t terribly pressing. Now it is and I want to shoot my past self.

Our MediaWiki version is ancient, and it was, like, the last version before WikiMedia started implementing a consistent upgrade path. I believe the general consensus in the past was that the most efficient thing might just be to copy pages over manually from our current version to a new version installed next to it. But now this is complicated by the fact that the wiki will probably stop working on Monday. The path forward is probably to compile our own copy of PHP 5.2 and have the old wiki use it for the transition period. That’s going to be fun, but doable.

So, in addition to just informing everyone of all this, my purpose here is to ask when the best time this weekend would be for some hopefully brief downtime of the blog. Sunday night is probably the best time for me, but I’m flexible; if that’s a bad time for any current gameplay, I can start sooner.

I’ll be keeping tabs on this post, I’ll be on in the IRC channel all weekend, and I’m available by email at .(JavaScript must be enabled to view this email address) .

Any input or suggestions are welcome. I’m very sorry this is so last-minute; if I’d paid more attention I might have started this sooner.

Thursday, October 30, 2014

Proposal: Encouraging Even More Proposals

In the rule “List of Proxies”, change the text

The author of any pending proposal with at least two FOR votes on it, or any proposal that became enacted in the last 24 hours, may cause McGraft to attempt to take any rules-defined action.


The author of any pending proposal with at least two FOR votes on it, or any proposal that became enacted in the last 24 hours, may cause McGraft to attempt to take any rules-defined action. If McGraft’s action affects any gamestate information, its author may not cause McGraft to act again for the same proposal. Players should record which proposal they’re using in a GNDT comment for bookkeeping purposes.

Thursday, October 30, 2014

Markdown Tip

Tip: Markdown formatting seems broken, but if you write your post in Markdown elsewhere and use Markdown to generate HTML, formatting “None” (instead of “XHTML”) seems to work out quite well.

I think that composing the post elsewhere may also have the advantage that, if you click “Make New Post” only after you’re done, the timestamp on the article will be close to the actual time you post. I’m not sure whether this is actually a problem—testing it now by leaving this draft open in EE for half an hour.

Proposal: There are N Balls

Self-killed. -Bucky

Adminned at 31 Oct 2014 20:38:07 UTC

Amend Rule 2.2, "The Ball", to read:

There are N Balls. Some Players may have a Ball, tracked in the GNDT field "Ball" with a single "O". By default, Players do not have a Ball, tracked in the GNDT field "Ball" with a single "-".

Some Players may be Assisting, and by default are not Assisting: Assisting Players are tracked in the GNDT field “Ball”, with a single ":". When a Player gains a Ball, they cease to be Assisting, if they were Assisting.

If a Ball is Out of Play, any Player may roll DICEN, where N is the number of Players. On a roll of K, that Ball is given to the Kth Player in the GNDT.

If a Player with a Ball has no position, that Ball immediately becomes Out of Play.

The Balls are completely fungible. For example, if two players were to instantaneously trade Balls, the gamestate would not have changed.

Rename Rule 2.2 to "The Balls".

For each EVC, take the last line of the form "Balls: " followed by a single positive integer less than the number of players. Replace "N" in "There are N Balls" in Rule 2.2 with the median of the numbers in those lines.

In Rule 2.2.1, replace the middle paragraph with:

When a Player Kicks or Loses a Ball to another Player, ownership of that Ball is transferred to the other Player.

In Rule 2.6.1, "List of Proxies", replace "Shooting the Ball" with "The Method of Scoring".

In Rule 2.10, "The Method of Scoring", amend the last paragraph to read:

Immediately after a player Shoots, the Ball they had becomes Out of Play.

Amend Rule 2.11, "Offside", to read:

If a Player Kicks a Ball to a Player that is not in the same Position or an Adjacent Position to the kicking Player, then that Ball becomes Out of Play.

Amend Rule 2.15, "The Throw-in", to read:

If a Player who has a Ball has had it for the entirety of the previous 72 hours, any Player may transfer that Ball to their own possession.

That was easier than I thought it would be.

Wednesday, October 29, 2014

Unmutexing the ball?

One gripe I have with the current rules is that there’s nothing much to do if you don’t have the ball (hereafter, if you are a non-carrier). The ball acts like a mutex for play. One idea for changing this:

Allow players to set instructions, in some restricted language, in the GNDT (“Play”, maybe?), which take effect immediately upon their acquiring the ball (subject to some safety conditions, e.g. to prevent infinite cycles). This would give non-carriers something to do (prepare their Plays), but would still keep ‘actual’ play centered on the ball, leaving the mechanics for the ball unchanged. Surely ideas roughly like this have been tried in past dynasties? My gut says it’s unlikely to work well, but I’m not sure.

I guess that would be creating play for non-carriers by introducing a level of metaplay. There are probably simpler alternatives where we just create new (non-meta) play for non-carriers.


Ill Be Back Eventually

I really haven’t been keeping up with this Dynasty, so I’m idling myself. Quorum remains four.

Tuesday, October 28, 2014

Proposal: Proposal Incentives, Proxy Style

Times out and passes 6-0. -Bucky

Adminned at 30 Oct 2014 19:43:09 UTC

Add the following text to the end of the rule “List of Proxies”:

There is a Proxy named McGraft.  The author of any pending proposal with at least two FOR votes on it, or any proposal that became enacted in the last 24 hours, may cause McGraft to attempt to take any rules-defined action.

The attempt may fail, though, if the rules don’t allow McGraft to take that action.
Write more proposals! They’re free!

Monday, October 27, 2014

Proposal: McDefense Defends

Passes 4-0 with Quorum FOR. -Bucky

Adminned at 28 Oct 2014 16:21:06 UTC

Set McDefense’s Position to Defense.


Proposal: Ball Handling and Position

Passes 5-0 with quorum FOR. -Bucky

Adminned at 28 Oct 2014 01:11:24 UTC

In Rule 2.3, change the text “A Player may change their Position” to “A Player who does not have the Ball may change their Position”.

Add the text “If the Player with the Ball has no position, the Ball immediately becomes Out of Play.” to the end of Rule 2.2.

No running with the ball and no taking the ball to the bench

Proposal: Coach Proxy Clarification

Passes 5-0 with Quorum FOR after 12 hours. -Bucky

Adminned at 27 Oct 2014 15:44:48 UTC

Add the text “The Coach is considered to be a Player for this rule and its subrules.” to the beginning of the last paragraph of the rule “The Assistant Referees”:

The main effect of this is to extend the PROXY X comment requirement to the Coach

Sunday, October 26, 2014

Nomic^3 goes idle.

Nomic^3 hasn’t done anything in the last couple of weeks and goes idle.  Quorum drops to 4.

Friday, October 24, 2014

Proposal: Decouple Position from Shirt v3

Passes 5-0 with Quorum FOR.  Pre-comment revision was legal by one minute. Note that, not being a Dynastic Rule, this proposal failed to set the Proxy’s Position.-Bucky

Adminned at 26 Oct 2014 21:31:12 UTC

Amend rule 2.3, "The Number of Players", by replacing "Shirt" with "Position".

Amend rule 2.4, "The Players' Equipment", to read:

Each Player wears a Shirt with a single number from zero to 99, the number being tracked in the GNDT field “Shirt” and defaulting to zero. If a Player is wearing a zero Shirt, they may change it at any time. No two Players may wear the same Shirt, unless they are wearing zero Shirts.

The Coach may also wear a Shirt with a number that is either zero, or 100 plus a number a Player might have; the Coach may change their Shirt at any time.

Remove the first paragraph of rule 2.11, "Offside".

Amend rule 2.1, "The Field of Play", to read:

Players may have Positions on the Field, tracked in the GNDT. By default a Player has no Position. If a Player has no Position, they may change their Position at any time.

The Coach may also have a Position, which they may change at any time.

Positions are ordered relative to each other and are associated with a Side. The Sides are Defensive and Offensive. The Positions, in order, with their Sides, are:

  1. Goalkeeper (Defensive)
  2. Defense (Defensive)
  3. Midfield (Offensive)
  4. Offense (Offensive)

Only one Player may have Position Goalkeeper.

Two Positions are Adjacent if they occur in adjacent items in the above list. One Position is Towards the Goal (respectively, Away from the Goal) from another Position if the first Position occurs before (resp. after) the second in the above list, that is if the first Position's index in the above list is less than (resp. greater than) the second Position's.

These properties and relations of Positions (Sides, Adjacency, Towards and Away from the Goal) can apply by extension to Players in the obvious way. For example, a Defensive Player is a Player with Position on Side Defensive, and Adjacent Players are Players with Adjacent Positions.

Amend rule 2.2.1, "Kicking the Ball" to read:

If a Player has the Ball, they may attempt to Kick the Ball by making a GNDT comment naming a Player (other than themselves, and who has a Position) to be a target Player and rolling DICE9. If the result of the die roll is less than 8, the Kicking Player has Kicked the Ball to the target Player. If the result is 8, the Kicking Player has Lost the Ball to a random Player who has the target Player’s position (excluding the Kicking Player). If the result is 9, the Ball becomes Out of Play and is removed from any Player’s possession.

When a Player Kicks or Loses the Ball to another Player, ownership of the Ball is transferred to the other Player.

When a Player Kicks the Ball, if they are not the Goalkeeper, they may become Assisting. If a Player Kicks the Ball to a Player Towards the Goal from the Kicking Player, the Kicking Player may cause all other Assisting Players to cease to be Assisting. The Goalkeeper may never be Assisting.

If possible, replace "Kick the Ball" with "attempt to Kick the Ball" in the rule "The Assistant Referees" and its subrules.

Set the Positions of all Players and the Coach to be the positions they had according to their Shirts immediately before this Proposal's enactment.