• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EST 05:45
CET 11:45
KST 19:45
  • Home
  • Forum
  • Calendar
  • Streams
  • Liquipedia
  • Features
  • Store
  • EPT
  • TL+
  • StarCraft 2
  • Brood War
  • Smash
  • Heroes
  • Counter-Strike
  • Overwatch
  • Liquibet
  • Fantasy StarCraft
  • TLPD
  • StarCraft 2
  • Brood War
  • Blogs
Forum Sidebar
Events/Features
News
Featured News
Intel X Team Liquid Seoul event: Showmatches and Meet the Pros10[ASL20] Finals Preview: Arrival13TL.net Map Contest #21: Voting12[ASL20] Ro4 Preview: Descent11Team TLMC #5: Winners Announced!3
Community News
Starcraft, SC2, HoTS, WC3, returning to Blizzcon!11$5,000+ WardiTV 2025 Championship4[BSL21] RO32 Group Stage3Weekly Cups (Oct 26-Nov 2): Liquid, Clem, Solar win; LAN in Philly2Weekly Cups (Oct 20-26): MaxPax, Clem, Creator win9
StarCraft 2
General
Starcraft, SC2, HoTS, WC3, returning to Blizzcon! RotterdaM "Serral is the GOAT, and it's not close" Weekly Cups (Oct 20-26): MaxPax, Clem, Creator win 5.0.15 Patch Balance Hotfix (2025-10-8) TL.net Map Contest #21: Voting
Tourneys
Constellation Cup - Main Event - Stellar Fest Merivale 8 Open - LAN - Stellar Fest $5,000+ WardiTV 2025 Championship Sea Duckling Open (Global, Bronze-Diamond) $3,500 WardiTV Korean Royale S4
Strategy
Custom Maps
Map Editor closed ?
External Content
Mutation # 498 Wheel of Misfortune|Cradle of Death Mutation # 497 Battle Haredened Mutation # 496 Endless Infection Mutation # 495 Rest In Peace
Brood War
General
BGH Auto Balance -> http://bghmmr.eu/ SnOw's ASL S20 Finals Review [BSL21] RO32 Group Stage Practice Partners (Official) [ASL20] Ask the mapmakers — Drop your questions
Tourneys
BSL21 Open Qualifiers Week & CONFIRM PARTICIPATION [ASL20] Grand Finals Small VOD Thread 2.0 The Casual Games of the Week Thread
Strategy
Current Meta How to stay on top of macro? PvZ map balance Soma's 9 hatch build from ASL Game 2
Other Games
General Games
Stormgate/Frost Giant Megathread Dawn of War IV Nintendo Switch Thread ZeroSpace Megathread General RTS Discussion Thread
Dota 2
Official 'what is Dota anymore' discussion
League of Legends
Heroes of the Storm
Simple Questions, Simple Answers Heroes of the Storm 2.0
Hearthstone
Deck construction bug Heroes of StarCraft mini-set
TL Mafia
TL Mafia Community Thread SPIRED by.ASL Mafia {211640}
Community
General
Russo-Ukrainian War Thread US Politics Mega-thread YouTube Thread Things Aren’t Peaceful in Palestine Dating: How's your luck?
Fan Clubs
White-Ra Fan Club The herO Fan Club!
Media & Entertainment
[Manga] One Piece Movie Discussion! Anime Discussion Thread Korean Music Discussion Series you have seen recently...
Sports
2024 - 2026 Football Thread NBA General Discussion MLB/Baseball 2023 TeamLiquid Health and Fitness Initiative For 2023 Formula 1 Discussion
World Cup 2022
Tech Support
SC2 Client Relocalization [Change SC2 Language] Linksys AE2500 USB WIFI keeps disconnecting Computer Build, Upgrade & Buying Resource Thread
TL Community
The Automated Ban List Recent Gifted Posts
Blogs
Why we need SC3
Hildegard
Career Paths and Skills for …
TrAiDoS
Reality "theory" prov…
perfectspheres
Our Last Hope in th…
KrillinFromwales
Customize Sidebar...

Website Feedback

Closed Threads



Active: 1523 users

a really specific Ninja ZvP nerf (1.4.0 PTR) - Page 20

