Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[FallacyofUrist]

<WARN> GATECRASH DETECTED
<PROTOCOL> LOAD COUNTERAGENTS {0...7}
<ERROR> {2} AGENTS CORRUPTED
<PROTOCOL> NETWORK LOCKDOWN
<PROTOCOL> COUNTERAGENT DIRECTIVE - NETWORK PURGE
<LOG> SET AGENT ELIMINATION - TRUE



Subforum's been dead for like two weeks now, so here's an experimental small-scale mafia.

You are advanced AI Agents operating within a Network. Five of you are Counteragents, unaware of the identities of the other Counteragents. The other two players are Corrupted Agents, aware of the identities of the other Corrupted Agents, and able to communicate privately.

Your objectives are a bit less standard.

The Counteragents win when both the Corrupted Agents are deleted, and lose when all the Counteragents are deleted, OR when each of the Network Nodes lose all Integrity.

The Corrupted Agents win when all the Counteragents are deleted, OR when each of the Network Nodes lose all Integrity. They lose when they are both deleted.

Spoiler: Roles and Abilities (click to show/hide)

Roles and Protocols:

Each role is a specific, specialized type of Agent, either a Corrupted Agents or Counteragent.

Abilities in this game are called Protocols. Each role will possess at least one Protocol, though the typical number of Protocols a role possesses will be somewhere between two and three.

You may use any number of Protocols in a given Network Cycle. You may even re-use the same Protocol multiple times if it is not invalid to do so. This is allowable because most Protocols will cost Energy to use. Each role has a given amount of Energy attached. If you lose all your Energy, you are deleted. You also cannot use more Energy than you actually have.

Due to the Network Nodes mechanic, many Protocols will not target a player directly, though some may still be able to.

Example Protocols:

<Data-Gathering> (**) Access Traffic Logs [node]: You read the traffic logs of a given Network Node, and learn which players entered that Node this Cycle.
<General> (***) Fortify Firewall [adjacent node / local node]: You install hardening scripts to secure a selected Network Node. It cannot lose Integrity this Cycle. If you are present at that Node, the cost of this Protocol is reduced to (*).
<General> () Transfer Power [player]: Choose an amount of Energy that you possess, up to (***). You connect to your target player, and transfer Energy. You lose that much Energy, and they gain that much Energy. This ability will fail to grant them the Energy if they are not within [adjacent node / local node].
<High-Priority> (1 Charge, ***) Fara-Dayl Cage [local node]: You block all routing ports into and out of the Network Node you are currently present at. It cannot be exited or entered this Cycle, and you learn all players present at that Node.

Resolution Notes:

Protocols resolve in this order.

Passive Protocols
High-Priority Protocols
Node Entrance/Exit
Interference Protocols
General Protocols
Integrity-Damaging Protocols
Data-Gathering Protocols
Special Protocols

The large majority of Protocols will belong to Interference, General, Data-Gathering, or Passive. A High-Priority Protocol will have some function that fits within the other sections, but belongs to that section instead due to its boosted resolution priority.

Protocols within the same category resolve simultaneously.

Self-Exhaustion Logging:

In the event that a player uses up all their Energy during a Cycle, and they do not lose Energy during that Cycle through any means other than using it for their Protocols, they may post one final message during the start of the next Cycle. The message may include information gained during the previous Cycle.

Spoiler: The Network (click to show/hide)

The Network:

The Network is a structure composed of many linked Network Nodes. Each Network Node has a given amount of Integrity. If a Node loses all its Integrity, it is destroyed and all the links it has to other Nodes are severed.

If a Network Node is linked to another Node, those Nodes are adjacent.

A given player can be present at a single Node. Each Cycle, each player may choose to enter any Node, becoming present at that Node at that stage of the Protocol resolution. This does not cost any Energy to do. During the first Cycle, all players must do this. The Node a player is present at is referred to as that player's local Node.

If a Node is destroyed while a player is at it, that player must choose to enter a non-destroyed Node during the next Cycle.

Network Design:



A: Data Node. No effects. 2 Integrity.
B: Data Node. No effects. 2 Integrity.
C: Power Conduit Node. A player that ends their Cycle present at this Node regains 1 Energy. 3 Integrity.
D: Load-Bearing Node. If an adjacent Node would be destroyed, this Node is destroyed instead, and any loss of Integrity which would cause that is negated. However, if this Node is destroyed in any other way, all adjacent Nodes lose 1 Integrity. 2 Integrity.
E: Data Node. No effects. 2 Integrity.
F: Data Node. No effects. 2 Integrity.
G: Network Scanner Node. As long as this Node is not destroyed, at the start of every Cycle, the Integrity values of every Node will be publicly revealed. If this Node is destroyed, only the destroyed / not destroyed status of a Node will be publicly revealed. 3 Integrity.

Spoiler: Proceedings of the Game (click to show/hide)

The game is played out in phases titled Cycles. Each Cycle lasts 48 hours, and may be extended at the moderator's discretion. During each Cycle, each player will publicly discuss the situation, and cast deletion votes. If a majority of players are voting a given player at the end of a given Cycle, that player will be deleted. Note specifically that that is majority, not plurality. If 3 players are voting player A, 2 players are voting player B, and 2 players are voting player E, no player will be deleted.

When a player is deleted, their role and alignment will both flip. They will no longer be able to interact with the game state or post, except to make a singular 'bah' post, unless their role specifically allows for it.

Also during each Cycle, players should plan and submit their Protocol usages privately. The Corrupted Agents will also be using their private chat during this time.

The Corrupted Agents also have access to a single shared Protocol, Overload Surge.

<Integrity-Damaging> (*) Overload Surge [local node / adjacent node 1-2x]: This Protocol has limited capacity and can only be used once per Cycle. Choose:
-Deal 2 Integrity damage to the local Node. All Counteragents present at that Node lose (**).
-Deal 1 Integrity damage to either the local Node and one adjacent Node, or two adjacent Nodes. All players at the selected Nodes lose (*).

Signups:

• Imp
• Maximum Spin
• notquitethere
• TricMagic
• Crystalizedmire
• ToonyMan
• juicebox

[Imp]

*in*

[Maximum Spin]

Celebratorily in.

[notquitethere]

In it to win it

[hector13]

I’ll PTW. I have family visiting from tomorrow, so I probably won’t be able to play.

[TricMagic]

Corruptin

[Crystalizedmire]

In

[ToonyMan]

This looks fun.

In.

[Imp]

looks around  Ahh.  I'm so happy to be here and see familiar names again!  I'll do my part but I don't wanna elim any of you!

[juicebox]

This seems like an interesting concept and I don't want it to die, so in

[FallacyofUrist]

Fantastic! I'll make an attempt at starting this Sunday. Have fun, everybody.

[ToonyMan]

Alright, which one of you killed Fallacy?

[Egan_BW]

Gate of Dreams when?

[Crystalizedmire]

Gate of Crash when?

[EuchreJack]

Gate of Dreams when?