Page 1 of 1

Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 12:26 pm
by TwoPointInfinity
In this scenario the game ends regardless of the vet having alerts. I played as Veteran, I had 1 alert left after the WW and I lynched the last mafia. The game ended immediately and I was confused. Why didn't the game play out and let me decide when to alert. If i had 2 alerts the game would've been my win for sure as i would alert on the nights WW can attack. But that isn't the case. This was a ranked game and I'm sure i had the WW convinced i was out of alerts.
BlankMediaGames please fix this scenario, the game win does not always belong to WW.
Let the game play out, WW should decide to draw game or risk it. If veteran only has 1 alert its up to him to use it on the first night against the ww or second. This game should play out for 3 days and that is okay.
GF vs Vet plays out.
Mafioso vs Vet plays out.
VETERAN VS ANYTHING (except ww) ALWAYS PLAYS OUT. So why does it end here? The ww only has basic defense and rampage basic attack. The veteran has powerful defense and wouldnt die on the night of ww visit. I would even rather the stalemate detector end in a draw but this scenario should play out.

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 12:30 pm
by MysticMismagius
The Vet actually can’t win in this scenario. If you had alerted when the wolf could attack, you’d both kill each other and the game would end in a scummy draw. Because that’s kinda lame, the game just gives someone the win (in this case the WW, because WW wins are harder).

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 12:51 pm
by TwoPointInfinity
I think most of the town would agree that the game is more fair ending as a draw than a win for ww, especially in a ranked game. If ww deserved the win he wouldn't be against the tk at the end.

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 12:53 pm
by MysticMismagius
But a draw means everyone’s time has been wasted. A draw means all that effort went to nothing, nobody wins.

As for the “If WW deserved the win” argument, one could just as easily make the case that if the Veteran really deserved the win, they could have hanged the WW earlier.

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 12:59 pm
by TwoPointInfinity
exactly so the game should either play out or end in a draw immediately. Giving the win to someone just because they never get to win is just catering to those who often lose. An example of this that i can think of is when Epic Games added overpowered Mech robots to fortnite so normal casual players can win games though they didnt deserve them. Although obviously not as serious of an issue, this is still currently not in the right for both parties. The game shouldnt end for someone to win just because it was going to be a draw. Why have draws been declared worse than losing? Is the penalty for a draw the same as losing? If that is the case than what needs to be fixed is that draw shouldnt be a loss in terms of elo.

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 1:19 pm
by MysticMismagius
It’s less “catering to those who lose” and more “draws suck so we’ll avoid situations where a draw is forced as much as possible.” Maybe you don’t agree with that philosophy, and that’s fine, but that’s the way the stalemate detector works.

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 3:13 pm
by TwoPointInfinity
It's really bad and my efforts shouldnt go into someone else winning just because some people don't like draws. This sounds like a bug.

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 3:34 pm
by MysticMismagius
It's not a bug tho, it's literally designed to do this.

Re: Stalemate Detector - WW vs Vet

PostPosted: Tue Oct 08, 2019 6:05 pm
by JacksonVirgo
If Town was so bad they let an NK survive until the end in a 1v1, Town deserves to lose. In a situation of WW/Vet, Town has a 0% chance of winning anyway, just give the win to them man.

Re: Stalemate Detector - WW vs Vet

PostPosted: Sat Oct 12, 2019 3:03 pm
by Jerme
Moving this to not bugs since its intended behaviour.