Forum Index > SC2 General
Post a Reply
Prev 1 18 19 20 All
tarath
Profile Joined April 2009
United States377 Posts
Last Edited: 2011-09-15 04:02:56
September 15 2011 04:01 GMT
#381
On September 15 2011 12:51 weiliem wrote:
This is freaking lame.... Blizzard doesn't like to see Z winning ZvPs, they want P to have 100% win rate in PvZ, so they proceed into massive nerf on the Z race. 1st nerfing fungal, then now completely nullifying the bane drops, which is fking important against the deathball. Blizzard wants to c death ball in every PvZ games.... TQ blizzard....


Not to burden you with facts but....

GSL August:

PvZ: 23.5% (4W, 13L)

PvT: 34% (16W, 31L)

And now your QQing about something that will likely affect <1% of games. I can't even comprehend how you think this "completely nullifies" baneling drops.
scatmango2
Profile Joined November 2010
United States408 Posts
September 15 2011 04:01 GMT
#382
This nerf was totally needed. It was quite retarded when ~3 banelings could kill a a whole protoss army. People qq'ing on zerg's behalf have no idea that this was just a straight up broken mechanic and needed to be fixed.
NEgroidZerg
Profile Blog Joined April 2010
United States244 Posts
September 15 2011 04:07 GMT
#383
So you can avoid any drops by jsut forcefielding around your army?
Yeah
YipCraft
Profile Joined July 2011
United States216 Posts
September 15 2011 04:10 GMT
#384
Hmmm...They really really really REALLY want the zerg to return to the sloppy and terrible roach hydra corruptor vs toss...Nothing...Can...Work anymore if all zerg nerfs are going in effect. Ah well, I guess this time I will pack a flashlight for the dark times of Zerg.
integrity
Profile Joined April 2011
United States1014 Posts
September 15 2011 04:13 GMT
#385
On September 15 2011 13:07 NEgroidZerg wrote:
So you can avoid any drops by jsut forcefielding around your army?

if infestors are out the better option is to run away from the drops
Truedot
Profile Joined August 2011
444 Posts
Last Edited: 2011-09-15 08:10:52
September 15 2011 08:09 GMT
#386
On September 13 2011 08:15 I Hott Sauce I wrote:
Blizz is just raping Zerg now huh

User was warned for this post


Please cite your sources for blizzard raping zerg, and give us details and examples.

About the bane drop situation, under a colossus still counts as "free space" when not occupied, right? Thus a colossus who doesn't have units unit it will basically draw all the banes from the Ols like a magnet, since everywhere else will be packed with stalkers.

Seems like a buff to me.
I used to spend my time not caring about people's language in chat. Until I got hit by blizz. Now I spend my time instigating people to verbal abusive levels, so I can ban them in turn. The circle of life.
Truedot
Profile Joined August 2011
444 Posts
September 15 2011 08:19 GMT
#387
+ Show Spoiler +
On September 13 2011 14:12 DustyShelf wrote:
Hello! I am the creator of the original test (tpyo / BelligerentWombat) and the videos that are linked to. I just wanted to add my 0.02 cents.

First off I should really clarify that I 100% agree with the TL;DR on the original post

That is: "it probably requires unrealistic conditions to take full effect"

I apologise for my sensationalist headline and minimalist commentary on my initial posting on reddit, it has resulted in the community wildly overreacting to the change. It probably wont be an issue for most games. I have performed further testing on more realistic death balls and have clarified that everything should be okay.

Anyway, I did want to clarify a couple of things. The tests were not "failed" in any way. While I appreciate that I used a somewhat unrealistic parameters but I really wanted to see if there was any change between the two versions, hence I made a huge ball of closely clumped together zealots.
I verified my results multiple times. Exactly the same micro and setup was used almost every single time. The holes circled in the OP are not real gaps but merely appear to be due to the perspective of the 3d.
Unless 1.4 also has also made changes to the way one can clump a bunch of zealots those gaps do not exist

To clarify my findings: There is a difference between 1.3 and 1.4 in the way that the drop code is handled. In 1.3 it will permit the dropping of units into a tight cluster of units if it cannot find available space within a specific radius. In 1.4 it will delay the drop command until if finds viable space. However in 1.4 if it fails to find available space within a specific period of time the drop command will be cancelled. This is why in my 1.4 test you can see that most of the overlords fail to drop their full contingent of banelings.

Now while this should not be an issue in most games my fear is that cunning players of the future will find mechanisms to exploit this logic and cause baneling drops to fail. I really wanted to bring light to the fact that there is a flaw in the new logic in 1.4 that should be resolved before people find mechanisms to exploit it. I have added some musings to my thread on battle.net (*shudders*) and I hope the devs take note and consider improving the logic.

