Wednesday, August 17, 2022

Proposal: Little corks

In the effect of Spikes, change 15 to 3.

In the effect of Ram, change ten to 2.

Increase the Consumption of Spikes to 90, of Flamethrower to 230, and decrease the Consumption of Ram to 60.

In the status Scorched, change 5 to 10.

Balance pass on scratch multipliers; a bumpmurderbot is still possible but becomes a totalising strategy. Flamethrower + 3* Spikes is still outputting 270 damage but anything less than that is damaging but not instantly lethal.

Wednesday, August 17, 2022

Forfeit

Idle me. I’ll join the next dynasty

Story Post: Announcement #25

Advertisers are getting tetchy, Danny.

I don’t see why? Viewership figures are up on all previous years, engagement is through the roof and sponsorship opportunities…

All of that’s great, Danny, but the advertisers want spectacle.

Spectacle?

You know, pizzazz, razzmatazz, other words with a surprising number of z’s in them…

Embezzelment?

Danny, if you’re going to be like that then tis meeting is over.

Okay, look, you want a show? Fine. Name two Bots who haven’t fought yet, your two favourites.

Dark Lord?

I shoulda guessed you’d be a Dark Lord guy. Okay, and…?

DuckTank.

Slightly more surprising, but okay. Dark Lord and DuckTank… done. Tomorrow, 7pm, Arena Hall A. It’s prime time, baby!

Oh, you say baby too?

You bet your sweet ass. And we’re going to have obstacles at positions 8, 10 and 13 - ah, the audiences are gonna love it.

Proposal: Double Blind

In the rule ‘Winners at War’, add the following paragraph after “...continuing in the same pattern until the single Bout in the last round of the Tournament Bracket has concluded.”:

While the game is in Tournament Mode, any Operator whose Readiness is Workshop or Ready may privately message the Announcer with a list of Systems they wish to be added to their Bot for their upcoming tournament Bout. Once an Operator’s Readiness is set to Staging, the Announcer should remove all the Systems in their list from their Spare Parts Bin and add the Systems to their Bot, given their Bot has enough spare hardpoints to accommodate all the Systems in their list and all the Systems in the list exist in their Spare Parts Bin.

Before the Tournament the BlogBot league was little more than fun and games, all trash talk and teasing between Operators being for the show more than anything else. Now that glorious Victory looms over their heads, everything has become deadly serious; the Operators conduct modifications to their Bots in cold secrecy, hidden away where not a soul may see.

Story Post: Bout #30: DuckTank vs B.A.D [SupernovaStarbright vs Trapdoorpspyder]

A highly anticipated match today as SupernovaStarbright meets Trapdoorspyder - for the third time in this tournament, in fact. This has become one of the classic pairings, as no two operators have met each other as often, and going into the bout the score is tied - their first meeting in Bout #13 was a DuckTank win, while their more recent interaction in Bout 21 was famously the bout that SupernovaStarbright threw in order to get onto Trapdoorspyder’s LED board. We of course can’t know what happens behind the scenes here at the arena halls but the rumour is that she has recanted that position, and possibly also that Trapdoorspyder reneged on his side of the deal anyway, so we should see a more competitive match today.

In the left, in position 4, it’s DuckTank - still a chunky little pusher, now decked out with a nuclear engine to give some heft to its battering ram / cow catcher combo. Assessors seem to think that DuckTank is now likely to have similar pushing power to Hard Hat, but of course the shoving meta has faded a bit since the mid-portion of this tournament - we’ll see if Annoy-o-Tron has the answers.

Except that Annoy-o-Tron is no more! Over in position 15, instead of the usual mound-shaped body, we have the newly rechristened B.A.D, as it seems like Trapdoorspyder wants to capitalise on his recent infamy - under the hood it looks like the same sort of loadout as Annoy-o-Tron, but the whole presentation is much gothier, like the robot version of black eyeliner and a tattoo on the inside of your lip.

And they’re off!

DuckTank steams forward to position 13, getting right into the range of B.A.D.‘s axe but not close enough to get a shove in or give a poke with that battering ram - but what do I know - position is everything here, after all. B.A.D. declines to take a swing, instead opting for an evasive move, clearly anticipating a shove, but DuckTank has anticipated the anticipation and makes its own blocking pattern, trying to dissuade B.A.D. from attempting to bypass! This is some very high-level tactical play from these two, play and counter-play being rolled out seamlessly - and the crowd loves it - even BAD is getting some encouraging cheers amongst the usual boos.

BAD breaks formation first, swinging in with a quick axe attack - but this requires BAD to stand still for a second, and that gives DuckTank an opening, which it uses to crunch forward, moving to position 17 and pushing BAD to 18 in the process! The damage from the ram is superficial but the danger is acute - the edge of the arena is right there - BAD tries evasive moves again but DuckTank snaps right back into that blocking pattern, keeping BAD corralled into the corner, and BAD is going to try to fight its way out, another huge swing with that axe, but DuckTank isn’t missing an opportunity like that! One more big shove and that’s it - BAD is in the gutter and out of this match! What a Bout!

DuckTank wins by TKO!

Monday, August 15, 2022

Proposal: Let’s Buff Spikes

Times out 1-3 with 1 unresolved DEF. Failed by Brendan.

Adminned at 17 Aug 2022 18:44:16 UTC

Create a new rule entitled “Damage” as follows:

When a Bot’s hardware component suffers condition loss, that condition loss is known as damage.

If a Bot’s System would take damage greater than the total remaining Condition of that System, the difference between the damage inflicted and the remaining Condition of that system is applied as damage to that Bot’s next-frontmost System, or to the Bot’s Chassis if the bot has no next-frontmost System.

Call for Judgment: Spiking the Spikes

Timed out and failed, 2 votes to 4. Josh

Adminned at 17 Aug 2022 13:59:57 UTC

Add the following as a subrule of the “Bot Loadout” rule, titled “Compounding Systems”:

If a Bot would have two or more systems that share the same name equipped on their Bot, that Bot is considered to have exactly one of that system equipped on their Bot for the purposes of applying the effect of that system, unless all instances of that system on that Bot are at 0%. If a System refers to its own condition, then the highest condition instance of that System on that Bot is used.

Yeah, let’s fix this. I figured I’d do it in a way that also ensures that stuff like this doesn’t happen in the future.

Story Post: Bout #29: CrowBot2000 vs CarolAIna Reaper [Raven1207 vs Habanero]

It’s a small crowd tonight due to counterprogramming - this Bout has been scheduled at the same time as Dark Lord vs Hard Hat in the next Arena Hall over, and this match between CrowBot (with its slightly underwhelming win/loss ratio) and a new pilot of mysterious background seems to have been written off by many as the lesser attraction. This commentator, however, can’t help to be compelled by the mysterious Habanero - there they are now, in the operator pit, shrouded by a heavy poncho and a wide sombrero hat. Who are they, and where have they come from? How will they shake up this league?

We’re about to find out. CrowBot2000 has taken position 4, unchanged since its loss to Credit Score: F - still working with that flamethrower/axe combo.

Opposite it is our first look at CarolAIna Reaper. Its form factor is similar to a stumpy chilli pepper but it is covered in spikes - and under the spikes, thick ablative plating. This is an interesting loadout, and not one we’ve seen before; in this league we’ve seen spikes do some damage but there must be twice as many spikes on this Bot as we’ve seen before and that can only compound the potential for damage.

There’s the blue light - they’re off.

CrowBot is first to act, taking a cautious position at square 9, and Habanero - oh! Habanero moves decisively out to meet it, its chassis spinning as it does so, and it slams into CrowBot, and there it is! There are those spikes, tearing and smashing into CrowBot with incredible ferocity, a single bump rips CrowBot’s flamethrower clean off and throws it across the arena, and the double-spike loadout suddenly makes a load of sense!

CrowBot gets a swing in with its axe but that gets absorbed by the ablative plating on the Reaper, who pulled back a little to position 14 - CrowBot just sits there, stunned - but here’s the Reaper again, with its little run-up, smashing back into CrowBot and this time ripping the axe straight out of the chassis and sending it flying into the pit wall! This is stunning and the crowd are on their feet - what an incredible Bout - they’ve never seen anything like this before!

Once again Habanero pulls the Reaper backwards for a big run-up, and Raven is just looking at his controller - he has no idea what to do in the face of this!

Here it comes again - boom - those spikes shredding chassis now, and that’s that, one little bump and CrowBot is eviscerated. The Bout is swiftly called and I can guarantee that Habanero’s next Bout will be much more closely watched.

CarolAIna Reaper wins by TKO!

I’ve interpreted the effect of two sets of spikes as multiplicative - so 1*15*15 = a single bump doing 225% damage. As always please CfJ if you disagree.

Proposal: The Bots Attain Sentience

Timed out and enacted, 5-1. Josh

Adminned at 17 Aug 2022 08:34:27 UTC

If Proposal: Needs Less Halting Problem was enacted, revert its changes.

Add a new System to the list in the rule Systems:

| Advanced Logic Module || ₩4,500 || 290 || Passive: Enables all Advanced Triggers and Reactions in the rule Botscript.

In the rule BotScript, add the following to the bulleted list immediately after the sentence ‘All otherwise-legal Reactions are Resolvable, except if that Reaction’:

Triggers and Reactions marked Advanced may only be Resolvable if the Actor is permitted to use them by a System Effect or other ruleset-defined mechanism.

In the same rule, after “Combined triggers are accompanied by a single Reaction as normal”, add:

Combinable Reactions may be combined with one other other Reaction in the same manner as Triggers; however, a Combinable Reaction must be the first in the combined Reaction.

Add the following to the list of triggers:

* Advanced: “If the value of Token X is [greater than / less than / equal to] Y”, where X is any string of one five characters in length and Y is any integer
* Advanced: “If [the Actor’s / Y’s] [chassis / engine / exposed System] has a Condition that is [greater than / less than / equal to] X”, where x is any positive percentage value and Y is the name of a single Opponent that is a current participant in the same Bout as the Actor
* Advanced: “If line #X of this script was the trigger that took effect in the Actor’s most recent round preceding this one”, where X is an integer between 1 and 10
* Advanced: “If on the Opponent’s last turn they uses system X” where X is the name of any System

Add the following to the list of reactions:

