Difference between revisions of "The Second Dynasty of card"

From BlogNomic Wiki
Jump to navigation Jump to search
(→‎Ascension: clarify a bit, and the GNDT order was just a coincidence (I mentioned it off-hand in the enactment in case I had any reason to delay or change my mind before DoVing))
(→‎Ascension: DoV link)
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''27 September 2018 -'19 October 2018''
+
'''27 September 2018 - 19 October 2018'''
  
 
== Ascension Address ==
 
== Ascension Address ==
Line 35: Line 35:
 
* [https://blognomic.com/archive/stay_on_target Stay on Target!] allowed players to target each other when running the MCP.
 
* [https://blognomic.com/archive/stay_on_target Stay on Target!] allowed players to target each other when running the MCP.
 
* [https://blognomic.com/archive/in_like_flynn1 In Like Flynn] expanded the Access mechanic.
 
* [https://blognomic.com/archive/in_like_flynn1 In Like Flynn] expanded the Access mechanic.
* [https://blognomic.com/archive/crown_joules Crown Joules] gave every player a GNDT-tracked Energy switch. If one player had more energy than any other player, they could win under this rule.
+
* [https://blognomic.com/archive/crown_joules Crown Joules] gave every player GNDT-tracked Energy. If one player had more energy than any other player, they could win under this rule.
 
* [https://blognomic.com/archive/resting_energy Resting Energy] set each player's Energy to 1 instead of 0, allowing for a win.
 
* [https://blognomic.com/archive/resting_energy Resting Energy] set each player's Energy to 1 instead of 0, allowing for a win.
  
 
==Ascension==
 
==Ascension==
  
When the proposal [https://blognomic.com/archive/resting_energy Resting Energy] passed, Kevan adminned it. This proposal increased everyone's energy to 1 from 0. As the win condition was to have more energy than every other player combined, Kevan's choice to assign this energy one player at a time with himself first meant that he was able to achieve victory.
+
When the proposal [https://blognomic.com/archive/resting_energy Resting Energy] passed, Kevan adminned it. This proposal increased everyone's energy to 1 from 0. As the win condition was to have more energy than every other player combined, Kevan's choice to assign this energy one player at a time with himself first meant that he was able to [https://blognomic.com/archive/token_ring achieve victory].
  
 
==Commentary==
 
==Commentary==
  
 
I was just a spectator but I'm personally very skeptic that the victory was formally possible. The sentence that was attempted to be abused was ''"set the energy of each program to the default."'', which I believe means that at the instant that the proposal is enacted, all of the energy of the programs are set to the default and then the admin just updates the gamestate-tracking elements (like the GNDT) to reflect that. On the same coin, if he enacted that proposal but ''didn't'' update the GNDT with the values, the game would still formally have those values changed, it's not like he has some godly power within the action of enactment to change the gamestate as he chooses (and even if he did, I still believe that it would have to have been changing all of the values at the same time and he couldn't do it any other way). Things that ''track'' the gamestate are very different from the actual gamestate itself. But anyways, that rant aside, I believe that it was actually a positive thing that he won because the dynasty had lost a lot of momentum (proposals had been sitting for 4 days without processing, for example) and I believe people had just gotten bored/demotivated with it. The game had gotten into Dormancy too. Still, I disagree how the victory was actually formally accomplished; but even Derrick, one of the other two players who FOR'd the DoV, also admitted to doubts about its legitimacy but also agreed with that it was better for the dynasty to just move on. Maybe coding is too boring/tedious to play with? I don't know. --[[User:Cuddlebeam|Cuddlebeam]] ([[User talk:Cuddlebeam|talk]]) 11:48, 20 October 2018 (UTC)
 
I was just a spectator but I'm personally very skeptic that the victory was formally possible. The sentence that was attempted to be abused was ''"set the energy of each program to the default."'', which I believe means that at the instant that the proposal is enacted, all of the energy of the programs are set to the default and then the admin just updates the gamestate-tracking elements (like the GNDT) to reflect that. On the same coin, if he enacted that proposal but ''didn't'' update the GNDT with the values, the game would still formally have those values changed, it's not like he has some godly power within the action of enactment to change the gamestate as he chooses (and even if he did, I still believe that it would have to have been changing all of the values at the same time and he couldn't do it any other way). Things that ''track'' the gamestate are very different from the actual gamestate itself. But anyways, that rant aside, I believe that it was actually a positive thing that he won because the dynasty had lost a lot of momentum (proposals had been sitting for 4 days without processing, for example) and I believe people had just gotten bored/demotivated with it. The game had gotten into Dormancy too. Still, I disagree how the victory was actually formally accomplished; but even Derrick, one of the other two players who FOR'd the DoV, also admitted to doubts about its legitimacy but also agreed with that it was better for the dynasty to just move on. Maybe coding is too boring/tedious to play with? I don't know. --[[User:Cuddlebeam|Cuddlebeam]] ([[User talk:Cuddlebeam|talk]]) 11:48, 20 October 2018 (UTC)
 +
 +
I was short on spare time this dynasty, but it did feel like the programming aspect increased the effort required to even cast votes, to the point where the game started flagging. You couldn't reasonably vote on a code-change proposal without taking time to paste it into the MCP and check that it worked - although in retrospect we should probably have addressed that in the ruletext, so that a code-change proposal couldn't enact until a second person had confirmed that it compiled. Glad that we gave this theme a good run, though. --[[User:Kevan|Kevan]] ([[User talk:Kevan|talk]]) 18:12, 5 December 2018 (UTC)
  
 
{{Dynastic Histories}}
 
{{Dynastic Histories}}

Revision as of 10:43, 22 January 2020

27 September 2018 - 19 October 2018

Ascension Address

The extinction left no life behind; all that remains are computers and possibly robotic “life”.

Repeal all Dynastic rules and change “Monolith” to “Flynn” and “Ape” to “Program”

Players

The following players were active at the start of the Dynasty:

Brendan*, card*, derrick*, Kevan*, Trigon, Zaphod

The following players were active at the end of the Dynasty:

Brendan*, derrick*, Kevan*, Trigon, Zaphod

Final Ruleset

Proposals of Interest

  • The Core Mechanic made a rule that was not meant to be followed; instead it would be code to be executed.
  • Code Monkey allowed players to run JavaScript from the Master Control Program using a special website.
  • Gigo gave each player Input and Output GNDT values, defaulting to the first two and last two letters of their names.
  • Clean Machine brought back cleanup proposals from the previous dynasty.
  • The Unemperor created a special case rule that changed the way Deferentials work.
  • Walls of Fire and Light gave each person a firewall, which was an 8x8 grid of characters.
  • Forty Two created a way to change GNDT values as output of the Master Control Program.
  • v0.1 created a very basic Master Control Program to read the GNDT.
  • needs more randomization expanded the Master Control Program to include some random generation utilities.
  • Clean Deterministic Hardware simplified how the MCP would run, and implemented random seeds.
  • Front Door simplified the way Input and Output worked.
  • dictionary of fire made more functions, relating to numberpads.
  • Stay on Target! allowed players to target each other when running the MCP.
  • In Like Flynn expanded the Access mechanic.
  • Crown Joules gave every player GNDT-tracked Energy. If one player had more energy than any other player, they could win under this rule.
  • Resting Energy set each player's Energy to 1 instead of 0, allowing for a win.

Ascension

When the proposal Resting Energy passed, Kevan adminned it. This proposal increased everyone's energy to 1 from 0. As the win condition was to have more energy than every other player combined, Kevan's choice to assign this energy one player at a time with himself first meant that he was able to achieve victory.

Commentary

I was just a spectator but I'm personally very skeptic that the victory was formally possible. The sentence that was attempted to be abused was "set the energy of each program to the default.", which I believe means that at the instant that the proposal is enacted, all of the energy of the programs are set to the default and then the admin just updates the gamestate-tracking elements (like the GNDT) to reflect that. On the same coin, if he enacted that proposal but didn't update the GNDT with the values, the game would still formally have those values changed, it's not like he has some godly power within the action of enactment to change the gamestate as he chooses (and even if he did, I still believe that it would have to have been changing all of the values at the same time and he couldn't do it any other way). Things that track the gamestate are very different from the actual gamestate itself. But anyways, that rant aside, I believe that it was actually a positive thing that he won because the dynasty had lost a lot of momentum (proposals had been sitting for 4 days without processing, for example) and I believe people had just gotten bored/demotivated with it. The game had gotten into Dormancy too. Still, I disagree how the victory was actually formally accomplished; but even Derrick, one of the other two players who FOR'd the DoV, also admitted to doubts about its legitimacy but also agreed with that it was better for the dynasty to just move on. Maybe coding is too boring/tedious to play with? I don't know. --Cuddlebeam (talk) 11:48, 20 October 2018 (UTC)

I was short on spare time this dynasty, but it did feel like the programming aspect increased the effort required to even cast votes, to the point where the game started flagging. You couldn't reasonably vote on a code-change proposal without taking time to paste it into the MCP and check that it worked - although in retrospect we should probably have addressed that in the ruletext, so that a code-change proposal couldn't enact until a second person had confirmed that it compiled. Glad that we gave this theme a good run, though. --Kevan (talk) 18:12, 5 December 2018 (UTC)

Dynastic Histories

Round One - Myke I - Lyndse I - Myke II - Kevan I - Anthony I - Est I - Kevan II - Damanor I - Kevan III - Cayvie I - Josh I - Keitalia I - SatyrEyes I - Metadynasty I - Cayvie II - Brendan I - Kevan IV - Knightking I - Chronos Phaenon I - TrumanCapote I - Knightking II - Quazie I - Simon I - AngryGrasshopper I - Rodney I - Aaron I - Josh II - Metadynasty II - Chronos Phaenon II - Excalabur I - Excalabur II - 75th Trombone I - Elias IX I - Metadynasty III - Angry Grasshopper II - Hix I - Thelonious I - Elias IX II - Rodney II - Clucky I - Doremi I - Chronos Phaenon III - Amnistar I - Clucky II - Amnistar II - Bucky I - Clucky III - Josh III - Kevan V - Hix II - Spikebrennan I - Jack I - Purplebeard I - Rodlen I - Yoda I - Amnistar III - Darknight I - Bucky II - Yoda II - Metadynasty IV - Arthexis I - Amnistar IV - Devenger I - Ais523 I - Ienpw III I - Qwazukee I - Klisz I - Metadynasty V - Bucky III - Wakukee I - Kevan VI - Ais523 II - Josh IV - Purplebeard II - Ais523 III - Ienpw III II - Klisz II - Lilomar I - Coppro I - Ais523 IV - Kevan VII - Brendan II - Alecto I - Josh V - Clucky IV - Purplebeard III - Kevan VIII - Ais523 V - Purplebeard IV - Yoda III - Bucky IV - Kevan IX - Bateleur I - Metadynasty VI - Coppro II - Ais523 VI - Cpt Koen I - Southpointingchariot I - Josh VI - Scshunt III - Quirck I - Clucky V - Bucky V - Kevan X - Josh VII - Kevan XI - Scshunt IV - RaichuKFM I - Larrytheturtle I - Skju I - Metadynasty VII - Purplebeard V - Spitemaster I - Josh VIII - RaichuKFM II - The Alien I - Benzene I - RaichuKFM III - Purplebeard VI - Kevan XII - Ayesdeeef I - Bucky VI - Kevan XIII - Josh IX - Mideg I - Kevan XIV - Brendan III - Kevan XV - Tantusar I - Josh X - Kevan XVI - Thrawn I - Brendan IV - Kevan XVII - Moonroof I - RaichuKFM IV - Larrytheturtle II - Brendan V - Kevan XVIII - Brendan VI - RaichuKFM V - Kevan XIX - Brendan VII - Kevan XX - Viv I - Pokes I - Sphinx I - Madrid I - Pokes II - Madrid II - Metadynasty VIII - Axemabaro I - Diabecko I - Kevan XXI - Diabecko & Card I - Kevan XXII - Derrick I - Card I - Madrid III - Card II - Kevan XXIII - Pokes III - Kevan XXIV - Trigon I - Derrick II - Kevan XXV - Derrick III - Farsight I - TyGuy6 I - Pokes IV - Madrid IV - TyGuy6 II - Kevan XXVI - The Duke of Waltham I - Josh XI - Clucky VI - Naught I - Metadynasty IX - Kevan XXVII - Josh XII - Clucky VII - Josh XIII - Bucky VII - Josh XIV - Kevan XXVIII - Lemonfanta I - Clucky VIII - Josh XV - Misty I - ais523 VII - Josh XVI - Kevan XXIX - Trapdoorspyder I - Metadynasty X - Brendan VIII - Brendan IX - Zack I - Misty II - Josh XVII - MadisonSilver I - Josh XVIII - Kevan XXX - Lendunistus I - Josh XIX - SingularByte I - Trapdoorspyder II - Bucky XIII - JonathanDark I - Trapdoorspyder III - Habanero I - JonathanDark II - Misty III - Metadynasty XI - Josh XX - Lemon II - Kevan XXXI - Josh XXI - Clucky IX - Vovix I - JonathanDark III - Zack II - JonathanDark IV - Josh XXII