Not entirely fair considering you cannot control maps or factions. There isn't a massive rush right now Bannerlord Online is filling some gaps in playtimeotherwise let's finish the tournament with the old matchmaking system, anyway we can't play otherwise without a fix unless you like pain.
Commendable idea, but it's not working either, Destiny Pickups came to a complete halt for weeks because of that.otherwise let's finish the tournament with the old matchmaking system, anyway we can't play otherwise without a fix unless you like pain.
Been a while, but just to recap:With TW basically agreeing it's a bug, should that round not be awarded to the Khuzait faction in retrospect? Arguably a wrong that can be rightened.
To be silent about it and not make a decision, I think is wrong for a tournament managementBeen a while, but just to recap:
DR vs SGM - game bug awarded round at 2:0 (for DR) to SGM and what should have been a 3:0 for DR on that set turned into a 2:3 for SGM.
Since Gotha streamed the entire event and we had a developer response stating that the round should indeed have been awarded to DR, which lead to this issue being fixed in the latest patch, that result should be adjusted by the administration.
However a decision is yet to be made, and while my arguing does come with some bias, I firmly argue that the evidence and consequent conclusion is clear.
If you want to reread the debate or simply watch the event in question, here's Firunien's post including Gothas stream that kicked the question off.
To be completely fair, almost a month long interruption did bring things out of order.To be silent about it and not make a decision, I think is wrong for a tournament management
it was supposed to be fixed, because it was reported earlier but they had to revert it since it was causing crashes.It was fixed with 1.5.7. But we had to revert it since it causes crashes. But we will apply it once again soon.
DR vs SGM was played on february 14 so it was supposed to be fixed and to work like this.
- Fixed a bug that caused the game to end with the wrong side winning when a player killed an enemy in overtime.
We waited for an answer all the time.Losing rounds to bugs/lags/crashes is just a part of the BL experience. Embrace it already..
Losing a round because one of your players gets 1000 ping (not his internet) after the warmup is also games fault..
So is getting a crash mid-game.
Losing a round to a flag bug is on the same playing ground.
To me it seems that SGM didn't agree to count that round as DR win at the time which is on the same level as not restarting round because a player crashes/lags out. And it was their right to do so.
It was actually even less "bad" because at the time it seemed like a feature. The game counted morale instead of living players at the time of the round end.
Adding rounds now is same as a clan deciding to give a round to someone from a month ago because they had a crash in a certain round or someone got stuck on the stairs or a crossbow was bugged and it didn't reload. It might seem like it's a "special" case of a bug. But it's a bug that impacts round outcome just like any other bug/crash/lag.
Obviously you are trying to defend a bug cause it now matters for your team, while we were trying to get this set since we played on february 14.Losing rounds to bugs/lags/crashes is just a part of the BL experience. Embrace it already..
Losing a round because one of your players gets 1000 ping (not his internet) after the warmup is also games fault..
So is getting a crash mid-game.
Losing a round to a flag bug is on the same playing ground.
To me it seems that SGM didn't agree to count that round as DR win at the time which is on the same level as not restarting round because a player crashes/lags out. And it was their right to do so.
It was actually even less "bad" because at the time it seemed like a feature. The game counted morale instead of living players at the time of the round end.
Adding rounds now is same as a clan deciding to give a round to someone from a month ago because they had a crash in a certain round or someone got stuck on the stairs or a crossbow was bugged and it didn't reload. It might seem like it's a "special" case of a bug. But it's a bug that impacts round outcome just like any other bug/crash/lag.
There never was a decision it was just hushed up until now. Even tho we tried to receive an answer.If the admins think that DR should get the round now, with a good explanation why the previous decision should be overturned, so be it, but we don't agree with that.
Just in case you were talking about our game: You asked for a restart after you lost the first round, not during warmup.For example we had a BUG that caused a player to have 1000+ ping even though his connection was normal.
Right after warmup, not during it. We asked for a restart after the 1st round was lost and it was denied. End of story. This is exacly the same only after 3 played rounds not 1.
Oh yes, but thank god the patchnotes stated that this exact bug was fixed right before so it was valid to assume that we win this set by killing both enemies cause that was the gamedesign intention.*edit OH, and also.
This was a known bug at the time. Competative players should have known about it.
Nice to hear that, cause in fact both SGM players could have started teamkilling each other to win this round even faster since that would have granted them the win in this scenario.And if there was a suicide bug like you wrote Gotha then people would agree that it's against the rules before it happend like that.. This was posthumus kinda thingy..
It's game developers responsability to provide us with servers that won't CONSISTENTLY make people lag. In my mind a gamebreaking/unplayable lag caused by something outside of players control is equal to a crash.No, lags are not the same as bugs. These might be a routing issues but these are usually not taleworlds fault or at least not fault of the game itself. It's just caused by a bad routing towards / back from the gameserver location (netherlands) (edit: taleworlds still might be able to improve / fix those routing / package loss issues, but usually it's caused by the server, not the server software nor the game itself).
Also this bug is not comparable with crashes, in this scenario there was simply no way we could have won this round.
Aslo one could argue that during that stage of game development the round was SGMs the second timer ran out to 0. Meaning they lost economy because of a bug..Also this bug is not comparable with crashes, in this scenario there was simply no way we could have won this round.
Yes we asked for a restart because one player had such great lag that it would be better for us that he crashed so at least we would have the extra economy beacuse of it.Just in case you were talking about our game: You asked for a restart after you lost the first round, not during warmup.
There was no rule in the tournament stating anything about this bug. That makes this a fallacy IMO because :Oh yes, but thank god the patchnotes stated that this exact bug was fixed right before so it was valid to assume that we win this set by killing both enemies cause that was the gamedesign intention.
And again in that state game should have ended at 0 and SGM would have better economy because of it.Nice to hear that, cause in fact both SGM players could have started teamkilling each other to win this round even faster since that would have granted them the win in this scenario.
I am just telling you it's not exactly a bug, even tho it's unintended. But that has not really anything todo with this case anyway. Usually you can find out if you lag etc. if you spawn during the warmup phase and walk around. And this entire case is covered by the rules anyway.It's game developers responsability to provide us with servers that won't CONSISTENTLY make people lag. In my mind a gamebreaking/unplayable lag caused by something outside of players control is equal to a crash.
Not valid at all cause if one team has more moral and the team with less moral holds the flag, overtime starts UNTIL their moral surpasses the other teams moral or one team gets wiped out. So this is never supposed to happen. So it's invalid cause SGM was supposed to lose that round.Aslo one could argue that during that stage of game development the round was SGMs the second timer ran out to 0. Meaning they lost economy because of a bug..
This case is covered anyway by the rules and we would've let you restart (we also let RM restart yesterday) but not after we won the first round (and not after waiting a long time without claiming a default before).Yes we asked for a restart because one player had such great lag that it would be better for us that he crashed so at least we would have the extra economy beacuse of it.
After you refused and we accepted your decision.
So that meant we had no chance to win that game. Maybe we'd win if you all decided to teamkill one another but so what ? I don't think thats argument enough.
So again, this bug was fixed and other than crashes / high pings not easy to reproduce really quick without bringing 12 clan players into the same game.So again. Because this bug was known at the time, and had been no precautions in place for in case it happend it is not fair to treat it as a special case of a bug.
Especially since there was no malice on SGMs side aka it wasn't intentional.