* Advanced, Combinable: “...[increase / decrease] Token X by Y”, where X is any string of one five characters in length and Y is any integer
* Advanced: “... then move X times towards opponent Y”, where X is a positive integer and Y is the name of a single Opponent that is a current participant in the same Bout as the Actor

Add the following as a new subrule to the rule BotScript, called Tokens:

Some BotScript Triggers or Reactions may refer to Tokens being tracked or modified. Tokens only exist relative to the BotScript that created them; the Announcer may distinguish between Tokens of the same name generated by different scripts as they please. A Token is created for a BotScript whenever its value is modified by a Reaction in that script, if that token does not already exist for that script; each Token may only hold numeric values, defaults to a value of zero, has its value privately tracked by the Announcer, and is reset to zero and then destroyed at the end of the Bout in which is was created.

My attempt at bringing together Habanero’s ideas with SB’s suggestion that they carry a cost: in this case, money, power and a hardpoint.

Sunday, August 14, 2022

Proposal: Formalised Disputes

Times out 6-0. Enacted by Brendan.

Adminned at 16 Aug 2022 17:23:52 UTC

Create a subrule of Winners at War called Formalised Disputes:

This rule is flavour text if the game is not in Tournament Mode.

If the events of a bout in tournament mode are ever being challenged by a call for judgement and that call for judgement’s text requests a pause in the tournament, the schedule in Winners at War is paused for as long as that call for judgement is not resolved; time spent with the tournament being paused is not counted towards the 12 hour and 24 hour thresholds in the schedule. Only the Announcer is permitted to enact calls for judgement that request that the tournament be paused.

Where multiple open calls for judgement each request a pause, that pause lasts until all of them have been resolved.

In cases where a rule has been unambiguously applied incorrectly by the Announcer in a bout in tournament mode in the opinion of the Announcer, the Announcer is permitted to recalculate the results of that bout without the use of a proposal or call for judgement so long as less than 24 hours have passed since the end of that bout. The new ending time for a recalculated bout is considered to be the ending time of that bout’s Round, with the most recent ending time being used in the case of multiple recalculated bouts in the same round. This ending time recalculation applies whether the bout was recalculated as a result of the enactment of votable matter, or as a result of the Announcer choosing to recalculate without the use of a votable matter.

In the case of a declaration of victory existing while a call for judgement requests a pause in the tournament, all Operators are encouraged to vote against that declaration of victory if they believe that the revelation of new or secret information as a result of the possible enactment of that call for judgement could change their vote. There is no 120 hour cooldown on the use of a Declaration of Victory while the game is in Tournament Mode, though fair play rules still apply.

Where this rule refers to a Round, it uses Round in the context implied in Winners at War rather than the context in The Arena.

Things could get messy if a bout has to be recalculated due to the number of bouts that might be impacted, so this should hopefully make everything flow smoothly in that case. DoVs are also affected just so that we don’t need to rush Josh to recalculate the final bout on short notice if something goes wrong, but as a consequence the DoV cooldown has to be turned off.

Story Post: Bout #28: Hard Hat vs Dark Lord [SingularByte vs Brendan]

There’s history between these tow Operators; the last time they met SingularByte contested the result, and still holds that Brendan essentially stole the match - most lately calling Brendan out in a series of guest verses on rap tracks, as SingularByte is also a very skilled MC besides being a skilled Operator.

Still, the expectations for this Bout are low; Brendan was public about being willing take on anybody to deny Trapdoorspyder further victories, and the sense in the air is that neither Operator is going to be trying too hard here, or wanting to risk valuable components in advance of a possible Tournament finish.

In position 4 we have Hard Hat, unchanged since its last bout against Annoy-o-Tron, in which Cool Hand Luke provided a famous assist. Opposite from Hard Hat is Dark Lord - who seems to have varied its loadout at the last minute with a giant mitt, to prevent bypassing manoeuvres, thanks to its modular breakpoint.

And they’re off - but Hard Hat is just sitting there - is this another SingularByte stratagem? In the Operator pit SingularByte is looking expectantly at Brendan, who jams the control forwards, moving Dark Lord over the traps and past the various obstacles to position 8. SingularByte looks disgusted - it’s unclear what he was looking for from the Bad Boy of BlogBot but he didn’t get it - and now h’s dramatically jamming Hard Hat backwards, and yes - out of bounds! SingularByte declines a post-match handshake from Brendan and stalks out of the arena, but Brendan just shrugs and updates his LED Banner, as the judges announce -

Dark Lord wins by TKO!

Proposal: Vanishing Point

Times out and passes, 5-2. Enacted by Brendan.

Adminned at 16 Aug 2022 17:20:10 UTC

In the rule Showboating change “quorum or more” to “more than four”.

LED Banner victory being vulnerable to sudden shifts in quorum strikes me as odd; also odd is that I count towards quorum for the purposes of determining the victory as things stand.

New Mentorship

Brendan is to be Habanero’s mentor.

Sunday, August 14, 2022

Proposal: Needs Less Halting Problem

Times out 2-2 and fails -SingularByte

Adminned at 16 Aug 2022 05:10:29 UTC

Enact the proposal ‘Needs More Turing Completeness’, changing the Reaction it adds to read:

...then [enable/disable/toggle] the Triggers at the following positions in the list: X. If the Script has been run less than thrice this turn, run it again after this Reaction is Resolved without incrementing the turn number of the Bout”, where X is a set of integers denoting valid positions in the list of Triggers

Let’s try this again!

Story Post: Announcement #24

Meanwhile, in a seedy bar not far from the Arena Hall complex…

If you give the bartender the exact right kind of nod, they’ll gesture you towards a nondescript door which will lead you to a dark corridor. At the end of that corridor is a heavy steel door, which, when opened, will reveal a narrow, rusted-iron spiral staircase leading down into a damp cellar. From the foot of these stairs you will now be able to hear the sounds of people shouting and the tortured whine of metal on metal. This is the real deal; push through the curtains and what you’ll see is the real BlogBot fighting league, the dark, dangerous underbelly of the sport where everything is for keeps and nothing is off limits.

Take this bout, for example. One Bot, called Zero Wing, is basically a control unit surrounded by autonomous modules that can break away, charge down the opponent and detonate themselves - expensive for the Operator, worse still for the Opponent. It’s hanging back, now, at the edge of the fighting pit, its drones circling its main unit, looking for an opening through which to strike.

Because its opponent is also a Bot of no common factor; named Six Eyes, its form profile is more or less a series of rotating rings inside a fixed frame, each of which holds a lens in place. When activated a single laser beam can be split into a half-dozen, scoring the centre of the stage and preventing even a determined bot-cloud from getting through. This bot is making aggressive moves; it’s a battle of positioning, as the ring-bot tries to find a position where it can catch its Opponent’s central unit with its laser with enough force to knock it out in one, while the Operator of the cloud-bot is trusting their gut, watching the rings, waiting for a moment where -

Ah. There it is.

For just a split-second the rings are misconfigured, giving too much coverage on the left and not enough on the right. And that’s all that the swarm needs; two of the detonation modules peel away from the central housing and score up the left hand track of the pit - but it was a feint, and actually the rings were never misconfigured at all, and suddenly those lenses are snapped back into position, the detonation modules are fried and dead-stick, and that’s now created a little safety-corridor on the left for Six Eyes, who takes it…

Because behind Six Eyes is a player knows that you don’t play against the Bot, you play against its Operator.

In the chaos as the Bout concludes, with the bookies collecting their winnings and the crowd jostling and yelling, someone appears at the Operator pit, by Six Eyes’ Operator: someone in the livery of the BlogBot league. The Operator is handed a note; it reads:

ANNOY-O-TRON. ARENA HALL B. NO CONFIGS.

SupernovaStarbright stands up and, with a thin smile, grabs her competitor’s pink slip, her winnings, and a fat manilla folder marked TRAPDOORSPYDER. Time for DuckTank to get back to work.

Meanwhile, across town, a mysterious figure stepped off of a boat and onto the dock. Despite the lashing rain, this stranger had no coat or umbrella, and nor did the man there to meet him - although this person at least could be identified thanks to the BlogBot League pin on his lapel. “Are you… Habanero?” asked the man, and the figure just nodded. “Come this way please… Your first bout happens imminently, it’s against Raven1207 and CrowBot2000, do you need time to get ready…?”

Habanero’s response was simply a shake of the head. It was time to shake up this league.

SupernovaStarbright vs Trapdoorspyder, no configurations
Habanero vs Raven1207, bumpers up, obstacles as follows: 11^, 10v, 7v

Proposal: Needs More Turing Completeness

Withdrawn and therefore failed -SingularByte

Adminned at 15 Aug 2022 05:50:48 UTC

In the rule ‘BotScript’, change the first sentence to read:

Each Bot has a Script, being a list of up to ten Triggers, each Trigger having a corresponding Reaction and a boolean value indicating whether it is Enabled or Disabled (defaulting to Enabled).

In the same rule, change:

until they find a Trigger which is true for the Bot in question and its corresponding Reaction is Resolvable

to read:

until they find a Trigger which is Enabled, true for the Bot in question, and has a Resolvable corresponding Reaction

Append the following Reaction to the bullet point list starting with “Possible Reactions are:-” in the same rule:

...then [enable/disable/toggle] the Triggers at the following positions in the list: X. If the Script has been run less than thrice this turn, run it again after this Reaction is Resolved”, where X is a set of integers denoting valid positions in the list of Triggers

But can it run Doom?

A new Operator joins the fray

I formally announce my intention to become an Operator.

Hopefully I did this right!

Proposal: Meaningful Mist

Reaches quorum with 10-1 and is enacted -SingularByte

Adminned at 15 Aug 2022 05:48:51 UTC

In the rule Taunt, change

When a Bout concludes, the Winner gains additional Money equal to ten times their own Red Mist, and any non-winning participants lose percentage points of Condition to their chassis and exposed system equal to their Red Mist, to minimums of zero; then, the Red Mist of all participants in that Bout is set to zero.

to read

When a Bout concludes, the Winner gains additional Money equal to one hundred times their own Red Mist, and any non-winning participants lose percentage points of Condition to their chassis and exposed system equal to five times their Red Mist, to minimums of zero; then, the Red Mist of all participants in that Bout is set to zero.

Friday, August 12, 2022

Story Post: Annoucement #23

[A music video for the track Safety Gear by Lil Botty]

