• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EDT 07:22
CEST 13:22
KST 20:22
  • 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
Classic Games #3: Rogue vs Serral at BlizzCon7[ASL20] Ro16 Preview Pt1: Ascent10Maestros of the Game: Week 1/Play-in Preview12[ASL20] Ro24 Preview Pt2: Take-Off7[ASL20] Ro24 Preview Pt1: Runway13
Community News
Weekly Cups (Sept 1-7): MaxPax rebounds & Clem saga continues22LiuLi Cup - September 2025 Tournaments3Weekly Cups (August 25-31): Clem's Last Straw?39Weekly Cups (Aug 18-24): herO dethrones MaxPax6Maestros of The Game—$20k event w/ live finals in Paris76
StarCraft 2
General
#1: Maru - Greatest Players of All Time Classic Games #3: Rogue vs Serral at BlizzCon Team Liquid Map Contest #21 - Presented by Monster Energy [G] How to watch Korean progamer Streams. Weekly Cups (Sept 1-7): MaxPax rebounds & Clem saga continues
Tourneys
LiuLi Cup - September 2025 Tournaments Maestros of The Game—$20k event w/ live finals in Paris WardiTV Mondays Sparkling Tuna Cup - Weekly Open Tournament RSL: Revival, a new crowdfunded tournament series
Strategy
Custom Maps
External Content
Mutation # 490 Masters of Midnight Mutation # 489 Bannable Offense Mutation # 488 What Goes Around Mutation # 487 Think Fast
Brood War
General
alas... i aint gon' lie to u bruh... BW General Discussion [ASL20] Ro16 Preview Pt1: Ascent BGH Auto Balance -> http://bghmmr.eu/ The Korean Terminology Thread
Tourneys
[ASL20] Ro16 Group A [ASL20] Ro16 Group B [Megathread] Daily Proleagues Is there English video for group selection for ASL
Strategy
Simple Questions, Simple Answers Muta micro map competition Fighting Spirit mining rates [G] Mineral Boosting
Other Games
General Games
Stormgate/Frost Giant Megathread General RTS Discussion Thread Iron Harvest: 1920+ Nintendo Switch Thread Warcraft III: The Frozen Throne
Dota 2
Official 'what is Dota anymore' discussion
League of Legends
Laptop on Rent in Delhi – Smart Choice for Student
Heroes of the Storm
Simple Questions, Simple Answers Heroes of the Storm 2.0
Hearthstone
Heroes of StarCraft mini-set
TL Mafia
TL Mafia Community Thread
Community
General
US Politics Mega-thread Things Aren’t Peaceful in Palestine Russo-Ukrainian War Thread The Games Industry And ATVI UK Politics Mega-thread
Fan Clubs
The Happy Fan Club!
Media & Entertainment
[Manga] One Piece Anime Discussion Thread Movie Discussion! [\m/] Heavy Metal Thread
Sports
2024 - 2026 Football Thread Formula 1 Discussion MLB/Baseball 2023 TeamLiquid Health and Fitness Initiative For 2023
World Cup 2022
Tech Support
Linksys AE2500 USB WIFI keeps disconnecting Computer Build, Upgrade & Buying Resource Thread High temperatures on bridge(s)
TL Community
BarCraft in Tokyo Japan for ASL Season5 Final The Automated Ban List
Blogs
Collective Intelligence: Tea…
TrAiDoS
A very expensive lesson on ma…
Garnet
hello world
radishsoup
Lemme tell you a thing o…
JoinTheRain
RTS Design in Hypercoven
a11
Evil Gacha Games and the…
ffswowsucks
INDEPENDIENTE LA CTM
XenOsky
Customize Sidebar...

Website Feedback

Closed Threads



Active: 1483 users

Game-changing discovery: Clustered Recall - Page 11

