TW Sandbagging issue
the TW matchmaking is a problem. a lot of guilds exploits this matchmaking, sandbagging, going with less players, and enjoy easier fights. it shouldn't happen. I'm not sure if you are now realizing t...
Forum Discussion
"Tezza23;c-2114966" wrote:
Don’t find it a problem anymore cause it usually switches around . Plus how do you know they keep people out ? We had 7 not join due to life issues and as a result went down a bracket when we rather have competed for 1st in a higher bracket and a easy to clear board means your guild must work on efficiency, this led to more co operation from our guild than mindlessly throwing teams at them.
doesn't matter your specific case. and if you have 7 not join once, one of the suggestion si that you'll face guild at your level with 7 people out also. or something close.
whats the problem with that ? you afraid of an even matchup?
its not usually switch around, there are guilds that do it regularly to keep win TWs.
Alpha, Global Force, Bravehearts are the obvious examples.
check at the leaderboard: Alpha at #13, with 1,083,000,000 GP defeated, and their GP is 320M. that means that on Average, they are sandbagging 50M per TW. they are beating 270M GP, 4 times. its INSANE. its auto win for them, and it give no chance and no fun to the opponent guild. the difference between 270M go and 320M in rosters, mods and GL is huge.
for example, My guild (TheBigChewbowski) is at #8, with 1,123,000,000 GP defeated, and our GP this month was 280M+-. we beat around 280M 4 times, cause we go with 50 usually - and we also had 1 TW when we had 1 missing player this month.
check kudalty picture. look at the Mods, the Relic difference. the sandbagging is a huge problem, I offered lot of solutions that will help it. if some people in your guild cant participate - it wont hurt your guild - it will make it EVEN, instead of having advantage.
sandbagging need to be stopped so matchups will be even