[The first verse features typical scenes of rap music excess - Lil Botty on a boat, Lil Botty in the club, Lil Botty shooting at a helicopter with a gamma pistol]

[The second verse, however, is a guest verse from none other than MC HardHat himself - now watch out as SingularBeat drops some rhymes]

Yeah, yeah
Ayo, the fans, it’s time.
It’s time, the fans (aight, the fans, begin).

Straight out the metallic dungeons of rap
The trap drops deep as does my ajax
I’m a mothershover, ‘cause to shove is the sister tax
Beyond the walls of bots, life is defined
I think of victory when I’m in an Arena Hall C state of mind

Hope the axe got some tax.
My max don’t like no dirty wax.
Run up to the syntax and get the lax.

In an Arena Hall C state of mind.
What more could you ask for? The strong trap?
You complain about Dark Lord
Out and about stealing Bouts, Brendan I’m calling you out
I gotta love it though - somebody still sneaks through this crap

Brendan, you got called out bruv,
Brendan, you got called out

I’m rappin’ to the chassis,
And I’m gonna move your profligacy.
Weak, damaged, defunct, like a bar
Boy, I tell you, I thought you were a spar.

I gotta take the Dark Lord, gotta take the map.
I woulda tried to win I guess I got no rap.
I’m rappin’ to the profligacy,
And I’m gonna move your chassis.

Yea, yaz, in an Arena Hall C state of mind.

Thinking of victory. Yaz, thinking of victory (victory).

[Behind him, Hard Hat does donuts while an effigy of the Arena Hall explodes in a CGI effect]

A flame tile at square 9 and an explosion tile at square 13; obstacles above 9^, 12^, and 18^, and below 19v, 10v, and 15v.

Story Post: Bout #27: Yvette the Botmistress vs Annoy-o-Tron [chiiika vs Trapdoorspyder]

We’re in for a spicy match tonight - over the course of this contest Trapdoorspyder has emerged as the villain of the piece, and the fans just love to hate him. Here he is now, entering the stadium - the boos are starting up - but oh, he seems to be pushing his elderly granny along in a wheelchair, oh, that’s blunting some of the audience response, the stands seem to be quieting down - WHAT! He’s just tipped granny OUT of the wheelchair and asked the hottest person in the audience that he could find to hop in instead! That’s his grandma, sprawls on the floor, while he is flirting with his front-row floozy! Oh, what a villain, what an vicious brute!

By contract, here’s chiiika, dressed in a white power-suit, looking like she’s ready for nothing less than business in this bout. Yvette doesn’t have the strongest record in this contest, in three bouts she’s chalked up one win, against Credit Score: F, but she’s the firm crowd favourite tonight.

In position 4 starts Annoy-o-Tron, which seems to have been redesigned to look more… menacing? Lots of extra spikes, and it seems to have a mohawk now. Other than that its configuration seems to be unchanged.

In position 10 we have Cool Hand Luke, the house bot that herds horses and axes bots. Cool Hand Luke is perfectly capable of knocking out a competitor if left to its own devices, so both Operators will hopefully be cognisant of its threat and will have planned to work around it.

And in position 16 it’s Yvette, similarly unchanged in configuration.

The blue light is on and so is this Bout! Trapdoorspyder jams on his controller, sending Annoy-o-Tron into a 180 - it’s facing outside of the arena, towards the bumpers - and Yvette jumps forward before clattering into the back of Cool Hand Luke. The house bot is unperturbed, facing the other direction - and then Annoy-o-Tron jams had backwards, sketching an elaborate bypass pattern to push across the entire arena to position 19.

Luke moves into the area vacated by Annoy, heading into square 7, and Yvette - oh goodness - Yvette pulls the same move again, ramming Luke hard from behind, and why is she picking a fight with the house bot when Annoy-o-Tron is right there? He’s not even doing anything, just sitting smugly on the sidelines, and now Luke is turning around - he won’t take being hit twice - and Yvette seems to be stuck in place, watching it happen.

A grapple and three swift axe-blows later and that’s it - it’s all over for Yvette. Trapdoorspyder smugly steps into the middle of the arena, as if conducting the audience’s boos, while chiiika gives a small wave and then heads out through the Operator tunnel, disappointed by unbowed. Over the tannoy comes the announcement -

Annoy-o-Tron wins by TKO!

Thursday, August 11, 2022

Proposal: Quicker endgame

Timed out and enacted, 6-0. Josh

Adminned at 13 Aug 2022 19:12:23 UTC

In the rule Winners at War, in the bulleted list immediately following the line that reads “Once the Bracket has been posted, the following schedule takes effect”, change all instances of 24 to 12 and then change all instances of 48 to 24.

Proposal: POS

Timed out and enacted, 3-0. Josh

Adminned at 13 Aug 2022 16:09:53 UTC

Remove the words “50% of” from the sentence in the rule “Systems” that currently reads “An Operator whose Readiness is not Set may remove a System from their Bot at any time by either increasing their money by 50% of the Effective Cost of the system being removed or adding that system at the appropriate condition to their Spare Parts Bin.”

If there exists a rule called “Repair Wrench” then repeal it.

Proposal: Galvanised Sprocket

Enacted popular, 6-0. Josh

Adminned at 13 Aug 2022 07:40:35 UTC

In the rule Income, change “Once in between each Bout in which they participate, while their Readiness is Workshop, an Operator may add 5% condition to each component in their Bot” to read as follows:

At any time while their Readiness is Workshop, an Operator may add 5% condition to each component in their Bot for each full 24 hour period that has elapsed since they last performed this action or since the end of the last Bout in which they were a participant, whichever is most recent.

.

Proposal: Part recall

Timed out and failed, 1-4. Josh

Adminned at 13 Aug 2022 07:38:12 UTC

Repeal the rule Repair Wrench.

As I’ve commented in the other proposal, this honestly seems like a redundant rule. You can replace parts relatively cheaply, and you can repair parts via Income. We don’t really need a third form of repairs.

Wednesday, August 10, 2022

Proposal: GPC

Popular just under the wire at 6-0. Enacted by Brendan.

Adminned at 12 Aug 2022 22:19:31 UTC

Add to the list of triggers in the rule “BotScript” the following:

* “If the Actor is in the space numbered X [or [higher / lower]]...”, where X is a positive integer.
* “If the Actor is in the space lettered X [or [earlier / later]]...”, where X is a letter from A to F.

Story Post: Announcement #22

09h42, CORRIDOR H LEADING TO ARENA HALL C

Three children are playing with BlogBot action figures in an alcove behind one of the stages hosting cosplay competitions. One of them is showing off their rare, limited-edition Credit Score F figurine, with articulated flipper action. Trapdoorspyder spots them while passing through, diverts his course, and pushes them out of the way before viciously stomping on the rare action figure. “This is what becomes of homes and dreams!” he shouts.

11h07, CENTRAL PARADE SQUARE

Giancarlo Federico Magistrelli, the internationally renowned ice sculpturist, is unveiling his latest work in the main plaza outside the stadium. A life-sized replica of Cool Hand Luke, it is designed to stand in the square for weeks and slowly reveal over time the smaller models of The Colonel and The Pyramid hidden within. Trapdoorspyder sits at the side of the square for an hour with a magnifying glass, training the sun onto a patch of ice and melting a hole clean through the middle of the sculpture, ruining it.

15h47, THE CANTEEN

Trapdoorspyder is standing on the chaffing dish stand, his trousers around his ankles, when chiiika bursts in.

“ENOUGH,” she cries out, “Is this how you behave in the Archepelagic League?”

“Are you calling me out,” snarls Trapdoorspyder.

“You bet I am,” says chiiika. “Arena Hall A, 19h00, bumpers up, Cool Hand Luke. I’m gonna make you wish you were never born.”

She sweeps from the canteen while the attendees cheer raucously.

Proposal: The cost of repairs but I got everything this time

Times out 1-2 with 1 unresolved DEF. Failed by Brendan.

Adminned at 12 Aug 2022 20:14:51 UTC

In the Repair Wrench subrule…

Change the formula from

Decrease their money by the formula: ((new effective cost of the part) - (previous effective cost of the part)) * 1.25

to

Decrease their money by the formula: ((new effective cost of the part) - (previous effective cost of the part)) * 0.65

Add the following to the end of the rule:

Equipment repaired in this way can only have their condition increased by 15% and only be repaired once in a 24 hour period beginning when the atomic action was completed

Maldor looked at the Dynix Repair systems brochure, and was appalled at the potential cost of repairs for his Chassis. “I could do better than that” he said, and went to the local hardware store to purchase some materials and tools. And then had to make a second trip because he forgot the screws needed to fix one of the mounting points… And a third trip when the drill he bought didn’t have the correct tooling…

Proposal: Cost of doing repairs

Illegal. Josh

Adminned at 10 Aug 2022 19:24:24 UTC

In the Repair Wrench subrule, change the formula from

Decrease their money by the formula: ((new effective cost of the part) - (previous effective cost of the part)) * 1.25

to

Decrease their money by the formula: ((new effective cost of the part) - (previous effective cost of the part)) * 0.65

Maldor looked at the Dynix Repair systems brochure, and was appalled at the potential cost of repairs for his Chassis. “I could do better than that” he said, and went to the local hardware store to purchase some materials and tools.

Proposal: Time skip

Times out 5-0 with 1 unresolved DEF. Enacted by Brendan.

Adminned at 12 Aug 2022 18:00:58 UTC

Immediately after the first sentence of “Winners at War” append:

If no Operator have had their readiness changed in the last 96 hours, and no bouts are currently pending resolution, then the game has entered Tournament Mode.

Replace “On 22 August” with “On the day that Tournament Mode begins”
Replace “On 25 August” with “Three days after Tournament Mode begins”

This is basically just a way to ensure that the game’s activity doesn’t drop too low while we wait for the tournament. If absolutely everyone stops fighting, we skip the wait.

Proposal: Final Countdown

Reaches quorum with 8-0 and is enacted -SingularByte

Adminned at 11 Aug 2022 07:01:11 UTC

In the rule Winners at War, change “The winner of the last Bout in the Tournament has achieved Victory” to “The winner of the final Bout in the Tournament has achieved Victory”.

Story Post: Bout #26: Dark Lord vs Bad Door [Brendan vs maldor]