Forum Index > BW General
Post a Reply
Prev 1 9 10 11 12 Next All
niteReloaded
Profile Blog Joined February 2007
Croatia5281 Posts
Last Edited: 2018-05-15 22:13:49
May 15 2018 22:09 GMT
#201
I tried splitting the army (pure goons, as I assumed it would ensure maximum retardation) after stacking them - which would happen in case of failed recall - and it's not hard at all.
I just used a mix of stop and move commands away from the center stacking point.
It seems that in 3-4 seconds they are unstacked.

I'm assuming this will be banned from tournaments after it's been used in one or a couple of high publicity matches.

PvT is slightly skewed in P favor, this might tweak it a percent or two more.

As people practice this tactic, it might make the cornerstone of some strategies.
TT1
Profile Blog Joined December 2008
Canada10010 Posts
May 15 2018 22:21 GMT
#202
On May 16 2018 07:09 niteReloaded wrote:
I tried splitting the army (pure goons, as I assumed it would ensure maximum retardation) after stacking them - which would happen in case of failed recall - and it's not hard at all.
I just used a mix of stop and move commands away from the center stacking point.
It seems that in 3-4 seconds they are unstacked.

I'm assuming this will be banned from tournaments after it's been used in one or a couple of high publicity matches.

PvT is slightly skewed in P favor, this might tweak it a percent or two more.

As people practice this tactic, it might make the cornerstone of some strategies.


ab = tl(i) + tl(pc), the grand answer to every tl.net debate
Freakling
Profile Joined October 2012
Germany1529 Posts
Last Edited: 2018-05-16 12:27:40
May 16 2018 12:16 GMT
#203
So as far as I understand it right now recall takes units positioned inside a 64 px square (~4 by 4 tile area) and moves them inside a 256x256 px (about 8x8 tiles) area, if they fully fit into available walkable, unoccupied space in that area.
Note that this does not quadruple the capacity, though, as the origin area only takes unit position (~unit centre) into account, so for Dragoons they effectively can occupy up to 5x5 tiles (25 Goons in tightest square packing, recall on central Goon).
On arrival, the units have to fully fit into the destination area, though (their collision box boundaries must not overlap the search area boundaries), and search starts from the Arbiter position in the centre. So when the area is unobstructed statistically about half a unit dimension will go to waste on each edge (so one unit dimension overall). So with Dragoons you end up with a 7x7 tile square (49 goons) for unobstructed target space, as I already empirically found.

Let's look at Zealots:
Their collision size is 23x19 px. 129/23 = 5 (truncated), 129/19 = 6. So you can fit up to 6x7 = 42 Zealots into a recall without stacking (that's 3.5 control groups or 84 supply).
Furthermore, 5.5 · 23 = 126.5 < 127 and 19 · 6.5 = 123.5 < 127, so up to 11x13 = 143 Zealots could theoretically be recalled with stacking. This obviously blows the supply limit, and the unit placement might actually not be so optimal as to allow it, but it's probably safe to say that if your whole army supply in in Zealots, you should be able to recall you whole army with this.

Probes are 23x23 px in size.
So with analogous calculations one gets up to 11x11 = 121 Probes in one recall. Testing this is trivial, so excuse while I do it

edit: As predicted, actual maximum recall capacities are quite a bit lower than the ideal, due to inefficiencies in the unit placement algorithm, one of them being that no unit is actually moved directly to the Arbiter position. You can actually only recall 80 Probes at once. Realistically, you can probably get about 100 Zealots, which is still a maxed out supply (without anything else!), though.
iloveav
Profile Joined November 2008
Poland1478 Posts
May 16 2018 13:04 GMT
#204
Id say the risk of not pulling it off is higher than the potential benefits.

Magicbox storming... now that is bonkers :D.
aka LRM)Cats_Paw.
niteReloaded
Profile Blog Joined February 2007
Croatia5281 Posts
Last Edited: 2018-05-16 13:08:39
May 16 2018 13:08 GMT
#205
On May 16 2018 07:21 TT1 wrote:
Show nested quote +
On May 16 2018 07:09 niteReloaded wrote:
I tried splitting the army (pure goons, as I assumed it would ensure maximum retardation) after stacking them - which would happen in case of failed recall - and it's not hard at all.
I just used a mix of stop and move commands away from the center stacking point.
It seems that in 3-4 seconds they are unstacked.

