Gauntlet Rant
GhostStalker
✭✭✭✭✭
So I'm in the gauntlet that ends today (Ferengi, Merchant, Communicator)...
Why does it feel like I'm going up against Surak every time? I realize it's because he has three high proficiency scores, but come on, does he have to come up every time?
Literally, just did 3 rounds, all three a wall of Suraks. One Locutus in there, to be fair. And mine was already down for the round. Durp.
Why does it feel like I'm going up against Surak every time? I realize it's because he has three high proficiency scores, but come on, does he have to come up every time?
Literally, just did 3 rounds, all three a wall of Suraks. One Locutus in there, to be fair. And mine was already down for the round. Durp.
2
Comments
I'm really not eager to let this turn into a "Let's complain that f2p players get good things without paying for them, this is socialism" debate.
Obviously what the gauntlet code does after picking the round's opponents is it finds their character with the highest roll score to challenge you. The problem is, Surak has 3 high proficiencies, so he's going to come up often.
I don't really know how you could prevent it, unless there was some code that prevents it from displaying the character you just faced?
I mean they can't be too random, because it might pick an opponent's card with no matching skills. But there's definitely no denying that Surak is likely going to be featured in 3 out of 6 skills, unless the player happens to have a stronger card. That's a lot of "Vulking" Surak.
Sorry, I didn't mean to take it in that direction at all. The issue is the algorithm picks the strongest defender of the players selected which makes sense. But when most players have the same strong defender, that defender always shows up. I don't know if there is an easy way to fix this.
It's also worth remember that DB built gauntlet to get you to spend merits and dil, not to give you long streaks and free stuff. So anything that causes you to need to refresh more and cuts your odds of winning is a feature from their perspective.
You'd be surprised just how many you can gain by simply not refreshing rounds.
Wow... that’s pretty harsh words for the Father of Vulcan Logic... most illogical 😇
They're better, you say? No, they're pretty much all junk. And I'd rather have 7 chances at junk than 3 chances. What kind of game makes me wish I had done WORSE to get more prizes?
Same. I’m finally able to do merit pulls again.
That’s because the higher critical rate only applies to the crew you are facing, not really to your own crew.
At least, it seems that way...
Not according to my statistics:
https://docs.google.com/spreadsheets/d/1sYlf7A6M-kaENSsxoHhiUrpNuv71zNRz50Izi-ARB6E/edit#gid=828863195
Edit: My comment was not actually serious, it was more on bad RNG luck.
Yes, bad luck totally happens.
Thus far in my collection, I've observed a total of 16 failures at 95% of higher (out of ~2300 total rounds) including a 99% failure.
5% Locutus vs 5% Kahless (not FEd) on DIP/SEC
389-768 / 274-546 5%
vs
110-335 / 217-597 5%
Result:
600 189
400 632**
698 270
376 436
459 567
400 892**
=======
2933 2986
So:
1) Unlikely crits (0 vs 2, both at 5%)
2) Average rolls on my side (50.59% average percentile)
3) Above average rolls for the opponent (67.96% avg)
EDIT: I've observed a total of 279 matches with 99% estimated probability and this was the one and only failure so far.
Please see previous statement regarding the need for death by fire while being drawn and quartered, poisoned, irradiated, suffocated, and stung by no fewer than eight swarms of hornets.
SEC-SCI seems to be a good candidate for the first beastly crew release (as it won’t knock down Caretaker too much too soon).
ENG-SCI and SCI-MED can follow some time after.
Species 8472 Invader fits that pair pretty nicely:
SEC (345–698) SCI (236–595)
It is my highest gauntlet SEC roll, and even though it is only a two stat, I use it more often than not. It can crush Surak in the right matchups.
*slow clap*
PM for details.
So long and thanks for all the fish.