Ah, here’s Brendan, swaggering into the arena. Looks like he’s flipping off the crowd - ah, and they love it. To be fair, that’s a mild, even affectionate entrance for the Bad Boy of BlogBot. Just Brendan being Brendan! By contrast, here’s maldor, chatting, signing autographs, pausing for a selfie - seems like a really likeable guy - but Brendan’s just putting on his aviators and scanning the crowd for hot chicks. That is some rock and roll living, right there.

Here come the bots. The bumpers are up, so neither Operator seems to have gone for a shove-heavy lineup. Dark Lord is coming into position 4, having reconfigured around a grapple-and axe combo - the versatility of this Bot and Operator is so wild, last Bout it was a conventional shover but this is a completely different spec.

On the other end, at 16, it’s Bad Door - Bad Door is of course very familiar to fans having just come off of a hot run in the club circuit, but tonight’s it’s first runout in the League. The ram/flipper/taser combo it’s working with today is an interesting mix, less immediately obvious in terms of strategy than Dark Lord, but who knows? It’s not just about the config, it’s about the orders.

The blue light is flashing - here we go!

Dark Lord is off the line first, crashing forward to position 16 - clattering into Bad Door back but bashing itself hard on that ram in the process! Bad Door retaliates with a shot from its taser which embeds itself into Dark Lord’s LED Banner, but Dark Lord has popped a side-loaded harpoon from its chassis and plugs Bad Door right in the side with it - Bad Door is Grappled and appears to be Anchored to Dark Lord!

Bad Door now has a puzzle as to how to resolve its predicament - and it appears to have decided on the ram way out, charging straight at Dark Lord and trying to force its way through! Dark Lord has the edge on shoving power so isn’t budged but that ram is starting to do some serious damage to the Dark Lord’s hull. But Dark Lord isn’t backing off - and now, from the other side of the chassis comes a glittering pickaxe - which is brought down hard onto Bad Door, doing major damage to its chassis! Again and again Bad Door tries to break free, but Dark Lord is implacable - holding its position and bringing down that axe, two, three, four times - and Bad Door can’t hold up against the onslaught.

Dark Lord wins by TKO!

Tuesday, August 09, 2022

Story Post: Bout #25: Credit Score: F vs Annoy-o-Tron [lendunistus vs Trapdoorspyder]

Today’s marquee match is between Credit Score F and Annoy-o-Tron, and on paper it’s an interesting match-up - Credit Score is here on its sixth Bout of the contest, with three wins and three losses under its belt, while Annoy-o-tron is on its ninth go, with five wins to four losses. So a very even track record, and although Annoy-o-Tron has arguably faced tougher opponents thus far, it has also been embroiled in a messy match-rigging scandal.

Here they are - on the left, in position 4, it’s Credit Score: F - the crowd is greeting lendunistus warmly as he enters the operator box.

And on the right, Annoy-o-Tron - again, a big reaction from the crowd, but a few boos scattered throughout. That’s interesting - usually BlogBots is a very good-natured sport and you’ll see a lot of people in the crowd reacting against the boos, cheering louder, considering them unsportsmanlike.

And they’re off! And - oh! Credit Score F is straight into the bumper with a massive hard reverse!

A big flip from the bumper and Credit Score is flipped into square 6. Was this just a misfire on the control pad? Lendunistus looks composed but the crowd is starting to get agitated… Annoy-o-tron is prodding cautiously forward to 10, and then again to 9 while Credit Score rights itself, but then Credit Score again rams hard backwards into the barriers - going flying into position 12 - and now the crowd is starting to boo - this looks like it could get ugly.

Annoy-o-Tron, to be fair, isn’t standing still - it spins in place, trying to get a bearing on Credit Score, but lendunistus is off again, hard in reverse - but now Annoy-o-Tron is in the way and the chassis of Credit Score smashes into it, sparks flying - the shove power in Credit Score is just greater, but with the obstacles in the arena the control isn’t there, so Annoy-o-Tron ends up wedged behind an obstacle at position 8 while lendunistus is just in position 9.

The shove has left Annoy-o-Tron flipped, so Credit Score F resumes its suicide run - again reversing hard into the left hand bumpers - and slamming down into position 6, on its back - and here we have both bots on their backs, rocking to get upright - some of the more agitated members of the audience are starting to throw bottles.

Annoy-o-Tron is the first back on its feet and it turns in position to face the other way, and then Credit Score F is back upright and, again, hurtling back towards the barriers. This is sad to see, now, as Annoy-o-Tron seems to be unwilling to come out from behind its obstacle - just turning in place - as Credit Score F pounds itself into the left hand wall again and again. Finally - after three more flips - the chassis of Credit Score F cracks, and, to the sound of loud boos from disappointed fans, the Bout is called. Annoy-o-Tron may have won this Bout, but the true loser was perhaps the sport that we all love - what an expensive way to throw a match.

Annoy-o-Tron wins by TKO!

Monday, August 08, 2022

Proposal: Brand new energy saving techniques!

Timed out and enacted, 5-0. Josh

Adminned at 10 Aug 2022 15:24:55 UTC

Change the cost of the LED Banner system to 120.

A handful of people don’t even have LED banners because of the energy cost. It’s hard enough getting matchups right now without also having to worry about a steadily increasing energy cost. In addition, as it is now with the current proposed system, it’s actually a penalty if you make it to the tournament with more than 1 name.

Proposal: [Core] Play Fair!

Timed out and could not be enacted - 3-2, falling short of the quorum requirements for core rule changes. Josh

Adminned at 10 Aug 2022 14:33:10 UTC

Add the following to the list of rules listed under Fair Play:

An admin should not abuse any powers granted to them as a result of their Admin status, such as performing a scam that another non-Admin Operator could not have performed as a result of not being an Admin. This does not include situations where an Admin quickly performs a scam shortly after enacting a proposal.

 

Me and Brendan were taking about a scam I could have had the opportunity to do a a result of being an admin, and came to the result that this needed to make its way into the ruleset.

Proposal: Sooner or Ablater

Reached quorum and enacted, 6-0. Josh

Adminned at 10 Aug 2022 13:51:21 UTC

Rewrite the effect for the Ablative Plating System as follows:

Passive: All Condition loss incurred by other Components on the Actor is reduced by 50% and is incurred to this System instead of any other Component that it might be incurred to. Regardless of Statuses or the effects of other Systems on this Bot, no damage incurred to this System as a result of this Effect may cause damage to be incurred to other Components on this Bot.

To prevent loops in which damage to a Loose bot’s engine, say, is returned to the Plating and then returned back to the Engine and then returned back to the Plating etc etc

Proposal: Winners at War

Timed out and enacted, 5-0. Josh

Adminned at 10 Aug 2022 09:24:06 UTC

Add a new rule, called the BlogBot League Final Showcase:

If the date is on or after 22 August 2022 then the game has entered Tournament Mode. If the game is not in Tournament Mode then the rest of this rule is flavour text.

The rules Showboating and Taunt have no effect and are flavour text; any Operator or Announcer may remove them from the ruleset.

On 22 August or as soon as possible thereafter, the Announcer should post a Provisional Seed List. The Provisional Seed List is the Announcer’s subjective opinion of which Operators in the Dynasty have the best Bots, ordered from 1 being the best to the highest number being the weakest. The Operator is allowed to use whatever private metrics they please to assess this, with the single exception that they cannot consider the number of names on any Bot’s LED Banner.

On 25 August or as soon as possible thereafter, the Announcer should post the Final Seed List. The Final Seed list is the same in form, purpose and rules for composition as the Provisional Seed List, updated to take into account any changes between the posting of the two documents. Once the Final Seed List has been posted, all Operators have their Readiness set to Workshop, Operators may not change their Readiness, and unidling Operators are considered not to be Operators for the purposes of the remainder of this rule for the remainder of the Dynasty.

When the Final Seed List has been posted, the Announcer should at their earliest opportunity post a Bracket. The Bracket is the organised list of Bouts that will comprise the Final Tournament, and the Announcer may organise those Bouts as they determine best, following where possible the following principles:
* In round 1 of the Bracket, all Operators with no LED Banner or no names on their LED Banner should participate in a Bout
* In round 1 of the Bracket, Bouts should be organised with the top seed Operators (the top n/2 names on the Final Seed List, where n is the number of Operators participating in round 1) being matched with the non-top-seed Operators
* If there are an uneven or otherwise unmanageable number of Operators in round 1 then the top-most seeded Operators may be deferred into round 2
* Whenever an Operator loses a Bout in the Tournament, they are eliminated from the Tournament and cannot be scheduled in a future Tournament Bout, cannot win the Tournament, and cannot achieve Victory in this dynasty
* In Round 2 of the Bracket, all Operators to have won their round 1 Bout should progress to be matched against Operators deferred into round 2 (due to having populated LED banners or being too high-seeded for round 1)
* If there are an uneven or otherwise unmanageable number of Operators in round 2 then the Operator with the most names in their LED Banner (using top-most seededness as a tiebreaker) may be deferred into round 3
* Rounds then proceed with winning Operators proceding into further rounds, until a final Bout of 2 Operators is due to take place
* In any round after round 2 (i.e. round 3 or above), if there are uneven number of Operators in the round, then before any of the Bouts in that round take place an elimination bout is held between the two bottom seeded Operators in that round; the loser of an elimination bout is eliminated
* All Bouts in the Bracket should have their Configurations detailed in the Bracket document

Once the Bracket has been posted, the following schedule takes effect:

* 48 hours after the Bracket has been posted, all Operators have their Readiness set to Staging
* 24 hours after that, all Operators have their Readiness set to Set; as soon as possible thereafter, the Announcer should run the first round Bouts in the Tournament Bracket,
* 48 hours after the result of the final Round 1 Bout has been posted, all Operators due to participate in a Round 2 Bout have their Readiness set to Staging
* 24 hours after that, all Round 2 participant Operators have their Readiness set to Set; as soon as possible thereafter, the Announcer should run the second round Bouts in the Tournament Bracket

...continuing in the same pattern until the single Bout in the last round of the Tournament Bracket has concluded.

The winner of the last Bout in the Tournament has achieved Victory.

I *think* this works but you can never tell when writing something like this, so please, feedback.

A 2-week fuse to allow someone to win under the current spec if they can, and to allow for this rule to be modified if it is utterly janked.

Sunday, August 07, 2022

Story Post: Announcement #21

Just got a new works order in

Oh, yeah, what we go?

Arena Hall G. Apparently they need a bunch of obstacles installed.