I'm assuming this will be banned from tournaments after it's been used in one or a couple of high publicity matches.

PvT is slightly skewed in P favor, this might tweak it a percent or two more.

As people practice this tactic, it might make the cornerstone of some strategies.



OK, so it's not like that anymore? : ))

I'm not following closely in recent times. I know Flash is killing everyone, but are other Ts > P??
TaardadAiel
Profile Joined May 2017
Bulgaria750 Posts
Last Edited: 2018-05-16 20:18:06
May 16 2018 20:13 GMT
#206
On May 12 2018 02:06 Freakling wrote:
Show nested quote +
On May 12 2018 01:45 TaardadAiel wrote:
On May 12 2018 01:33 Freakling wrote:
On May 11 2018 21:16 ejac wrote:
On May 11 2018 15:29 Freakling wrote:
On May 11 2018 14:41 Azzur wrote:
I went through the whole thread but couldn't find a conclusive answer - is this exclusively as SC:R thing? Could you do this in the old BW 1.16?

No. Same engine, same behaviour. 1.21, 1.16, 1.08 doesn't matter…

Just because it's the same engine doesn't mean everything behaves identically. If they did, then replays from 1.08 should theoretically still work on 1.21 (as replays from 1.16 do), and since they don't, it's obvious that some subtle things have changed. Maybe nothing terribly important, but saying "because game engine" is wrong.


Things like unit and ability stats have been changed (simple data file changes, nothing to do with the engine), some bugs, abuses and other fringe cases have been changed or been worked around (like preventing Siege Tanks from sieging up under landed buildings by making them explode), core engine functionality (such as collision handling, which is what we are talking here) has never been touched post-release.

On May 12 2018 00:04 TaardadAiel wrote:
On May 11 2018 14:24 CHEONSOYUN wrote:
People seem to be ignoring the significance of mines being unable to detonate against this tactic;

Recalls in general will become suddenly more difficult to deal with regardless of the number of units sent.


This. Recalling any number of units with impunity is scary as hell.

