Farmsletje wrote:There are multiple things wrong with this
- First of all as i said at the start i was counting from the moment pepsi shift g'd, which was around 11.15 - 11.18 (don't remember anymore) and jagged had 10k hp at the start of THAT. Jagged died at 11.34 which means that during the battle jagged has taken a maximum of (34 - 16) * 2 * 100 = 3.6k damage from the pd and no more. This means your calculation is way of the mark. I excluded the extra damage he had taken previously because he got 1. an extra hp boost from the t2 upgrade and 2 because at the moment i started the equation he still had 10k hp remaining which is normally a healthy acu.
- As i said in my last point i started counting from the moment pepsi shift g'd, and 1 to 2 seconds after that jaggeds pd started shooting units. Again it doesn't matter what happened before this timeframe.
- Also right before Jagged died pepsi still had enough units left to do atleast another 1k damage to him. This means that the impact of the t2 pd's was even less than 3.6k considering jagged likely still would've died if they only did 2.5k damage
- pepsi was NOT i repeat NOT in a defensive (winning) position. Anything but that. He was literally pd creeping onto jaggeds territory. This makes no sense whatsoever
- Bad decision where? Pushing with a bigger army with a better acu vs a faction that has a slight disadvantage defensively (because of worse pd's and worse t1 tank hp)? If this was a bad idea SOLELY because of the existance of snipemode than it is all the more reason to remove it.
First of all my calculations were made to show that all the damage jagged acu took would have been translated into tanks dying instead, so you cant ignore the fact that he took 4k hp damage before the shift-g, 4k damage would be around 13 strikers.
Espi had 2 t2 pds that had units in range since min 10:32 until min 11:34 and so if those pds were htting units instead of acu, espi army would be bigger and would have been able to defend without having to shift-g, also jagged t2pds wouldnt have been hitting espi units,
With defending winning position i meant that on this certain fight, the outcome would have been in favor for espi with those t2 pds shooting all those units while armies were around same size and jagged t2 pds werent able to shoot espi units.
Farmsletje wrote:The second game was an example about how snipemode influences ladder games. The reason why this is more impactfull than jester/corsair/w/e snipes has already been said before. Because it is way, i repeat WAY easier to accomplish. The main difference is that you have to properly invest in air snipes, but you don't have to invest ANYTHING in a snipemode snipe because whether you go for the snipe or not you will need the units anyway.
You invest a lot on those snipemode snipes, if you fail you are most likely fucked as you noted in the second replay, so i think losing a game is a big investment.
Farmsletje wrote:No, balance changes shouldn't be made to prevent people using certain strategies. HOWEVER if a strategy is super dominant to the point that a lot of people deem it gamebreakingly dominant it definitely should be changed. If this wouldn't be the case then we would still be stuck in old restorer balance where everybody said they were OP. "Want to change the OP restorer? Don't prevent people from trying certain strategies!!" As you can see this argument doesn't hold up.
Ok, so we agree on that, it would be easy to check about 100 last 1vs1 high rating replays and to check how dominant the snipemode thing is, i think the balance team should have done this before of making such change, maybe it is right but i would love to see data, if snipe mode is so relevant i will be up for the change.
Resstorers were changed because it was only winning strat and it was also only available for one faction.
So yeah as with restorers if the snipemode is clearly so dominant winning strategy and the only way to win a game because it has no counter but doing the same then it will be easy to do a database with a certain numbers of replays and to check in how many the snipemode was relevant game ender.