One example of such exploits that concern me is how players exploit the "hold" position command on workers in micro fights to make melee troops act idiotically. People seem to champion this as "amazing micro" whereas (as a software engineer) I see it as just a flaw in the system that should be fixed (not that I dislike players that do it but I don't like the fact that the exploit exists at all).

Once more I'd like to apologise for creating the video without the proper commentary alongside it to put into context and for my sensationalist title. I will be more careful with any future postings I make.

Thanks for reading this far.

TL;DR; "it probably requires unrealistic conditions to take full effect" (but there is a difference between the two versions and the tests were genuine)

---------

EDIT: WHOA! Check the post at the top of this page that states:

Show nested quote +
has anyone tested if surrounding your stalkers super tightly with forcefields will make it so banelings cannot even hit the prtosos untis when dropped?


I just did a couple of tests... and by all means we really need to test this further, preferably with two people to make the micro good (as its tough to do it all as one person)..... but from what I can gather It's true.

I don't know if it is unrealistic to have so many sentries/FFs but it is at least possible.

+ Show Spoiler +


And you're correct, And I dont really like that "mechanic" either, of hold position. Not that I don't do it. its another tool in the toolbox, and I've even done this with roaches (since bad players will not realize the range limitation will make them autoattack the workers while on hold position, making it a more resilient worker-kill force), however, the main issue is NOT hold position but "Mineral Walk". Thats the reason it works so well. In BW, this didn't exist.

"Mineral Walk", imo, gets the vote for worst mechanic addition ever. Sure, people are using it to get around or avoid being cheesed, but doesn't that say something about the game itself when a mechanic is abused in such ways to simply survive?

I put 2 and 2 together after a while and decided that I can start scouting Protoss bases with mineral walking drones.

T can do the same thing to protoss.

Meanwhile T is impervious to this.

Just one more way in which they damaged the mechanics of the gameplay for some unknown reason, leading to unintended consequences, and these factors affect balance, because it artificially deflates the value of what a protoss might by trying to tech to in secret, as one of many examples of ways it screws with the game.

I don't see how they ever thought mineral walk was a good idea. ITs the reason hellions are getting nerfed, even though mass hellions can still toast queens and a number of roaches damn quickly.

If only roaches got +2 to light...
I used to spend my time not caring about people's language in chat. Until I got hit by blizz. Now I spend my time instigating people to verbal abusive levels, so I can ban them in turn. The circle of life.
fleeze
Profile Joined March 2010
Germany895 Posts
September 15 2011 20:52 GMT
#388
On September 15 2011 17:19 Truedot wrote:
+ Show Spoiler +
On September 13 2011 14:12 DustyShelf wrote:
Hello! I am the creator of the original test (tpyo / BelligerentWombat) and the videos that are linked to. I just wanted to add my 0.02 cents.

First off I should really clarify that I 100% agree with the TL;DR on the original post

That is: "it probably requires unrealistic conditions to take full effect"

I apologise for my sensationalist headline and minimalist commentary on my initial posting on reddit, it has resulted in the community wildly overreacting to the change. It probably wont be an issue for most games. I have performed further testing on more realistic death balls and have clarified that everything should be okay.

Anyway, I did want to clarify a couple of things. The tests were not "failed" in any way. While I appreciate that I used a somewhat unrealistic parameters but I really wanted to see if there was any change between the two versions, hence I made a huge ball of closely clumped together zealots.
I verified my results multiple times. Exactly the same micro and setup was used almost every single time. The holes circled in the OP are not real gaps but merely appear to be due to the perspective of the 3d.
Unless 1.4 also has also made changes to the way one can clump a bunch of zealots those gaps do not exist

To clarify my findings: There is a difference between 1.3 and 1.4 in the way that the drop code is handled. In 1.3 it will permit the dropping of units into a tight cluster of units if it cannot find available space within a specific radius. In 1.4 it will delay the drop command until if finds viable space. However in 1.4 if it fails to find available space within a specific period of time the drop command will be cancelled. This is why in my 1.4 test you can see that most of the overlords fail to drop their full contingent of banelings.

Now while this should not be an issue in most games my fear is that cunning players of the future will find mechanisms to exploit this logic and cause baneling drops to fail. I really wanted to bring light to the fact that there is a flaw in the new logic in 1.4 that should be resolved before people find mechanisms to exploit it. I have added some musings to my thread on battle.net (*shudders*) and I hope the devs take note and consider improving the logic.

One example of such exploits that concern me is how players exploit the "hold" position command on workers in micro fights to make melee troops act idiotically. People seem to champion this as "amazing micro" whereas (as a software engineer) I see it as just a flaw in the system that should be fixed (not that I dislike players that do it but I don't like the fact that the exploit exists at all).

Once more I'd like to apologise for creating the video without the proper commentary alongside it to put into context and for my sensationalist title. I will be more careful with any future postings I make.

Thanks for reading this far.

TL;DR; "it probably requires unrealistic conditions to take full effect" (but there is a difference between the two versions and the tests were genuine)

---------

EDIT: WHOA! Check the post at the top of this page that states:

Show nested quote +
has anyone tested if surrounding your stalkers super tightly with forcefields will make it so banelings cannot even hit the prtosos untis when dropped?


I just did a couple of tests... and by all means we really need to test this further, preferably with two people to make the micro good (as its tough to do it all as one person)..... but from what I can gather It's true.

I don't know if it is unrealistic to have so many sentries/FFs but it is at least possible.

+ Show Spoiler +


And you're correct, And I dont really like that "mechanic" either, of hold position. Not that I don't do it. its another tool in the toolbox, and I've even done this with roaches (since bad players will not realize the range limitation will make them autoattack the workers while on hold position, making it a more resilient worker-kill force), however, the main issue is NOT hold position but "Mineral Walk". Thats the reason it works so well. In BW, this didn't exist.

"Mineral Walk", imo, gets the vote for worst mechanic addition ever. Sure, people are using it to get around or avoid being cheesed, but doesn't that say something about the game itself when a mechanic is abused in such ways to simply survive?

I put 2 and 2 together after a while and decided that I can start scouting Protoss bases with mineral walking drones.

T can do the same thing to protoss.

Meanwhile T is impervious to this.

Just one more way in which they damaged the mechanics of the gameplay for some unknown reason, leading to unintended consequences, and these factors affect balance, because it artificially deflates the value of what a protoss might by trying to tech to in secret, as one of many examples of ways it screws with the game.

I don't see how they ever thought mineral walk was a good idea. ITs the reason hellions are getting nerfed, even though mass hellions can still toast queens and a number of roaches damn quickly.

If only roaches got +2 to light...


wtf am i reading?
did you even play bw since you want to justify your whining about hold position and mineral walk by making totally wrong statements....
just for the record: mineral walking exists in bw and was used ever since it was discovered. the only limitation is that you need to scout your opponents minerals first to go into a base since there is actually fog of war. it exists in wc3 too btw.
and hold position is a known micro techninque also used in every blizzard rts and noone has EVER complained about it. maybe because it is just doing what it says and is working as intended.

to the subject of workers on hold: in all blizzard rts workers ALWAYS behave like this. this is not a bug but intended by the designers (though it's sort of a work around to a not easy to solve problem technically). it is to buff workers and give them a fighting chance through attacking all at once or surrounding. and it has never been a problem but lead to exciting micro situation and more options.

and wtf has this to do with the thread at all?
Phant
Profile Joined August 2010
United States737 Posts
September 15 2011 21:13 GMT
#389
I'm perfectly fine with them being able to drop in a clustered army, just show me which overloads are empty and which are loaded =)
Truedot
Profile Joined August 2011
444 Posts
September 15 2011 21:22 GMT
#390
On September 16 2011 05:52 fleeze wrote:
Show nested quote +
On September 15 2011 17:19 Truedot wrote:
+ Show Spoiler +
On September 13 2011 14:12 DustyShelf wrote:
Hello! I am the creator of the original test (tpyo / BelligerentWombat) and the videos that are linked to. I just wanted to add my 0.02 cents.

First off I should really clarify that I 100% agree with the TL;DR on the original post

That is: "it probably requires unrealistic conditions to take full effect"

I apologise for my sensationalist headline and minimalist commentary on my initial posting on reddit, it has resulted in the community wildly overreacting to the change. It probably wont be an issue for most games. I have performed further testing on more realistic death balls and have clarified that everything should be okay.

Anyway, I did want to clarify a couple of things. The tests were not "failed" in any way. While I appreciate that I used a somewhat unrealistic parameters but I really wanted to see if there was any change between the two versions, hence I made a huge ball of closely clumped together zealots.
I verified my results multiple times. Exactly the same micro and setup was used almost every single time. The holes circled in the OP are not real gaps but merely appear to be due to the perspective of the 3d.
Unless 1.4 also has also made changes to the way one can clump a bunch of zealots those gaps do not exist

To clarify my findings: There is a difference between 1.3 and 1.4 in the way that the drop code is handled. In 1.3 it will permit the dropping of units into a tight cluster of units if it cannot find available space within a specific radius. In 1.4 it will delay the drop command until if finds viable space. However in 1.4 if it fails to find available space within a specific period of time the drop command will be cancelled. This is why in my 1.4 test you can see that most of the overlords fail to drop their full contingent of banelings.

Now while this should not be an issue in most games my fear is that cunning players of the future will find mechanisms to exploit this logic and cause baneling drops to fail. I really wanted to bring light to the fact that there is a flaw in the new logic in 1.4 that should be resolved before people find mechanisms to exploit it. I have added some musings to my thread on battle.net (*shudders*) and I hope the devs take note and consider improving the logic.

One example of such exploits that concern me is how players exploit the "hold" position command on workers in micro fights to make melee troops act idiotically. People seem to champion this as "amazing micro" whereas (as a software engineer) I see it as just a flaw in the system that should be fixed (not that I dislike players that do it but I don't like the fact that the exploit exists at all).

Once more I'd like to apologise for creating the video without the proper commentary alongside it to put into context and for my sensationalist title. I will be more careful with any future postings I make.

Thanks for reading this far.

TL;DR; "it probably requires unrealistic conditions to take full effect" (but there is a difference between the two versions and the tests were genuine)

---------

EDIT: WHOA! Check the post at the top of this page that states:

Show nested quote +
has anyone tested if surrounding your stalkers super tightly with forcefields will make it so banelings cannot even hit the prtosos untis when dropped?


I just did a couple of tests... and by all means we really need to test this further, preferably with two people to make the micro good (as its tough to do it all as one person)..... but from what I can gather It's true.

I don't know if it is unrealistic to have so many sentries/FFs but it is at least possible.

+ Show Spoiler +


And you're correct, And I dont really like that "mechanic" either, of hold position. Not that I don't do it. its another tool in the toolbox, and I've even done this with roaches (since bad players will not realize the range limitation will make them autoattack the workers while on hold position, making it a more resilient worker-kill force), however, the main issue is NOT hold position but "Mineral Walk". Thats the reason it works so well. In BW, this didn't exist.

"Mineral Walk", imo, gets the vote for worst mechanic addition ever. Sure, people are using it to get around or avoid being cheesed, but doesn't that say something about the game itself when a mechanic is abused in such ways to simply survive?

I put 2 and 2 together after a while and decided that I can start scouting Protoss bases with mineral walking drones.

T can do the same thing to protoss.

Meanwhile T is impervious to this.

Just one more way in which they damaged the mechanics of the gameplay for some unknown reason, leading to unintended consequences, and these factors affect balance, because it artificially deflates the value of what a protoss might by trying to tech to in secret, as one of many examples of ways it screws with the game.

I don't see how they ever thought mineral walk was a good idea. ITs the reason hellions are getting nerfed, even though mass hellions can still toast queens and a number of roaches damn quickly.

If only roaches got +2 to light...


wtf am i reading?
did you even play bw since you want to justify your whining about hold position and mineral walk by making totally wrong statements....
just for the record: mineral walking exists in bw and was used ever since it was discovered. the only limitation is that you need to scout your opponents minerals first to go into a base since there is actually fog of war. it exists in wc3 too btw.
and hold position is a known micro techninque also used in every blizzard rts and noone has EVER complained about it. maybe because it is just doing what it says and is working as intended.

to the subject of workers on hold: in all blizzard rts workers ALWAYS behave like this. this is not a bug but intended by the designers (though it's sort of a work around to a not easy to solve problem technically). it is to buff workers and give them a fighting chance through attacking all at once or surrounding. and it has never been a problem but lead to exciting micro situation and more options.

and wtf has this to do with the thread at all?



I played bood war for 10 years. scvs would stack, but their movement would still be impeded by non harvesting units. thus, its not the same as in this game.

hold position is only lame in relation to this "trick". did I say hold position was bad all around? Its been in RTSes since around the dune2000 era.

wtf am I reading?
I used to spend my time not caring about people's language in chat. Until I got hit by blizz. Now I spend my time instigating people to verbal abusive levels, so I can ban them in turn. The circle of life.
Prev 1 18 19 20 All
Please log in or register to reply.
Live Events Refresh
The PondCast
10:00
Episode 70
CranKy Ducklings33
Liquipedia
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
SortOf 193
OGKoka 189
StarCraft: Brood War
Sea 2104
GuemChi 1645
Jaedong 1504
Flash 1120
firebathero 536
Pusan 368
Leta 275
Soma 244
Stork 243
Hyun 143
[ Show more ]
Light 131
Last 107
Killer 106
hero 77
JulyZerg 74
Barracks 74
ToSsGirL 65
Rush 62
Shine 61
Mong 50
Sharp 50
Backho 46
Snow 43
ZerO 42
Movie 39
zelot 24
Free 18
Terrorterran 16
Noble 15
scan(afreeca) 7
Dota 2
BananaSlamJamma181
XcaliburYe129
League of Legends
JimRising 157
Reynor78
Counter-Strike
edward72
Other Games
summit1g16125
Happy162
crisheroes162
XaKoH 127
Mew2King74
ZerO(Twitch)3
Organizations
Other Games
gamesdonequick536
Counter-Strike
PGL234
StarCraft: Brood War
lovetv 8
StarCraft 2
Blizzard YouTube
StarCraft: Brood War
BSLTrovo
sctven
[ Show 15 non-featured ]
StarCraft 2
• LUISG 23
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• LaughNgamezSOOP
• Migwel
• sooper7s
StarCraft: Brood War
• iopq 14
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
League of Legends
• Jankos1376
• Stunt880
Other Games
• WagamamaTV105
Upcoming Events
LAN Event
4h 15m
OSC
11h 15m
Replay Cast
12h 15m
OSC
1d 1h
LAN Event
1d 4h
Korean StarCraft League
1d 16h
CranKy Ducklings
1d 23h
WardiTV Korean Royale
2 days
LAN Event
2 days
IPSL
2 days
dxtr13 vs OldBoy
Napoleon vs Doodle
[ Show More ]
BSL 21
2 days
Gosudark vs Kyrie
Gypsy vs Sterling
UltrA vs Radley
Dandy vs Ptak
Replay Cast
2 days
Sparkling Tuna Cup
2 days
WardiTV Korean Royale
3 days
LAN Event
3 days
IPSL
3 days
JDConan vs WIZARD
WolFix vs Cross
BSL 21
3 days
spx vs rasowy
HBO vs KameZerg
Cross vs Razz
dxtr13 vs ZZZero
Replay Cast
3 days
Wardi Open
4 days
WardiTV Korean Royale
5 days
Replay Cast
5 days
Kung Fu Cup
6 days
Classic vs Solar
herO vs Cure
Reynor vs GuMiho
ByuN vs ShoWTimE
Tenacious Turtle Tussle
6 days
The PondCast
6 days
RSL Revival
6 days
Solar vs Zoun
MaxPax vs Bunny
Liquipedia Results

Completed

BSL 21 Points
SC4ALL: StarCraft II
Eternal Conflict S1

Ongoing

C-Race Season 1
IPSL Winter 2025-26
KCM Race Survival 2025 Season 4
SOOP Univ League 2025
YSL S2
IEM Chengdu 2025
PGL Masters Bucharest 2025
Thunderpick World Champ.
CS Asia Championships 2025
ESL Pro League S22
StarSeries Fall 2025
FISSURE Playground #2
BLAST Open Fall 2025
BLAST Open Fall Qual
Esports World Cup 2025

Upcoming

BSL Season 21
SLON Tour Season 2
BSL 21 Non-Korean Championship
Acropolis #4
HSC XXVIII
RSL Offline Finals
WardiTV 2025
RSL Revival: Season 3
Stellar Fest
META Madness #9
BLAST Bounty Winter 2026: Closed Qualifier
eXTREMESLAND 2025
ESL Impact League Season 8
SL Budapest Major 2025
BLAST Rivals Fall 2025
TLPD

1. ByuN
2. TY
3. Dark
4. Solar
5. Stats
6. Nerchio
7. sOs
8. soO
9. INnoVation
10. Elazer
1. Rain
2. Flash
3. EffOrt
4. Last
5. Bisu
6. Soulkey
7. Mini
8. Sharp
Sidebar Settings...

Advertising | Privacy Policy | Terms Of Use | Contact Us

Original banner artwork: Jim Warren
The contents of this webpage are copyright © 2025 TLnet. All Rights Reserved.