What I mean by this is explained by example
I use Hk(L), ig88, ig86, JE, jawa
Start off JE goes first, grants everyone TM, and all 4 have max TM
Now RNG decides who goes first
Rather it should be Jawa, ig88, ig86, HK
Do you agree with this? Would it be a buff, or the opposite?
Imo I'd just rather if 88 never went first because it weakens his aoe potential
If jawa always went first at least there's a chance I'll have some debuffs (my jawa has omega aoe)
0
Replies
30 percent TM is already a lot without adding any.
I think screwing around with his recalibrate level might come in handy.
But with hk and jawa tying, you have a 33 percent chance that hk AND jawa will go before 88. 33 percent chance that hk or jawa will go before 88. And a 33 percent chance that 88 will go first. So that is not bad, either.
And people complain about dodge rng. Droids are the king of rng.
No, when multiple characters are brought to 100% TM, the order is random.
I don't know if it's a bug or intended, but it doesn't really make sense. Speed should be the factor for who goes first.
+1. I have posted this with regards to STH both in the bugs/issues section and here but have received no official response.
+1
Not the issue here.
The idea is that when multiple characters reach 100% TM, they'll move according to their speed. So faster characters first, slower last.
Nothing was said about turning more than 100% TM into several turn. TM is capped at 100%, and it should stay that way.
but still, the turnmeter of the fastest character should hit 100% before the others. In the same turn the others also reach 100%, but it feels like a bug to me.
Just because this means that the particular team you're running at this particular moment isn't working exactly the way you want it to doesn't make it a bug.
I'm not sure it's intended. It would make sense to make the fastest characters act first, even when everyone gets at 100% TM at the same time.
We don't need more RNG than we actually have.
Well, when something has been openly discussed as a feature rather than a "bug," pretty much since the game's inception, you can be pretty sure.
Whether you can make an argument that it should be nonetheless changed -- which I disagree with, but that's admittedly just my opinion (and the settled expectations dictated by the established rule set) -- that's another question. But not a bug.