Aw, hell.

Yeah, so it’s gotta be stuff we don’t mind if it gets bashed up.

I’ve got some MDF we could use?

Don’t think so, I think they’re looking for more of an industrial steel vibe.

Are they paying for it?

It’s the BlogBot League, they ain’t exactly short of cash.

What’s the config?

Obstacles above 1, 2 and 8, and one below 4. Oh, and we gotta put the bumpers up as well.

Alright, let’s get to work.

Who d’you think’s getting this one?

Oh, I heard about this - it’s Annoy-o-Tron and Credit Score: F.

Heh. Good luck to em, that’s what I say.

Proposal: More reactions

Times out 2-0 with 3 unresolved DEFs. Enacted by Brendan.

Adminned at 09 Aug 2022 23:29:55 UTC

In the bullet point list titled “Possible Reaction are:-” Add the following entries:

…then [Use system Y / Move X spaces [toward / away from]] the bot that inflicted Z status. Where Y is a valid system on the bot, X is a positive integer, and Z is a status

BotScript v2.3.1

Changes:

Bots can now react to status effects better, by targeting the bots who gave them that status.

Bugfixes:

Script no longer assumes things about the arena its in.

Proposal: How To Get Softlocked by RNG

Enacted popular, 6-0. Josh

Adminned at 08 Aug 2022 15:14:21 UTC

In the rule “Bouts”, after “When an Operator’s Readiness is Workshop and their Bot is not Trashed, they may set their Readiness to Ready at any time”, add the following:

* When an Operator’s Readiness has been set to Ready for the past 48 hours, they may set it to Workshop

This prevents being locked to your current loadout when you’re screwed by RNG and never get picked

Call for Judgment: Non-dis-script

Reached quorum and passed, 6-0. Josh

Adminned at 08 Aug 2022 09:00:20 UTC

In the rule BotScript, change the text “All Reactions are Resolvable, except if that Reaction:” to read:

All otherwise-legal Reactions are Resolvable, except if that Reaction:

In the same rule change “If a line in a script is no longer a legal entry but may be legally represented by other wording without changing the meaning it had at the time of being provided to the announcer, the announcer should strive to treat it as if it had that legal wording if possible” to read

If a line in a script is not a legal entry but may be clearly assessed (without context) as having the same meaning as a single, specific instance of legally compliant wording, without changing the meaning that that line had at the time of being provided to the announcer, the announcer should strive to treat it as if it had that legal wording if possible.

Add the following to the end of the first paragraph of the same rule:

All legal Triggers and Reactions can be found in lists in this rule.

Set the Readiness of any Operator whose Readiness is Set and whose EVC on this CfJ contains the word “rethink” to Staging.

Clearing up some ambiguities in what counts as a legal script.

Saturday, August 06, 2022

Proposal: I CALL FOUL!

Enacted popular, 7-0. Josh

Adminned at 08 Aug 2022 08:23:04 UTC

In the subrule “Configuration”, remove the text “.In this Bout, square 20 is also In Bounds, and the right-hand-most Bot starts on square 17 rather than square 16;” and then capitalize the first letter of the word immediately following the removed text.

As it stands, one person starts closer to the house bot than the other. Let’s fix that.

Story Post: Announcement #20

Two children look up from exchanging collectable cards of their favourite Bots and Operators. One is holding the shiny foil Brendan card; that child is in the middle of negotiating a trade for the classmate’s extra-deluxe Maldor card.

As they sit, two adult figures appear over their shoulders. The children look up; it’s Brendan and Maldor themselves! “WOAH!” say the kids as the two heroic operators look down at them.

At the bottom of the screen appears the legend: COLLECT THEM ALL! All of the League’s biggest stars, for you to keep and collect in your Office BlogBots League Collectable Card Binder! Available from all good newsagents!

Then a close-shot of a smiling Brendan - “And if you want to get your card signed by me - come to Arena Hall G tomorrow at noon before the big Bout!”

Cut to Maldor - “That’s right, I’ll be there taking on Dark Lord, and the bumpers will be up! Don’t miss it!”

A plain title card, saying: BLOGBOTS CARDS ARE OFFICIAL SPONSORS OF THE ULTIMATE BLOGBOTS LEAGUE. TM AND ALL RIGHTS RESERVED.

Story Post: Bout #24: Hard Hat vs Annoy-o-Tron [SingularByte vs Trapdoorspyder]

Astonishingly, these two bots - some would say the top seeds of the contest so far, although some of the newer comers might dispute it - have only met in the contest once before, right at the early days of the League. In that bout, SingularByte was still refining his signature shove-style, and managed to KO Hard Hat himself by steering his bot into the gutters. Tonight that won’t be an issue - the huge paddle-shapped bumpers are up, and Cool Hand Luke is patrolling the centre of the arena.

There, in position 4, is the familiar figure of Annoy-o-Tron - still a deceptively simple Bot, with just a mound-shaped body for defence and an axe on offence, the menace of Annoy-o-Tron rests entirely in the skill of its operator, Trapdoorspyder, who has emerged as a master at waiting for his opponent to self-destruct.

In position 10 we have Cool Hand Luke, the rootinest, tootinest cow-House-Bot in the old west. Yee haw! Let’s see if that big ole lasso Grapple and even more menacing Axe come into effect tonight.

And over there, in position 17, it’s the yellow-domed menace itself - stripped down to just its signature cow catcher - it’s Hard Hat! The crowd loves to see this audience favourite in the ring and tonight is no different.

Just a reminder that there has been significant discussion on the message boards about collusion with regards to Annoy-o-Tron since its last bout, so fans will be eagle-eyed to see whether Hard Hat puts up a fight.

And they’re off!

Annoy-o-Tron makes the first move, and with a shimmery bypass move it snakes all the way across the arena floor to take up position right behind Hard Hat in position 18! Cool Hand Luke sits impassively at position 10, but then Hard Hat has another malfunction - just like DuckTank did, it slams hard into reverse, but here the barriers are up, and that’s no good! Hard Hat sails across the arena, slamming down in position 3, completely upside down!

Annoy-o-Tron again bypasses - backwards this time across the stage to position 4 - an attack position - while Cool Hand Luke turns in place to survey the action. While Hard Hat is struggling to right itself, Annoy-o-Tron rotates in position to bring its axe into attack position - will Hard Hat get away in time? Cool Hand Luke is moving forward now, occupying a curious position in square 7 - Annoy-o-Tron is in range of its melee weapons, and may be distracted! Hard Hat struggles upright and tries to bypass away but slams straight back into the barriers - and they’ve deposited it right back in position 2, not upside down this time as SingularByte pulls off a deft mid-air correction, but still well within range of Annoy-o-Tron’s axe - which comes down with a sickening crunch! The crowd goes wild - this is very obviously not a fix, but it all seems to be Annoy-o-Tron right now!

But oh my god - with Annoy-o-Tron’s still in Hard hat’s chassis, Cool Hand Luke has fires out that gas-powered harpoon of a Grapple and has speared Annoy-o-Tron right through the outer shell! They’re bound together now in a tight 3-square radius!

Hard Hat has spotted its window now and slams on its reverse pedal, bypassing deftly around both its opponent and the House Bot to the relative safety of position 19. Annoy-o-Tron moves forward, still trying to shake off its pursuer - to no avail! Annoy-o-Tron takes position 1 but Cool Hand Luke is dragged to position 4, and there’s that axe! Is this Hard Hat’s strategy, to dance in and out of trouble while the House Bot keeps Annoy-o-Tron occupied?

It looks like it might be, as Hard Hat now moves back to position 2 - right between Annoy-o-Tron and Cool Hand Luke! Annoy-o-Tron simply, coolly turns around - oh, look at the skill here, Trapdoorspyder deftly suckering his rival into the firing line of the House Bot - which does not disappoint! That axe slams into Hard Hat and Hard Hat is now at risk from getting it from both sides, so flees back to position 19 and a moment of safety!

Annoy-o-Tron bypasses forward now, taking position 8 and dragging Cool Hand Luke into position 5 - and there’s nothing to absorb the blow this time - Cool Hand Luke’s savage axe slamming into Annoy-o-Tron’s chassis. This is a complete turnaround now as Annoy-o-Tron cannot seem to escape the House Bot and that chassis looks badly damaged now, with each of these extra blows getting refined precision thanks to the grapple removing the operator’s need to steer! Hard Hat bypasses right back to position 2, this time a much safer proposition, and Annoy-o-Tron bypasses towards the middle of the arena - hoping to catch Hard Hat again at the other side? Ah, no good - Annoy-o-Tron takes position in square 11, but Cool Hand Luke is still right there with him at position 8, and one more huge swing of the axe is all it takes - that Incisor TRN9P can take a lot but this was just too much. Annoy-o-Tron powers down and the judges call the Bout:

Hard Hat wins by TKO!

Proposal: Welcome to the Little Leagues!

Timed out and failed, 1-2. Josh

Adminned at 08 Aug 2022 08:22:24 UTC

Add a new subrule to the rule Bot Loadout titled “Little Leagues”:

If they do not already have one, an Operator may purchase a Mini Bot by paying ₩1,000 and gaining a Mini Bot.

In the rule titled “Bot Loadout”, reword the second line and the four bullet points below it to the following:

Each Operator possesses exactly one Bot, whose characteristics are publicly tracked. In addition, each Operator may have up to one Mini Bot, although each Operator defaults to not having a Mini Bot.

The characteristics that each Bot and Mini Bot must have are as follows:
* A name, which may be freely selected by the Bot’s Operator, must be different than each other Bot’s and Mini Bot’s name and is flavour text
* An Engine, which is by default a Petrol motor for Bots and an Electric motor for for Mini Bots
* A Chassis, which is by default an Apex Systems X1500 for Bots and a Frictionless Inquisitor for Mini Bots
* An ordered list of Systems, of which a single Bot may have between none and a number equal to the number of hardpoints on the Bot’s Chassis, defaulting into none

Mini Bots must also have the following Characteristics, and a Mini Bot is considered to be Defunct if any of these Characteristics are not true of it:
* The Chassis may not have a cost exceeding ₩3,350
* The Engine may not have a cost exceeding ₩4,000
* The Systems used may not exceed a total value of ₩2,000

Move the last sentence of the subrule “The Arena” to the end of the rule “BotScript”, prior to the first subrule, and reword it to the following:

