Sunday, July 17, 2022

Proposal: Underlay Underlay Arena

Timed out and enacted, 6-1. Josh

Adminned at 19 Jul 2022 16:00:38 UTC

Add the following as a second paragraph in the rule The Arena:

The Arena for each individual Bout may have differences in configuration, as set out in the rule Configuration. The specific Arena configuration for each Bout must be detailed in the Announcement for that Bout.

Add a new subrule to the rule The Arena, called Configuration:

Prior to Announcing a Bout, the Announcer must generate the Configuration for that Bout. This is an atomic action with the following steps:

* Set the Configuration for that Bout to be is a single row of infinite squares, with those numbered from 1 on the left to 19 at the right being in bounds and all others being out of bounds.
* Randomly determine between zero and two Configuration Variations.
* For each Configuration Variation thus selected, follow its instructions and add them to the Configuration.

Potential Configuration Variations are as follows:

* Physical Obstacles: Add between 2 and 6 squares above or below existing squares in the Configuration. Label them with letters in alphabetical order from left to right, starting with A; all such squares are In Bounds. A Bot can only be shoved from a Square on the same row as itself. When a Bot is Shoved in while occupying a square that has another square above or below it, instead of being moved backwards, it is moved into one of the squares above or below it and is flipped. When a Bot is in a square that is labelled with a letter and moves forwards or backwards, and there isn’t another lettered square that it can move into, it instead moves into the next numbered square in the direction of travel.
*  Trap panels: Add between 1 and 3 trap panels on random squares, each of which may randomly be one of: flip panel, flame panel, explosion panel, shock panel. When a Bot ends its turn on a trap panel it subtracts 5% from its Chassis and Engine, and gains a Status as follows: flip panels give Flipped, flame panels give Scorched, explosion panel gives Loose, and shock panel gives Scrambled. Trap panels are not considered when a Script tests whether a square is empty.
* Bumper sides: When a Bot would go out of bounds, it is instead set to a random square, subtracts 20% Chassis condition, and becomes flipped.
* House bot: There are up to three publicly tracked House Bots, which may be created by the Announcer at any time, which may have any of the Components available to Operator Bots (starting each Bout at 80% Condition), which must have a Bot Value of no more than ₩8,000, and whose Script is publicly tracked. Select one of them at random. In this Bout, square 20 is also In Bounds, and the right-hand-most Bot starts on square 17 rather than square 16; the selected House Bot starts in square 10, facing in a random direction. The House Bot may not the the Winner of the Bout and is not considered for the purposes of any clause in the rule Ending a Bout. House Bots are considered to be present when a line of Script checks whether a square is empty.

Add the following to the bullet list in the rule Statuses:

* Scorched: When an Actor is Scorched, whenever it would use a System it takes scratch damage to that system and to its Chassis
* Loose: When an Actor is Loose, half (rounded up) of any Condition loss incurred by the Chassis or System of that Bot is also applied to that Bot’s Engine.
* Scrambled: When a Bot becomes Scrambled, the Announcer randomises the order of its Script. When it ceases to be Scrambled its Script regains its standard order.

Comments

Lulu: she/her

17-07-2022 10:06:11 UTC

i could do with a bit of scrambling myself

Lulu: she/her

17-07-2022 10:07:27 UTC

also you forgot to change ‘flipped’ to ‘scorched’ in the scorched status

Josh: Observer he/they

17-07-2022 10:08:48 UTC

Ta

SingularByte: he/him

17-07-2022 10:20:47 UTC

Which direction do house bots start off facing?

Josh: Observer he/they

17-07-2022 10:39:44 UTC

Thanks; fixed

Kevan: he/him

17-07-2022 10:59:07 UTC

Do/should obstacles and traps show up when a BotScript checks for “spaces are empty”?

Josh: Observer he/they

17-07-2022 11:02:30 UTC

Thanks; have added clarification.

Trapdoorspyder: he/him

17-07-2022 14:49:00 UTC

I like all of these but House bots. Just mostly because a good chunk of the triggers weren’t designed with multiple enemies in mind, but it seems like a nightmare to write a script for. The rest seem fun though.

Josh: Observer he/they

17-07-2022 15:13:29 UTC

I definitely wrote that bit thinking “let’s just get it down and see what happens lol”

Lulu: she/her

17-07-2022 20:11:32 UTC

for

Trapdoorspyder: he/him

17-07-2022 21:30:14 UTC

for Whatever

thundershrike:

18-07-2022 04:43:35 UTC

My first reaction to house bots were that they seemed to a 2v1 for one player, but I think it shouldn’t be too bad as long as the house bot flips around at some point in its script.

for

Kevan: he/him

18-07-2022 09:10:44 UTC

imperial

Chiiika: she/her

18-07-2022 14:15:10 UTC

for

Brendan: he/him

18-07-2022 14:45:42 UTC

against Struggling with the systems complexity as-is.