It is not any number of units, as I have already briefly discussed, only about up to twice the normal amount. There is an actual limit (though it's about 4 control groups, or 100 supply, worth of goons, more for Zealots…)



I meant that the mine clearance is dangerous out of proportion to the number of units sent, unless the two are related. A normal size recall that is mine-resistant is a frightening proposition.
My two cents regarding that: Right now I am neither here nor there regarding whether units being preset on patrol command helps with the mine clearing.

On the one hand patrol issues an instantaneous attack command to units, which would allow them to diffuse mines before they can explode.
On the other hand Recall resets all orders of affected units (puts them on stop), which would cause the first attack to come out slower.
Now, depending on the exact order of code execution (frame by frame), it is possible that the following happens:
Units are first moved to the new location, then their order status is reset, so that in theory they could be in the old order state for a frame or so, allowing for a fast attack.

I'd suggest the following setup to test this:

Make a control group or two of units (Goons) to be recalled and gather them in a tight pack (no overlapping, just a normal matrix configuration for a standard recall). Make an Arbiter and get the upgrades (all this using cheats or a map editor). Have an enemy Terran minefield laid out at the intended Recall location. Safe the game.
Now Alternatively put the Goons on hold position (which also allows for faster attacks) or stop (slower attacks) command before recalling them. Look how many mines get diffused, and how many goons killed. Repeat this a few times (20 times for each setup at least, to get something approaching statistical meaningfulness).
Alternatively, or in addition, check the game code (OpenBW) and/or relevant data files (although I think this is probably found on the hard-coded level) how exactly Recall is processed internally.


You be the testing guru around this thread, so I won't argue on anything related to the exact mechanism. So far, I gather, it's just an observation that's been tested independently by some pros and presumed to be true until disproven. But it's a mechanic, let's call it that way, that can have a significant impact on the meta - one of the ways to deal with a recalling protoss goes down the drain. Leaving your base as terran with current rough timings where you reach a critical mass of upgraded mech and you assume the opposition has recall capabilities is suddenly much riskier. You either have to invest resources and space in turrets, possibly screwing your timing, or you have to invest APM directly or indirectly (through minimap awareness) on vessel defense. And if the stacked unit recall, even in normal size, has improved mine clearing abilities, then a unit cap on recalls won't bring the meta back where it was (then again, it could force protoss to be pickier in choosing which units they want to recall lest they leave behind a shuttle full of templar or an observer etc.).

I'm very purposefully not mentioning balance, because it is much too early to tell if it would affect balance or rather just the meta. Most of the newer posts around here are almost ethical in nature and I won't get into that, but since I can't follow streams lately, I have no idea if the protoss players have gone from testing to actually using the trick in sponsored matches, the most competitive field we have outside tournaments. If anyone has any info on that, please share.

I highly approve of blizzard's decision on following the matter through and not intervening in any way. We don't even know if the trick will impact the meta, though I assume it will. The big difference would come, as several people have already pointed out, from the way it impacts the meta. If the end result is terran players happily readjusting their timings with a uber-turtly style involving dozens of turrets, making the matchup highly predicable (or by forcing all the terran players to do earlier timing pushes unless they want to lose the game), then an intervention is maybe justified. If it improves the richness of the matchup, then by all means, keep it as it is. The effects on balance are even harder to estimate - it requires statistics with a rather consistent player base (comparable skill or adjusting for ELO) and mappool as well as quite some time to build a reasonably large sample. BW has evolved way beyond the wildest developer dreams and the player base has been instrumental in that, the developers just provided an amazing foundation for creativity to thrive. They know to leave it alone disregarding any intentions they had when designing unit behaviour. Please, have faith in the scene.

Tl; Dr: please don't advocate changes based on some observations from noncompetitive environment and extensive theorycrafting. We just don't have data.
WriterReV hwaiting!
Freakling
Profile Joined October 2012
Germany1529 Posts
Last Edited: 2018-05-16 20:46:04
May 16 2018 20:44 GMT
#207
On May 17 2018 05:13 TaardadAiel wrote:You be the testing guru around this thread, so I won't argue on anything related to the exact mechanism. So far, I gather, it's just an observation that's been tested independently by some pros and presumed to be true until disproven.
Well, most people don't really make any effort to get over their biases, so they tend to observe what they believe anyway, not what is really true. I made multiple tests under controlled conditions, and none of them suggests that unit orders before the recall make any difference in post-recall attacks. Furthermore I looked at the game code (OpenBW) and it resets the movement state (clears all movement orders in queue and sets on stop command AFAIK) for all units before relocating them, so movement state before the recall cannot have any effect.
My guess is that some combination of the following effects is responsible for a (perceived or real) higher mine clearance success rate:
  • Just having more tightly packed stuff attacking makes it more likely a mine will be killed before it can explode (more attacks, higher chance they succeed)
  • More recalled units cover a bigger area making it more likely mines will get stuck directly below a unit, bugging out their movement and thus preventing them from reaching their target and exploding (unless they happen to pick the unit they are under as target)
  • Even if the "normal" amount of mines actually goes off and kills/damages stuff, with a bigger recall there will be left more afterwards, in both absolute and relative terms. Recall 20 Goons and have 10 die to mines immediately – half your recall's dead and the rest probably critically damaged. Have 40 Goons in a wider area and have 10 of them around the edge immediately blown to smithereens – well, you still got 30 goons and probably half of them still undamaged.


But it's a mechanic, let's call it that way, that can have a significant impact on the meta - one of the ways to deal with a recalling protoss goes down the drain. Leaving your base as terran with current rough timings where you reach a critical mass of upgraded mech and you assume the opposition has recall capabilities is suddenly much riskier. You either have to invest resources and space in turrets, possibly screwing your timing, or you have to invest APM directly or indirectly (through minimap awareness) on vessel defense. And if the stacked unit recall, even in normal size, has improved mine clearing abilities, then a unit cap on recalls won't bring the meta back where it was (then again, it could force protoss to be pickier in choosing which units they want to recall lest they leave behind a shuttle full of templar or an observer etc.).
Again: stacking before the recall has no effect on unit position after the recall, unit orders before the recall simply get reset. So a 20 stacked Goon recall does not behave any different from a regular 20 Goon recall.
StylishVODs
Profile Joined December 2005
Sweden5331 Posts
May 16 2018 21:27 GMT
#208
On May 16 2018 22:08 niteReloaded wrote:
Show nested quote +
On May 16 2018 07:21 TT1 wrote:
On May 16 2018 07:09 niteReloaded wrote:
I tried splitting the army (pure goons, as I assumed it would ensure maximum retardation) after stacking them - which would happen in case of failed recall - and it's not hard at all.
I just used a mix of stop and move commands away from the center stacking point.
It seems that in 3-4 seconds they are unstacked.

I'm assuming this will be banned from tournaments after it's been used in one or a couple of high publicity matches.

PvT is slightly skewed in P favor, this might tweak it a percent or two more.

As people practice this tactic, it might make the cornerstone of some strategies.



OK, so it's not like that anymore? : ))

I'm not following closely in recent times. I know Flash is killing everyone, but are other Ts > P??

nah
According to Reach, he is the fastest learner he has ever seen. He start bw only like 2/3 years ago. Infact, his bw history knowledge is so limited, he didn't even know what the map Guillotine was.
funnybananaman
Profile Joined April 2009
United States830 Posts
May 17 2018 02:35 GMT
#209
Idk if this is game changing but pretty dope. might not be that easy to group up units this way when you're in an actual game vs another live person
TaardadAiel
Profile Joined May 2017
Bulgaria750 Posts
May 17 2018 03:57 GMT
#210
[B]On May 17 2018 05:44 Freakling wrote:Again: stacking before the recall has no effect on unit position after the recall, unit orders before the recall simply get reset. So a 20 stacked Goon recall does not behave any different from a regular 20 Goon recall.


I just called the total recall a stacked unit recall, but the observed mine clearance improvement is correlated (not implying causation) to the stacking technique, right?
WriterReV hwaiting!
Freakling
Profile Joined October 2012
Germany1529 Posts
May 17 2018 08:18 GMT
#211
If there is an actual effect and not just observer bias, my guess is that it is simply correlated to the number of recalled units. So it is only correlated with stacking insofar as stacking allows you to fit more units into the target area.
Twinkle Toes
Profile Joined May 2012
United States3605 Posts
May 17 2018 11:34 GMT
#212
I just tried this wow!
If I had known this 5 years ago, I'd have been B+ in ICCup!
Bisu - INnoVation - Dark - Rogue - Stats
TaardadAiel
Profile Joined May 2017
Bulgaria750 Posts
May 17 2018 12:10 GMT
#213
On May 17 2018 17:18 Freakling wrote:
If there is an actual effect and not just observer bias, my guess is that it is simply correlated to the number of recalled units. So it is only correlated with stacking insofar as stacking allows you to fit more units into the target area.

Ok, I might have missed it, but has this been tested? Recalling equal numbers (and compositions) of units "conventionally" and using stacking in the same mine field?
WriterReV hwaiting!
Freakling
Profile Joined October 2012
Germany1529 Posts
Last Edited: 2018-05-17 18:04:53
May 17 2018 13:31 GMT
#214
The units will be placed without overlap upon arrival, so whether they have been stacked or not beforehand makes absolutely no difference.

EDIT: I updated my test map to now also include a normal (25 goons) and big (50 goons) stack as well as a more sophisticated mine layout (now quite effective at blowing up all the goons). I still haven't added any other combat units or Observers into the mix.
A short test run indicates that on average a normal sized recall (stacked or not) directly kills about 3 to 4 of 16 mines, whereas an enhanced recall (from the big stack) clears about 5 to 6 mines on average.

EDIT 2: Might actually be more like 7 to 8 mines for the big stack recall.

EDIT 3: Did some further modification to the map. Stacking is now fully automated, giving you a very reliable setup. The big stack is now 100 goons. I added a counter for recalled goons (gas value). I found that 56 goons can consistently fit into a single recall (112 supply, 4+ control groups). With those huge recalls, average mine clearing rate is about 8, double that of a conventional recall.
zimp
Profile Blog Joined November 2008
Hungary951 Posts
Last Edited: 2018-05-17 22:47:48
May 17 2018 22:47 GMT
#215
On May 17 2018 22:31 Freakling wrote:
The units will be placed without overlap upon arrival, so whether they have been stacked or not beforehand makes absolutely no difference.

EDIT: I updated my test map to now also include a normal (25 goons) and big (50 goons) stack as well as a more sophisticated mine layout (now quite effective at blowing up all the goons). I still haven't added any other combat units or Observers into the mix.
A short test run indicates that on average a normal sized recall (stacked or not) directly kills about 3 to 4 of 16 mines, whereas an enhanced recall (from the big stack) clears about 5 to 6 mines on average.

EDIT 2: Might actually be more like 7 to 8 mines for the big stack recall.

EDIT 3: Did some further modification to the map. Stacking is now fully automated, giving you a very reliable setup. The big stack is now 100 goons. I added a counter for recalled goons (gas value). I found that 56 goons can consistently fit into a single recall (112 supply, 4+ control groups). With those huge recalls, average mine clearing rate is about 8, double that of a conventional recall.

good job. i can't test it now. does it matter if the mines are close to each other or separated?
no terran will have time to plant 10+ mines to all areas in the base...
agentzimp
TL+ Member
Dazed.
Profile Blog Joined March 2008
Canada3301 Posts
Last Edited: 2018-05-18 01:13:38
May 18 2018 01:13 GMT
#216
So how have the results been in game, people? Is it effective? Thats all that really matters, not number crunching.
Never say Die! ||| Fight you? No, I want to kill you.
orvinreyes
Profile Joined June 2007
577 Posts
May 18 2018 06:58 GMT
#217
On May 18 2018 10:13 Dazed. wrote:
So how have the results been in game, people? Is it effective? Thats all that really matters, not number crunching.


Please wait for starcraft's 25th anniversary for conclusive results of the change in meta, thx.
http://youtu.be/LfmrHTdXgK4
kogeT
Profile Joined September 2013
Poland2040 Posts
May 18 2018 10:13 GMT
#218
On May 18 2018 10:13 Dazed. wrote:
So how have the results been in game, people? Is it effective? Thats all that really matters, not number crunching.


I did it few times in 4v4 BGH, works brilliant.
https://www.twitch.tv/kogetbw
L1ghtning
Profile Joined July 2013
Sweden353 Posts
May 18 2018 13:33 GMT
#219
Great! As if recall wasn't already imbalanced enough.
Timebon3s
Profile Joined May 2018
Norway702 Posts
July 06 2018 01:00 GMT
#220
This changed evertything, didnt it?
Anyone seen this in a proper game?
Prev 1 9 10 11 12 Next All
Please log in or register to reply.
Live Events Refresh
RSL Revival
10:00
Season 2: Playoffs Day 1
Reynor vs ZounLIVE!
Tasteless689
Crank 645
IndyStarCraft 107
CranKy Ducklings94
Rex89
3DClanTV 53
LiquipediaDiscussion
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
Tasteless 748
Crank 645
Harstem 121
IndyStarCraft 111
Rex 89
Lowko72
ProTech11
StarCraft: Brood War
Calm 3165
Rain 2943
Sea 2413
GuemChi 2023
Flash 1444
Bisu 1217
Jaedong 782
firebathero 429
sSak 372
BeSt 311
[ Show more ]
Stork 295
EffOrt 238
Snow 235
hero 211
Soulkey 208
Mini 159
Last 139
Light 128
Barracks 119
Soma 110
Shuttle 103
Backho 85
Pusan 82
Aegong 57
TY 48
ToSsGirL 47
Liquid`Ret 46
JulyZerg 46
Mong 40
ggaemo 40
Rush 37
Icarus 23
soO 22
sorry 21
sas.Sziky 20
Sharp 19
Sexy 14
HiyA 11
ajuk12(nOOB) 10
IntoTheRainbow 7
Bale 6
Terrorterran 5
Britney 0
Dota 2
The International84050
Gorgc6038
Dendi560
BananaSlamJamma128
Counter-Strike
olofmeister1701
shoxiejesuss616
x6flipin492
Other Games
B2W.Neo359
crisheroes329
DeMusliM242
Happy191
Mew2King71
Organizations
StarCraft: Brood War
Kim Chul Min (afreeca) 1215
Other Games
gamesdonequick793
StarCraft 2
Blizzard YouTube
StarCraft: Brood War
BSLTrovo
sctven
[ Show 12 non-featured ]
StarCraft 2
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• LaughNgamezSOOP
• Migwel
• sooper7s
StarCraft: Brood War
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
Dota 2
• Ler69
League of Legends
• Jankos831
Upcoming Events
Kung Fu Cup
38m
TaeJa vs SHIN
ByuN vs Creator
The PondCast
1h 38m
RSL Revival
22h 38m
Classic vs TriGGeR
ByuN vs Maru
Online Event
1d
Kung Fu Cup
1d
BSL Team Wars
1d 7h
RSL Revival
1d 22h
Maestros of the Game
2 days
ShoWTimE vs Classic
Clem vs herO
Serral vs Bunny
Reynor vs Zoun
Cosmonarchy
2 days
Bonyth vs Dewalt
[BSL 2025] Weekly
2 days
[ Show More ]
RSL Revival
2 days
Maestros of the Game
3 days
BSL Team Wars
3 days
Afreeca Starleague
3 days
Snow vs Sharp
Jaedong vs Mini
Wardi Open
3 days
Sparkling Tuna Cup
4 days
Afreeca Starleague
4 days
Light vs Speed
Larva vs Soma
LiuLi Cup
5 days
Liquipedia Results

Completed

Copa Latinoamericana 4
SEL Season 2 Championship
HCC Europe

Ongoing

BSL 20 Team Wars
KCM Race Survival 2025 Season 3
BSL 21 Points
ASL Season 20
CSL 2025 AUTUMN (S18)
LASL Season 20
RSL Revival: Season 2
Maestros of the Game
Chzzk MurlocKing SC1 vs SC2 Cup #2
BLAST Open Fall 2025
BLAST Open Fall Qual
Esports World Cup 2025
BLAST Bounty Fall 2025
BLAST Bounty Fall Qual
IEM Cologne 2025
FISSURE Playground #1

Upcoming

2025 Chongqing Offline CUP
BSL Polish World Championship 2025
BSL Season 21
BSL 21 Team A
EC S1
SL Budapest Major 2025
BLAST Rivals Fall 2025
IEM Chengdu 2025
PGL Masters Bucharest 2025
MESA Nomadic Masters Fall
Thunderpick World Champ.
CS Asia Championships 2025
ESL Pro League S22
StarSeries Fall 2025
FISSURE Playground #2
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.