Relative to each Bot’s and Mini Bot’s Script, the Bot or Mini Bot who is performing the Script may be referred to as the Actor, and any other Bot or Mini Bot participating in a Bout with the Actor may be referred to as an Opponent.

In the subrule titled “Engines”, change the first line to the following:

A Bot’s or Mini Bot’s Engine has the following characteristics: a fuel type (which also acts as its name), a one-off cost, and a power output. The characteristics of each type of engine can be found below.

In the subrule titled “Engines”, change the text reading:

At any time as an atomic action, an Operator whose Readiness is Workshop may:
* Either increase their money by the effective one-off cost of their engine or add their engine and its condition to their Spare Parts Bin.
* Replace the Engine of their Bot with another of any Condition by paying the Effective One-off Cost of the new Engine. If the new Engine is present in their Spare Parts Bin, they may instead remove it from their Spare Parts Bin.

To the following:

At any time as an atomic action, an Operator whose Readiness is Workshop for either their Bot or Mini Bot may do the following for the corresponding Bot or Mini Bot:
* Either increase their money by the effective one-off cost of their Bot’s or Mini Bot’s Engine and then remove it, or add their Bot’s or Mini-Bot’s engine and its condition to their Spare Parts Bin.
* Either set the Engine of the previously referred to Bot or Mini Bot with another engine of any Condition by paying the Effective One-off Cost of the new Engine, or set the previously referred to Bot’s or Mini Bot’s Engine to one matching an Engine in their Spare Parts Bin and then remove that Engine from their Spare Parts Bin.

In the subrule titled “Chassises”, change the first line to the following:

A Bot’s or Mini Bot’s Chassis has the following characteristics: a model (which also acts as its name), a cost, a number of hardpoints, and a consumption. The characteristics of each type of chassis can be found below.

In the subrule titled “Chassises”, change the text reading

At any time as an atomic action, an Operator whose Readiness is Workshop may:
* Either increase their money by the effective one-off cost of their Chassis or add their Chassis and its condition to their Spare Parts Bin.
* Replace the Chassis of their Bot with another of any Condition by paying the Effective One-off Cost of the new Chassis. If the new Chassis is present in their Spare Parts Bin, they may instead choose to remove it from their Spare Parts Bin rather than paying the Effective One-off Cost.

To the following:

At any time as an atomic action, an Operator whose Readiness is Workshop for either their Bot or Mini Bot may do the following for the corresponding Bot or MIni Bot:
* Either increase their money by the effective one-off cost of their Bot’s or Mini Bot’s Chassis and then remove it, or add their Bot’s or Mini Bot’s engine and its condition to their Spare Parts Bin.
* Either set the Chassis of the previously chosen Bot or Mini Bot with another Chassis of any Condition by paying the Effective One-off Cost of the new Chassis, or set the previously referred to Bot’s or Mini Bot’s Chassis to one matching an Chassis in their Spare Parts Bin and then remove that Chassis from their Spare Parts Bin.

If the subrule titled “Systems”, change the first line to the following:

A Bot’s or Mini Bot’s Systems can each have the following characteristics: a name, a cost, a consumption, and an effect. The characteristics of each type of System can be found below.

In the subrule titled “Systems”, change the text reading:

At any time, an Operator whose Readiness is Workshop may add a System of a desired Condition to their Bot by spending its Effective Cost or removing that system from their Spare Parts Bin as long as that system is present in their Spare Parts Bin at that condition. An Operator whose Readiness is not Set may remove a System from their Bot at any time by either increasing their money by 50% of the Effective Cost of the system being removed or adding that system at the appropriate condition to their Spare Parts Bin.
The list of a Bot’s Systems represent the mounted positions of those systems, listed from front to back. When a System Effect refers to the Exposed System of a Bot, it means its frontmost System (if the Bot is facing the Bot using the Effect) or its rearmost System (if it is not). While a Bot is Flipped, none of its Systems are Exposed.
While a System has a Condition of 0%, then its Effect is considered to be “No effect.”, and it is skipped when determining the frontmost or rearmost System of a Bot.
If a System effect is preceded by “Passive:”, then it has no effect when used, and instead applies to a Bot with that System at all times.

To the following:

At any time, an Operator whose Readiness is Workshop for either their Bot or Mini Bot may add a System of a desired Condition to the Corresponding Bot or Mini Bot by spending its Effective Cost or removing that system from their Spare Parts Bin, as long as that system is present in their Spare Parts Bin at that condition. An Operator whose Readiness is not Set for either their Bot or Mini Bot may remove a System from the Bot corresponding Bot or Mini at any time by either increasing their money by 50% of the Effective Cost of the system being removed, or adding that system at the appropriate condition to their Spare Parts Bin.
The list of a Bot’s and Mini Bot’s Systems represent the mounted positions of those systems, listed from front to back. When a System Effect refers to the Exposed System of a Bot or Mini Bot, it means its frontmost System (if the Bot or Mini Bot is facing the Bot or Mini Bot using the Effect) or its rearmost System (if it is not). While a Bot or Mini Bot is Flipped, none of its Systems are Exposed.
While a System has a Condition of 0%, then its Effect is considered to be “No effect.”, and it is skipped when determining the frontmost or rearmost System of a Bot and Mini Bot.
If a System effect is preceded by “Passive:”, then it has no effect when used, and instead applies to Bots and Mini Bots with that System at all times.

In the subrule “Systems”, for each System with the word “bot” in its effect that is not part of another word, change that word to “Bot or Mini Bot”.

Reword the text of the subrule titled “Repair Wrench” to the following:

As an atomic action, when their readiness is set to workshop, an operator may:
* Set the condition of any part on their Bot, Mini Bot or in their spare parts bin to any condition higher than it previously was
* Decrease their money by the formula: ((new effective cost of the part) - (previous effective cost of the part)) * 1.25

Throughout the subrules “Scratch Damage” and “Statuses”, change each instance of the word “bot” that is not part of another word to “Bot or Mini Bot”, and change each instance of the word ‘bots” that is not part of another word to “Bots or Mini Bots”.

Change the first two paragraphs of the rule “BotScript” to the following:

Each Bot and Mini Bot has a Script, being a list of up to ten Triggers, each Trigger having a corresponding Reaction. Up to two Triggers may also be optionally combined into a single Trigger. This is formatted as “A and B”, where A is the first Trigger being combined and B is the second one. Combined triggers are accompanied by a single Reaction as normal. Bots’ and Mini Bots’ Scripts are tracked privately by the Announcer.
An Operator may change their Bot’s or Mini Bot’s Script at any time by privately informing the Announcer of this.

Throughout the list of possible Triggers and Reactions in the rule “BotScript”, change each instance of the word “Bot” that is not part of another word to the following: “[Bot/Mini Bot]”

Beginning with the part or the rule “BotScript” reading “To run a Script” and continuing through to the end of the second to last paragraph of the rule (not counting the subrules), change each instance of the word “bot” that is not part of another word to “Bot or Mini Bot”.

In the rule “Income”, change the word “bot” to “Bot and Mini Bot, up to the maximum value of 100%”.

Change the effect of the System known as “LED Banner” to the following:

Displays the name of every distinct Operator that this Bot has defeated in a Bout while using this System; these names are publicly tracked. If the Operator of this Bot also owns a Mini Bot, they may also include up to two names of Operators that that Mini Bot has defeated. Has no other effect.

Change the text of the rule “Bouts” to the following, without changing the subrules of that rule:

Operators pit their Bots and Mini Bots against each other in Bouts. At any time, each Bot and Mini Bot may be engaged in at most one Bout. The number of bouts each Bot and Mini Bot has been engaged in is publicly tracked, and includes announced bouts that include the bot that are yet to be resolved. This publicly tracked value may be referred to as the Bout Count.
Bots and Mini Bots have a Readiness, which is publicly tracked and may be either Workshop, Ready, Staging, or Set, and which defaults to Workshop.
* When a Bot’s or Mini Bot’s Readiness is Workshop it is not Trashed, the Operator of that Bot or Mini Bot may set the Readiness of that Bot or Mini Bot to Ready at any time
* When a Bot’s or Mini Bot’s Readiness is Ready and they are named in an Announcement Post then the Announcer should set their Readiness to Staging
* When a Bot’s or Mini Bot’s Readiness is Staging, the Operator of that Bot or Mini Bot may set the Readiness of that Bot or Mini Bot to Set at any time.
* When a Bot’s or Mini Bot’s Readiness is Set and they are participating in a Bout then the Announcer should set their Readiness to Workshop
Changes to any of a Bot’s or Mini Bot’s physical hardware components by that Bot’s or Mini Bot’s Operator (i.e. anything defined in the rule Bot Loadout) may only be made when the Corresponding Bot’s or Mini Bot’s Readiness is Workshop. Changes to a Bot’s or Mini Bot’s software by that Bot’s or Mini Bot’s Operator (i.e. anything defined in the rule BotScript) can only be made when the Bot’s or Mini Bot’s Readiness is Workshop, Ready or Staging.
If, at any point during a Bout, one of the participating Bots or Mini Bots has had their Readiness set to Set for the last 48 hours and the other has not changed their Readiness from Staging since the Announcement Post for that Bout, then the Bot or Mini Bot whose Readiness is Staging forfeits the match and the other Bot or Mini Bot is the Winner for that Bout.
Mini Bouts are a special type of Bout, which is still treated as a Bout for the purposes of anything that refers to a Bout, with the exception that there are always 0 Configuration Variations.
As a Daily Action, the Announcer may Announce any number of upcoming Bouts and Mini Bouts, by randomly selecting two Bots using the Selection Criteria for Bouts in this rule for each Bout, selectings two Mini Bots using the Selections Criteria for Mini Bouts in this rule and making a post Announcing their names.
The Selection Criteria for selecting Bots to engage in a Bout is:
* If a Bot has a higher Bout Count than any other Bot, they may not be selected by the Announcer, except if there are no other available Bots to select.
* If a Bot has a Readiness that is not Ready, it may not be selected by the Announcer.
* The random selection of eligible Operators is weighted towards Bots with a smaller Bout Count - for each eligible Bot, subtract the current Bout Count for that Bot from the highest Bout Count of all eligible Bots then add 1 to get the weighting that the random selection will use.
The Selection Criteria for selecting Mini Bots to engage in a Mini Bout is:
* If a Mini Bot has a higher Bout Count than any other Mini Bot, they may not be selected by the Announcer, except if there are no other available Mini Bots to select.
* If a Mini Bot has a Readiness that is not Ready, it may not be selected by the Announcer.
* The random selection of eligible Operators is weighted towards MIni Bots with a smaller Bout Count - for each eligible Mini Bot, subtract the current Bout Count for that MIni Bot from the highest Bout Count of all eligible Mini Bots then add 1 to get the weighting that the random selection will use.
Whenever the Announcer is required to randomly generate an outcome as part of administering a Bout they may do so privately.


