I don't think you're disagreeing on cactbot, just adding to something I said. The issue is that I put it very, very loosely, so the problem lies in how I worded it
Cactbot does indeed do things automatically, and it bypasses reaction time. Because it's reading information coming from the server live.Quote:
Some features are indeed personal, as they tell you where to go based on what marker you have, but those are specific mechanics.
Well, from the experiences I've had when people I raided with used cactbot (which was loud and you could hear it over voice chat xD it was funny), it was E9S and the mechanics were pretty minute, you still needed to know what to do. But there was a call-out, I think on the pizza slices that was super awkward and came in way too late. They just didn't bother with that one. You still needed to know how to react to it. The call-outs weren't exactly intuitive.
However if we're going to use it in something as straightforward as... maybe Limit Cut? Or, nah, simpler: Construct 7's maths thing. Then yeah, you don't even need to think about it, just stand on the place. I said "It's no different than your raid leader doing it" because I have done call-outs for Construct 7 for 2 different people in my party while still having to resolve my own. If mechanics are straightforward enough, then you'll just need to react accordingly. And if the whole thing is global, then it's even easier. This, however, is assuming a human-like reaction time, which Cactbot does not have.
The rest is, as I said, the fact that Cactbot is a lot more personal, and as you said, instantaneous because it's reading directly from the server. Even in my own analogies, I still point out: Cactbot eliminates human error in terms of mentally resolving a mechanic.
That's the automation part of it: the fact that it does so without human input and instantly. Really, that information was kinda there, so it's not really disagreeing, but it was very loosely worded and just overall not properly conveyed. You're otherwise correct.
