Timed out and failed, 3 up, 3 down. Josh
Adminned at 26 Jul 2022 10:49:48 UTC
In BotScript, append the rule named “Very Aggressive” that reads as follows;
If any Effect contains any instances of “The Opponent” which may affect more than one bot is activated, the Announcer should randomly choose a Bot able to be affected to be affected privately.
House Bots rn is a solid wall and let’s fix it
I think it should be decided via distance, not a dice roll
although that might also be a bureaucratic nightmare
SB: this wording would trigger on each Activation, so it works now
len: it *is* a bureaucratic nightmare.
Mild 
- random outcomes seem less interesting here - it should be either the closest Opponent or all Opponents in the operative range, and which of those may vary from System to System. I’d be interested in a more nuanced approach.
I’m expecting this to become irrelevant if my fix or Brendan’s removal goes through, and it’ll work as a stopgap until then.
I’d like any fix for this to come with a refund on my fight
BlogNomic is an online Nomic: a self-modifying game where changing the rules is part of the game. Players make blog posts proposing additions or alterations to the ruleset, discussing and casting votes in the comments: if enough vote in favour, the rules are changed and play continues.
The game has been running since 2003 and resets every month or so. Have a look around the wiki for more information and history. New players are always welcome and can join in the game at any time.
BlogNomic is powered by pMachine ExpressionEngine.
SingularByte: he/him
You might want to have it switch it up each turn who the opponent is, otherwise it might lock to a specific bot all bout long.