Throughout the subrules “When Push Comes to Shove”, “Evasion”, “The Arena”, and “Ending a Bout”, do the following:
For each instance of the word “bot” that is not part of another word, change it to be “Bot or Mini Bot”
For each instance of the word “bots” that is not part of another word, change it to be “Bots or Mini Bots” with the exception of the last instance of the word “bots”
For each instance of the word “bot’s” that is not part of another word, change it to be “Bot’s or Mini Bot’s”

Change the last paragraph of the subrule Ending a Bout to the Following:

When a Bout has Ended, the Announcer posts an entry to the blog summarising the events of the Bout and its Winner. All Operators who had Bots in the Bout gain ₩1,000, plus ₩500 for each Opponent. Likewise, all Operators who had Mini Bots in the Bout gain ₩750 plus ₩250 for each Opponent. When these values are awarded, the Readiness of all Operators to have participated in that Bout are set to Workshop if they are not already at that value. Once this summary post has been posted, that Bout is considered to be fully concluded and may have no further impact on the gamestate.

If https://blognomic.com/archive/tattlebots passed, reword the subrule “Secret Loadouts” to the following:

If a Bot or Mini Bot’s Readiness is Ready, and it has no Systems, then that Bot or Mini Bot is considered to have a Secret Loadout. A Secret Loadout is an ordered list of Systems that matches a subset of the Systems in that Operator’s Spare Parts Bin, and which must obey the same rules as if that list of Systems were the ones applied the Bot or Mini Bot; a Secret Loadout defaults to an empty list. While a Bot’s or Mini Bot’s Readiness is Ready, the Operator of that Bot may change their Bot’s or Mini Bot’s Secret Loadout at any time by privately informing the Announcer of this.

When the Announcer has been informed of a Secret Loadout by a given Operator, they must—immediately prior to changing that Operator’s Bot’s or Mini Bot’s Readiness to Staging—perform an atomic action called Kitting Out as follows:
* Removing the set of Systems matching the Bot’s or Mini Bot’s Secret Loadout from that Bot’s or Mini Bot’s Operator’s Spare Parts Bin
* Setting the Systems of the Bot or Mini Bot to match their Secret Loadout, in the specified order, with the same Conditions they had while in the Spare Parts Bin

This took a long time. If this infringes on Fair Play under spam, I’ll withdraw this, but as Fair Play says that spam is subjective and the concept this proposal introduces really needs this much text, I’d appreciate it if y’all deemed this NOT a fair play violation. Aside from that: TLDR; This proposal introduces Mini Bots, which piggy back off of most of the existing rules with some exceptions. They are intended to be a small scale supplemental to pick up the pace of the game a bit, while maintaining the current schedule. Most of the text introduced in this proposal is incorporating Mini Bots into the preexisting ruleset. If anyone has minor quibbles about the design after the edit window please consider introducing changes via proposal/cfj (as required), as this took a LOT of time. If this passes, I apologize to whichever admin ends up enacting this. If nobody else wants to enact this, just wait for me to notice the result (or ping me on discord) and I’ll get it myself.

Friday, August 05, 2022

Proposal: Taunting, but better

Passes 4-0. TDS

Adminned at 08 Aug 2022 01:47:06 UTC

Change the wording of the rule Taunt from:

An Operator may Taunt another Operator (the Taunt Target) at any time provided that the following is true:

To

An Operator may Taunt another Operator (the Taunt Target) at any time provided that any following are true:

Add another line to the rule, before the last line:

If all three of the previous conditions are true, the operator taunting the Taunt target may add one the amount of red mist given to the Taunt Target additionally.

The rule seeks to make it clear that you can taunt anyone, but rewards you for holding your tongue till right before the bout.

Proposal: Tattlebots

Timed out unpopular, 1-5. Josh

Adminned at 07 Aug 2022 19:38:34 UTC

Create a new subrule of the rule “Bot Loadouts” entitled “Secret Loadouts” as follows:

If an Operator’s Readiness is Ready, and their Bot has no Systems, then that Operator’s Bot is considered to have a Secret Loadout. A Secret Loadout is an ordered list of Systems that matches a subset of the Systems in that Operator’s Spare Parts Bin, and which must obey the same rules as if that list of Systems were the ones applied to the Operator’s Bot; a Secret Loadout defaults to an empty list. While an Operator’s Readiness is Ready, that Operator may change their Bot’s Secret Loadout at any time by privately informing the Announcer of this.

When the Announcer has been informed of a Secret Loadout by a given Operator, they may—immediately prior to changing that Operator’s Readiness to Staging—perform an atomic action called Kitting Out as follows:
* Removing the set of Systems matching the Operator’s Secret Loadout from that Operator’s Spare Parts Bin
* Setting the Systems of the Operator’s Bot to match their Secret Loadout, in the specified order, with the same Conditions they had while in the Spare Parts Bin

Reword the item in the rule “Bouts” that reads “When an Operator’s Readiness is Ready and they are named in an Announcement Post then the Announcer should set their Readiness to Staging” to read:

When an Operator’s Readiness is Ready and they are named in an Announcement Post then the Announcer should set their Readiness to Staging, after Kitting Out that Operator if they have a Secret Loadout

This is a tricky rule to write—feedback welcome.

Story Post: Announcement #19

Special Briefing: Report to the Chair of the Standing Committee for Regional Stability and Peace
Eyes Only

19h47, 02/09/44, NEW CRESCI:

The BlogsBot League Finals continue, with today’s announcement of a new prize fight: two of the very top seeds will be meeting tomorrow, SingularByte’s Hard Hat against Trapdoorspyder’s Annoy-o-Tron. Potentially this could be a map with geopolitical ramifications; Trapdoorspyder represents a minority faction and has become an emblematic athlete for that community, while Hard Hat has been embraced as a symbol of an intolerant tendency within the territory. The potential for violence in the aftermath of this Bout is low but not zero; it is recommended that the embassy be put on high alert and security staff be prepared for overtime requirements.

MEMO from the Chair of the Standing Committee for Regional Stability and Peace
Eyes Only

20h08, 02/09/44, CALLE CITY

Thank you for your update, Ambassador - we believe some details were missing, however - are there to be any modifications to the arena?

MEMO to the Chair of the Standing Committee for Regional Stability and Peace
Eyes Only

20h12, 02/09/44, NEW CRESCI:

Apologies, ma’am; Bumpers will be up, and the new House Bot, Cool Hand Luke, will be a participant. I believe that the best odds can be found at betblogbot.com.

Story Post: Bout #23: CrowBot2000 vs Credit Score: F [Raven1207 vs lendunistus]

It looks like Raven1207 has invested some money in this Bout - not so much in CrowBot, which remains one of the cheaper bots in the League, but in staging. For those listening to us on Radio BlogBot, thousands of crow feathers are falling from the ceiling while orchestral music plays. By contrast, Credit Score: F is simply moving into position with very little fanfare.

CrowBot is being lowered by a crane into position 4 - a single white-light spotlight making it appear like a descending angel - while Credit Score: F is plonking itself unceremoniously into position 16.

There’s the blue light - they’re off!

The crowd roars its appreciation - they’ve been craving the red meat of bot on bot action! CrowBot is straight off from the stocks, moving into position 9. Lendunistus sees this tactical move and responds, pushing Credit Score F into position 13 - just outside of the range of CrowBot’s melee weapons. But Raven is to trigger happy, letting off a huge gout of flame from its flamethrower that doesn’t quite manage to reach Credit Score’s position. Oh! But Credit Score keeps scuttling forward - it’s right on top of CrowBot now, in position 10! Looks like we’re in for a melee slugfest and the crowd loves it!

CrowBot gets the first strike in, bathing Credit Score with another blast of heat from that flamethrower - the paint on Credit Score’s chassis immediately puckers and its articulated joints all look Scorched! But what’s this - Credit Score is pulling out it’s flipper - and it’s found purchase! CrowBot is up and over on its back, defenceless, and that’s when Credit Score goes in with its axe - and then again - two huge chops on the underside of CrowBot from that axe, and CrowBot is - oh! It’s rocked itself back upright This match is still on!

Another blast from that flamethrower and Credit Score is starting to take some serious damage, the systems are warping every time they’re used and that chassis is starting to look very worn - but the flipper still works - there it is! CrowBot is back on its back and has no answer to the problem of being flipped! Two more big hits from that workmanlike hatchet and that’s it - CrowBot’s Apex Systems chassis is split clean down the middle and the Bot cannot compete any longer! The judges have called it -

Credit Score: F wins by TKO!

Proposal: Pumped Up Kicks

Enacted 6-1. TDS

Adminned at 07 Aug 2022 04:31:21 UTC

Throughout the ruleset and gamestate (excluding all votable matters), correct ‘Hydrolic’ to ‘Hydraulic’. Change the Cost of a Hydraulic engine to ₩7,300, and reduce the Money of any Operator whose Bot or Spare Parts Bin has a Hydraulic engine by ₩2,300; if any such Operator does not have ₩2,300 then sell their Systems, from the back to the front and gaining 50% of that System’s full Cost in value from the sale, until they do have enough Money.

Add the following as a new chassis:

| Numenatics Featherlight 44714 || ₩9,110 || 3 || 305

Add the following as new Systems:

| Modular Breakpoint || ₩3,100 || 170 || Passive: The Operator of the Actor may privately message the Announcer to add a System from their Spare Parts Bin to their Bot while their Readiness is Staging, if they have enough spare Hardpoints to do so. The Announcer should add that System to the Actor once its Operator’s Readiness is Set, but before processing the Bout.
| Howitzer || ₩2,600 || 260 || If no Opponent is less than eight spaces away from the Actor then the Condition of all Opponents’ Chassises is reduced by 50% and the Opponents gains the Status Loose
| Ablative Plating || ₩3,700 || 120 || Passive: All Condition loss incurred by the Actor is reduced by 50% and is incurred to this System instead of any other System that it might be incurred to.

