Why do so many players overuse the term "sack"? Sacking is when you get 3-4 more procs than your opp. Some kind of huge difference. Not when you kill the last mon with a vio proc and yet the procs for the entire match were close to even. Bothers me so much when people chalk every match up to "sacking."
It’s not really about frequency but rather the timing/impact of the procs. You can have a velajuel proc that literally turns the entire game around for instance
@@dominikzaft2086 but that's not a suck. It's not "unlucky" for vela to have one proc whether or not it has a big impact. Sacking it when you are well beyond the proc rates and your opp is not.
@@dominikzaft2086 in other words, if a vela procs once and it has a big impact as you said then that's a rune quality issue, not bad luck. Anyone blaming a loss on one or two procs and calling it sacking clearly doesn't understand the game or the reasons why things play out the way they do
I agree with u that the term is overused but in the vela case, how is it not literally rng if they proc or not? not sure if i missunderstood but what does it have to do with rune quality?
@@dominikzaft2086if vela procs once and it has a big impact, you should not be saying "look I got sacked." If your rune quality was better or you were smarter with your pick/ban then it wouldn't have been an issue. You should not be saying you got sacked just bc the opp proced once or twice more than you. I say I got sacked when the opp literally procs 5-7 times in a row and I have none. There's no amt of rune quality that can save that. One or two is a whole different ballgame.
I like when you show the runes of your mobs, greetings
Casual 3 am upload pog
Gonna see him alot in Rta now.
damn that fifth game
Banger Video 🪬
was planning to build Varuna until I realised that I somehow never summoned him... 🤣🤣
Asura's wrath
Chat really be trolling every single day “nice sack” like bro didn’t drop from rank 28 to rank 34 smdh
First game you should boost seara then bomb detonate
he dont know what hes doing hes only G3
He didn't even pick her first game
Wut? No seara on first game. Sounds like a bot comment
If he did that it will be just sacrifice his hp elenoa skill 3 rest everybody and have additional turn to one you choose
First: That wasnt even the first game
Second: He explained how wrong that play was right after the match was over.
His kit is underrated
but way to less damage
Why do so many players overuse the term "sack"? Sacking is when you get 3-4 more procs than your opp. Some kind of huge difference. Not when you kill the last mon with a vio proc and yet the procs for the entire match were close to even. Bothers me so much when people chalk every match up to "sacking."
It’s not really about frequency but rather the timing/impact of the procs. You can have a velajuel proc that literally turns the entire game around for instance
@@dominikzaft2086 but that's not a suck. It's not "unlucky" for vela to have one proc whether or not it has a big impact. Sacking it when you are well beyond the proc rates and your opp is not.
@@dominikzaft2086 in other words, if a vela procs once and it has a big impact as you said then that's a rune quality issue, not bad luck. Anyone blaming a loss on one or two procs and calling it sacking clearly doesn't understand the game or the reasons why things play out the way they do
I agree with u that the term is overused but in the vela case, how is it not literally rng if they proc or not? not sure if i missunderstood but what does it have to do with rune quality?
@@dominikzaft2086if vela procs once and it has a big impact, you should not be saying "look I got sacked." If your rune quality was better or you were smarter with your pick/ban then it wouldn't have been an issue. You should not be saying you got sacked just bc the opp proced once or twice more than you. I say I got sacked when the opp literally procs 5-7 times in a row and I have none. There's no amt of rune quality that can save that. One or two is a whole different ballgame.