Thursday, July 28, 2022

Proposal: Dodgy mechanics

Withdrawn and failed -SingularByte

Adminned at 29 Jul 2022 19:18:06 UTC

Repeal the rule Evasion, and remove all bullet points that contain the word “evade” from BotScript.

Change to Staging the Readiness of all Operators whose Readiness is Set.

As it stands, evasion has turned into a direct counter to shoving in a way that feels overly excessive - you can literally just keep dodging any time a shove bot is out of weapon range and you stay completely intangible to its only way to interact with the game. With the previous implementation, there was at least the small downside that an opponent could “see” a dodge and choose to act on that info, but now that’s been removed via a rapid cfj. Bots can already be immune to shoving for the low cost of 1 cheap part with no downside, we don’t need a second way to be immune for free.

Comments

Trapdoorspyder:

28-07-2022 05:13:51 UTC

I will vote for once edit window ends.

lendunistus: he/him

28-07-2022 05:40:24 UTC

this’ll make several botscripts illegal, so you should at least set operators to staging

SingularByte: he/him

28-07-2022 05:49:26 UTC

Done

Josh: Announcer he/him

28-07-2022 07:15:37 UTC

Is there no fix?

SingularByte: he/him

28-07-2022 07:29:52 UTC

There may be fixes, but it would fundamentally need a redefinition of what evade is actually meant to do.

Currently it just reduces melee range by 1 and makes you able to be moved through, but I don’t feel the range reduction component of it is significant at all - if you evade an attack, they can just retry it next turn so nothing would change.

Josh: Announcer he/him

28-07-2022 10:59:38 UTC

I guess I’m a little annoyed by this, as the status quo was fine; I acknowledge the unexploited bug but a minimal fix rather than a rushed CfJ that turned out to be too broad in scope has ended up undermining what was a useful tactical strut to the game.

imperial on this, I suppose.

SingularByte: he/him

28-07-2022 11:46:11 UTC

Okay, I think I’ve got another solution instead. I’ll put it up as a new proposal, and people can pick what they prefer.

Since the last iteration of it basically timed out with virtually no votes, I’m not super confident that it’ll pass though.

Brendan: he/him

28-07-2022 12:47:15 UTC

against

Darknight: he/him

28-07-2022 17:29:07 UTC

imperial

Raven1207: he/him

28-07-2022 18:36:33 UTC

against

lendunistus: he/him

29-07-2022 07:25:26 UTC

against

SingularByte: he/him

29-07-2022 07:53:20 UTC

against Withdraw, so this doesn’t hold up the queue once it’s at the front.