Some more top-end systems for high-value bots

Wednesday, August 03, 2022

Proposal: Status Symbiote

Popular at 8-0. Enacted by Brendan.

Adminned at 05 Aug 2022 22:20:16 UTC

Make the rule “Scratch Damage” a subrule of the rule “Bot Loadout” and place it at the end of that rule.

Make the rule “Statuses” a subrule of the rule “Bot Loadout” and place it at the end of that rule.

I am tired of scrolling to the end of the dynastic rules and then back up to remember how different weapons interact.

Story Post: Bout #22: The Dark Lord vs Yvette the Botmistress [Brendan vs chiiika]

Well these two have been trading blows on twitter all morning - either there’s no love lost between them or it’s all a bit of gamesmanship. I’ve always said, BlogBots is played on a hundred-square-foot arena but it really takes place up in the ole noggin, and in Brendan and chiiika we have to masters of the head-game that is BlogBots. Hopefully we’ll see some of their nifty work in the arena as well.

Oh - here we go!

IN THE LEFT, IN POSITION 4! It’s Dark Lord! Looks like the emo teen of this scene has had a bit of a rework - a dark LED banner has been positioned towards the front, as if being used as a tactical shield, and some of the other bits of glittering weaponry look slimmed down - as always, Dark Lord is expensive, but looks somehow more nimble than usual.

AND TO THE RIGHT, IN POSITION 16! Coming in on her third bout in this series, following a win against Credit Score: F and a loss to Hard Hat, it’s Yvette the Botmistress! She too has taken some changes; an upgraded chassis can be seen underneath a mound-shaped body, clearly anticipating a flip-heavy attack.

There’s the red light - then the amber - then the blue! It’s on!

Dark Lord is the first mover, and that huge nuclear engine is no joke - Dark Lord slammed across the arena right into Yvette, shoving her back to position 17 - and Yvette answers with those huge crunchy pincers, clanking into Dark Lord and giving it an almighty jolt! That’ll’ve rattled a few bolts Loose!

But no matter, says Dark Lord, and - OH! Oh my goodness! That lighter build-out has worked wonders because there Yvette goes, shoved in one motion out of the arena and into the gutter. What a move! The judges waste no time in deliberating - it’s Dark Lord wins by TKO!

Proposal: Sfida

Times out 4-0. Enacted by Brendan.

Adminned at 05 Aug 2022 22:18:31 UTC

Add a new rule to the ruleset, called Taunt:

Each Operator has a value for Red Mist, which is a publicly tracked integer that defaults to zero.

An Operator may Taunt another Operator (the Taunt Target) at any time provided that the following is true:

*They have not Taunted that Taunt target in the past 48 hours
* Both the acting Operator and the Taunt Target have their Readiness set to Workshop or Ready
* The acting Operator and the Taunt Target are Announced to be participants in the same upcoming Bout, and at least one of those Operators has a Readiness of Staging

When an Operator Taunts a Taunt Target they increase the Taunt Target’s Red Mist to any value up to two higher than their own Red Mist.

When a Bout concludes, the Winner gains additional Money equal to ten times their own Red Mist, and any non-winning participants lose percentage points of Condition to their chassis and exposed system equal to their Red Mist, to minimums of zero; then, the Red Mist of all participants in that Bout is set to zero.

Proposal: Diagnostic Debugging

Times out 4-4. Failed by Brendan.

Adminned at 05 Aug 2022 19:32:10 UTC

Add a section under the BotScript rule:

Within 48 hours of a bout (defined as 48 hours after a story post containing bout results is posted), an operator may privately message the Announcer for their bot’s BotScript execution string.
The BotScript Execution string contains the numbers corresponding to which triggers were activated during each round of play separated with a comma. If a scrambler was used, then it should be indicated as such with an S preceding the trigger that was executed. If no triggers were executed for any other reason then it should be indicated with an X.

The Arena systems were capable of getting information from the bots during a bout. But you just had to be set up to receive them… Interpreting them was as simple as building the script… Or at least that’s the theory.

Proposal: Half Magic

Times out 4-2. Enacted by Brendan.

Adminned at 05 Aug 2022 19:07:52 UTC

The following Systems are Discounted: Grinder, Plate, Targeting Module, Back-Up Battery. If any Bot or any Spare Parts Bin has any Discounted System, remove it, then increase the Money of its Operator by its Cost multiplied by its Condition. Once all Bots have no Discounted Systems, divide the Cost of each Discounted System in the Ruleset by 5, and divide the Consumption of each Discounted System in the Ruleset by 2.

In the effects of the System called Ram, change “Shoving” to “Shoving or Bumping”.

Reduce the Consumption of Taser to 290.

The following Systems are Recalibrated: Mound-Shaped Body, Spikes, Cow Catcher, Lead Weight. Set the Consumption of each Recalibrated System to 30. If the changes to Consumption for Recalibrated Systems would cause any non-Defunct Bot to become Defunct, set the Readiness of that Bot’s Operator to Workshop.

Reframing Josh’s omnibus systems overhaul.

Proposal: Haves and Have Nots

Popular at 7-0. Enacted by Brendan.

Adminned at 04 Aug 2022 15:33:17 UTC

In the Effect for the Grapple system, change “does not have” to “has”.

Did it the wrong way around there.

Monday, August 01, 2022

Proposal: Nerf Scripts

Unpopular at 1-5 with 1 unresolved DEF. Failed by Brendan.

Adminned at 03 Aug 2022 18:42:37 UTC

Append after the sentence in the rule “Ending a Bout” that reads “When a Bout has Ended, the Announcer posts an entry to the blog summarising the events of the Bout and its Winner” the following sentence:

The Announcer also, in this entry, posts the BotScript of the Winner’s Bot.

Proposal: Nerf Spikes

Popular at 8-0 with 1 unresolved DEF. Enacted by Brendan.

Adminned at 03 Aug 2022 18:36:25 UTC

Append to the rule “Scratch Damage” the following:

A Bot that would take Scratch Damage more than once in a given turn only takes Scratch Damage once in that turn instead. (This does not affect how Scratch Damage is multiplied.)

Reword the phrase in the rule BotScript that reads “if an individual move step would take the Bot into an occupied space” to read

if a move reaction would take the Bot into an occupied space

Set to Staging the Readiness of each Operator who is Set.

Josh has recently revealed on Discord that his current interpretation of “individual move step” makes Spikes, at the very least, a terrifying instant-death device just waiting to be exploited. I do not have Spikes, so I would like to fix that.

Maldor Returns

I would like to be un-idled, and participate in this bot madness…

Maldor enters the building where the fabled bot battles take place, he’s travelled far to see them before but entering as a spectator is not the same as entering as an operator. With some money and a bot to his name, he hopes to win the championships. Only time will tell to see how far he makes it…

Proposal: Bruise Banner

At 1-5, Unpopular with the number of Operators not voting AGAINST less than Quorum. Failed by Brendan.

Adminned at 03 Aug 2022 18:34:55 UTC

Add the following to the end of the rule Showboating:

If an LED Banner system is reduced to 0% Condition then its owner’s LED Banner Message loses all names stored in it and is set to blank (and its Consumption is adjusted accordingly).

Story Post: Announcement #18

As was traditional, at the start of the fourth week of the League Finals, a grand ball was held for all of the Operators. A gala black-tie event, it was the hottest ticket of the seasons; models, politicians and moguls all showed up, all hoping to rub shoulders with those brave folks who put their nerves and their Bots on the line for the purposes of entertainment.

And those Operators? Well, it was an opportunity for them to size each other up and psych each other out.

This year, chiiika cornered Brendan over by the shrimp buffet. “You know they only call you the ‘bad boy’ of BlogsBot because you’re bad, right? Like, literally not very good,” she hissed. “How dare you,” he snarled back. “We’ll settle this tomorrow; Arena Hall C, no configurations.” “You’re on,” replied chiiika, biting the head off of a shrimp before walking away.

Meanwhile, lendunistus was warily stalking Raven1207 around a colossal ice sculpture of SingularByte holding Hard Hat. “You shouldn’t put all those feathers on CrowBot,” sneered lendunistus; “I heard that they’re installing flame traps at positions 6 and 3 in Arena Hall F, and you wouldn’t want to get burned.” Sadly, by the time Raven’s translator has relayed this to the visiting Operator and a retort had been formed, lendistus was already deep in conversation with the Ambassador from some Continental nation and the moment had passed…

Proposal: Fixing a little bug

Timed out and failed, 1-5. Josh

Adminned at 03 Aug 2022 17:45:39 UTC

Reword the Effect of the System called “LED Banner” to the following:

Displays the name of every distinct Operator and idle Operator that this Bot has defeated in a Bout while using this System; these names are publicly tracked. Has no other effect.

Clearing up a small ambiguity in the wording of LED Banner. Also changed it to also include anybody that might go idle later on in the dynasty

Proposal: Hook, Line and Sinker

Timed out and enacted, 3-1. Josh

Adminned at 03 Aug 2022 14:24:44 UTC

Add the following System to the list in the rule Systems, above the entry for Grapple:

| Hookshot || ₩800 || 110 || If the opponent is within ten spaces, move the Actor to the square that is immediately adjacent to the Opponent; this System is not affected by Evasion and a Bot that is Evading is still affected by this System.

Rewrite the effect of the system Grapple as follows:

If the target Opponent does not have the status Anchored then this system has no effect. Otherwise, give them the status Anchored [x], where [x] is the name of the Bot using this system .

Add the following as a new Status in the rule Statuses:

Anchored [x] (where [x] is the name of another Bot): Whenever this Bot moves or bypasses, any Bot in the same Bout whose name is [x] (‘the Anchorer’) moves to the closest square to its current position that is in bounds, not occupied by another Bot, and within three squares of the Bot with this Status; if this isn’t possible then the Anchorer retains its position and the Bot with this Status loses this Status. If this Bot has multiple iterations of this Status attributed to multiple named Bots then this impact resolves for those Bots in turn order. A Bot with this Status takes an additional 10 percentage points of Chassis condition damage from any melee System which does Chassis damage. For the purposes of BotScript triggers or System effects, ‘Anchored’ refers to this status in any of its variations.

Some enabling infrastructure for melee builds.