• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EDT 05:48
CEST 11:48
KST 18:48
  • 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
Code S Season 1 (2026) - RO4 & Finals Preview0[ASL21] Ro4 Preview: On Course12Code S Season 1 - RO8 Preview7[ASL21] Ro8 Preview Pt2: Progenitors8Code S Season 1 - RO12 Group A: Rogue, Percival, Solar, Zoun13
Community News
Code S Season 1 (2026) - RO8 Results2Weekly Cups (May 4-10): Clem, MaxPax, herO win1Maestros of The Game 2 announcement and schedule !11Weekly Cups (April 27-May 4): Clem takes triple0RSL Revival: Season 5 - Qualifiers and Main Event12
StarCraft 2
General
Code S Season 1 (2026) - RO4 & Finals Preview Code S Season 1 (2026) - RO8 Results Code S Season 1 (2026) - RO12 Results Team Liquid Map Contest #22 - The Finalists MaNa leaves Team Liquid
Tourneys
KSL Week 89 2026 GSL Season 2 Qualifiers Maestros of The Game 2 announcement and schedule ! $5,000 WardiTV Spring Championship 2026 SC2 INu's Battles#16 <BO.9>
Strategy
Custom Maps
[D]RTS in all its shapes and glory <3 [A] Nemrods 1/4 players
External Content
Mutation # 525 Wheel of Misfortune The PondCast: SC2 News & Results Mutation # 524 Death and Taxes Mutation # 523 Firewall
Brood War
General
vespene.gg — BW replays in browser BW General Discussion ASL21 General Discussion Pros React to: TvT Masterclass in FlaSh vs Light BGH Auto Balance -> http://bghmmr.eu/
Tourneys
[ASL21] Semifinals B Escore Tournament StarCraft Season 2 [Megathread] Daily Proleagues [ASL21] Semifinals A
Strategy
Fighting Spirit mining rates [G] Hydra ZvZ: An Introduction Simple Questions, Simple Answers Muta micro map competition
Other Games
General Games
Stormgate/Frost Giant Megathread Nintendo Switch Thread Warcraft III: The Frozen Throne Starcraft Tabletop Miniature Game PC Games Sales Thread
Dota 2
The Story of Wings Gaming
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
Vanilla Mini Mafia Mafia Game Mode Feedback/Ideas TL Mafia Community Thread Five o'clock TL Mafia
Community
General
US Politics Mega-thread Russo-Ukrainian War Thread UK Politics Mega-thread YouTube Thread European Politico-economics QA Mega-thread
Fan Clubs
The herO Fan Club!
Media & Entertainment
[Manga] One Piece Anime Discussion Thread [Req][Books] Good Fantasy/SciFi books
Sports
2024 - 2026 Football Thread McBoner: A hockey love story Formula 1 Discussion
World Cup 2022
Tech Support
streaming software Strange computer issues (software) [G] How to Block Livestream Ads
TL Community
The Automated Ban List
Blogs
How EEG Data Can Predict Gam…
TrAiDoS
ramps on octagon
StaticNine
Funny Nicknames
LUCKY_NOOB
Customize Sidebar...

Website Feedback

Closed Threads



Active: 2064 users

Cost Theory and No. of Workers in a Game - Page 2

Forum Index > BW General
Post a Reply
Prev 1 2 3 Next All
ghostWriter
Profile Blog Joined January 2009
United States3302 Posts
January 09 2010 17:39 GMT
#21
On January 10 2010 02:09 lolaloc wrote:
How do I know if I have 24 workers on my mineral line?


Learn to count to 24?
Sullifam
vishrut
Profile Joined April 2009
United States567 Posts
January 09 2010 18:55 GMT
#22
On January 08 2010 22:22 Zona wrote:
Show nested quote +
On January 08 2010 05:09 Xeofreestyler wrote:
The question now is: can BW API be used to lower the optimal number ?

I expect so. By taking into account worker positioning and how long a mineral patch has until it is free for mining by another worker, there should be minimal wandering time. It's something I have been planning to code once I have some free time.

It would be useless to try to do that because the BWAPI checks what to do every frame. I am assuming it takes a lot of instructions to do this and that the computer has to do this for every frame.Most computers will not be fast enough and the game will start to lag.
Wurzelbrumpft
Profile Blog Joined July 2008
Germany471 Posts
January 09 2010 19:13 GMT
#23
On January 10 2010 02:39 ghostWriter wrote:
Show nested quote +
On January 10 2010 02:09 lolaloc wrote:
How do I know if I have 24 workers on my mineral line?


Learn to count to 24?


lol dont tell me you actually count how many workers you make
beam me up scotty, this planet suxX
Severedevil
Profile Blog Joined April 2009
United States4839 Posts
January 09 2010 19:31 GMT
#24
On January 10 2010 04:13 Wurzelbrumpft wrote:
Show nested quote +
On January 10 2010 02:39 ghostWriter wrote:
On January 10 2010 02:09 lolaloc wrote:
How do I know if I have 24 workers on my mineral line?


Learn to count to 24?


lol dont tell me you actually count how many workers you make

I don't, but it's not actually a hard thing to do. Just keep a running tally in your head, and increment it every time you build a worker.

I'm gonna do that from now on.
My strategy is to fork people.
ix
Profile Joined July 2003
United Kingdom184 Posts
January 26 2010 22:55 GMT
#25
The conclusion is that 24 workers on each base with 8/9 patches of minerals is the best number


For 9 mineral patch bases this is incorrect. 24 will saturate an 8 patch base but will have bad wandering on a 9 patch base. You need 27 to saturate a 9 mineral patch base and this can take time to stop wandering, so more may be better in a real game situation.
naonao
Profile Blog Joined November 2008
United States847 Posts
January 26 2010 22:58 GMT
#26
Also continually building workers is not just to saturate the base itself, it is also to have excess prepared for when you expand so that you can quickly have your new expansion saturated.
jodogohoo
Profile Blog Joined March 2008
Canada2533 Posts
January 26 2010 23:13 GMT
#27
On January 27 2010 07:58 naonao wrote:
Also continually building workers is not just to saturate the base itself, it is also to have excess prepared for when you expand so that you can quickly have your new expansion saturated.

truth
Impervious
Profile Blog Joined March 2009
Canada4217 Posts
January 26 2010 23:15 GMT
#28
On January 27 2010 07:55 ix wrote:
Show nested quote +
The conclusion is that 24 workers on each base with 8/9 patches of minerals is the best number


For 9 mineral patch bases this is incorrect. 24 will saturate an 8 patch base but will have bad wandering on a 9 patch base. You need 27 to saturate a 9 mineral patch base and this can take time to stop wandering, so more may be better in a real game situation.


That's not true - they still wander. If the AI was better, and they waited properly, 2 scvs/patch would be the maximum needed. Even with 4+, the amount of money they bring in still increases (although it increases so slowly that it is not worth the investment).
~ \(ˌ)im-ˈpər-vē-əs\ : not capable of being damaged or harmed.
ix
Profile Joined July 2003
United Kingdom184 Posts
Last Edited: 2010-01-26 23:39:22
January 26 2010 23:34 GMT
#29
It is true, test it yourself and give them some time to settle down. Mineral patches with breaks in take less time to settle. If you still doubt I'll make you a replay or something. It can take from 20 seconds to 5 minutes! to settle, depending on the spawn. And no, you are wrong, 2 SCVs cannot max out anything but optimal mineral patches of which there are only 2 to 3 per base. For longer travel patches you must have 3, 2 will only mine 120 (under perfect circumstances like only 1 patch or BWAPI controlled, in reality it will be lower due to wander) of the potential 140.8 (ish! Anyone know the exactly figure for how long mining takes per session of 8 minerals?) per fastest minute per patch.
StRyKeR
Profile Blog Joined January 2006
United States1739 Posts
January 26 2010 23:39 GMT
#30
On January 27 2010 08:15 lMPERVlOUS wrote:
Show nested quote +
On January 27 2010 07:55 ix wrote:
The conclusion is that 24 workers on each base with 8/9 patches of minerals is the best number


For 9 mineral patch bases this is incorrect. 24 will saturate an 8 patch base but will have bad wandering on a 9 patch base. You need 27 to saturate a 9 mineral patch base and this can take time to stop wandering, so more may be better in a real game situation.


That's not true - they still wander. If the AI was better, and they waited properly, 2 scvs/patch would be the maximum needed. Even with 4+, the amount of money they bring in still increases (although it increases so slowly that it is not worth the investment).


With 4+, there is no improvement, assuming optimal waiting and "regular" mineral-hatchery setup, for the same reason that putting more than 4 workers on a gas doesn't help.

Basically, a mineral can only be "ripped" off by a single worker at a time. If a mineral was constantly being ripped off with no rest in between, no amount of workers would increase production. You could derive a theoretical "best mining speed possible" with this metric.
Ars longa, vita brevis, principia aeturna.
Impervious
Profile Blog Joined March 2009
Canada4217 Posts
Last Edited: 2010-01-27 00:29:11
January 26 2010 23:51 GMT
#31
On January 27 2010 08:39 StRyKeR wrote:
Show nested quote +
On January 27 2010 08:15 lMPERVlOUS wrote:
On January 27 2010 07:55 ix wrote:
The conclusion is that 24 workers on each base with 8/9 patches of minerals is the best number


For 9 mineral patch bases this is incorrect. 24 will saturate an 8 patch base but will have bad wandering on a 9 patch base. You need 27 to saturate a 9 mineral patch base and this can take time to stop wandering, so more may be better in a real game situation.


That's not true - they still wander. If the AI was better, and they waited properly, 2 scvs/patch would be the maximum needed. Even with 4+, the amount of money they bring in still increases (although it increases so slowly that it is not worth the investment).


With 4+, there is no improvement, assuming optimal waiting and "regular" mineral-hatchery setup, for the same reason that putting more than 4 workers on a gas doesn't help.

Basically, a mineral can only be "ripped" off by a single worker at a time. If a mineral was constantly being ripped off with no rest in between, no amount of workers would increase production. You could derive a theoretical "best mining speed possible" with this metric.


Go and try it yourself and see. Then, make your own map, where there is 1 patch, and have 3 scv's mine it (since there is no wander, they will mine at max efficiency). Calculate the rate that the minerals are mined. Multiply that by 9 (or whatever number of patches there were that you were testing on), and if they don't equal each other, then there is still going to be an increase with additional workers. They wander in stupid ways, making it inefficient to try to mine out as fast as possible.

EDIT - I just ran a test on it. It's not completely conclusive, however, they were almost identical rates, with a very, very small difference.

36 SCV's, mining 9 patches, at one base, with the setup of the 12 o'clock base on Destination. 3 SCV's, mining 1 patch, directly above the CC, at another base.

I gave them 7 minutes to stabilize, then I set the mineral patches back to the original 1500 per patch.

There were still 64 minerals left at the first base, when the second base ran out. I paused the second that the second base finished returning ALL of the minerals, and I counted the resources left in the crystals, excluding any that were in the hands of the workers. The difference is small, but even with 4 patches, it does not mine as fast as possible. Basically, the best-case scenario is that it is still 64 minerals slower than the fastest possible rate of mining.

I used 3 on a single patch to identify the fastest rate that the minerals can be mined. There was no wandering at all. 4 per patch still had some wandering. Not much, but enough to prevent it from being an ideal situation.
~ \(ˌ)im-ˈpər-vē-əs\ : not capable of being damaged or harmed.
ix
Profile Joined July 2003
United Kingdom184 Posts
Last Edited: 2010-01-27 04:11:53
January 27 2010 00:45 GMT
#32
It's not just theoretical, it's (nearly) achievable. I just did my first 10 minute test after editing the Python 12 o'clock mineral pattern to the maximum value and got these results, starting the test after the 27 workers were completely stable, using APMLive's clock and start/stopping by hand (so small errors) with the workers already being in motion when the test starts (yes, some minerals en route to be delivered, the test was 10 mins so this should even out with those about to be delivered when it ends).

Minerals Gathered: 12,864
Per min: 1,286.4
Per patch per min: 142.9

So my per patch, per min figure earlier was a little low or this happened to come out a little high, it's between 140 and 143 minerals per patch per min. Note how much higher this figure is than the usual values given by, for example the Chinese test, because these are using workers still in wander mode. Wander can still continue with higher worker counts, it's something I'll need to investigate. These will get somewhat lower than optimal values of mineral return for a number of reasons, wander hurts gathering in interesting ways.
Impervious
Profile Blog Joined March 2009
Canada4217 Posts
January 27 2010 00:50 GMT
#33
On January 27 2010 09:45 ix wrote:
It's not just theoretical, it's (nearly) achievable. I just did my first 10 minute test after editing the Python 12 o'clock mineral pattern to the maximum value and got these results, starting the test after the 27 workers were completely stable, using APMLive's clock and start/stopping by hand (so small errors) with the workers already being in motion when the test starts (yes, some minerals en route to be delivered, the test was 10 mins so this should even out with those about to be delivered when it ends).

Minerals Gathered: 12,864
Per min: 1,286.4
Per patch per min: 142.9

So my per patch, per min figure earlier was a little low. Note how much higher this figure is than the usual values given by, for example the Chinese test, because these are using workers still in wander mode. Wander can still continue with higher worker counts, it's something I'll need to investigate. These will get somewhat lower than optimal values of mineral return for a number of reasons, wander hurts gathering in interesting ways.


They could be using a different timing technique than you, which would throw any comparison out the window.....
~ \(ˌ)im-ˈpər-vē-əs\ : not capable of being damaged or harmed.
ix
Profile Joined July 2003
United Kingdom184 Posts
Last Edited: 2010-01-27 00:59:09
January 27 2010 00:57 GMT
#34
I don't think so, the Chinese results are pretty much identical to mine at lower values, like exactly the same for 9 workers and are very similar to my results for wandering workers at higher values.
Impervious
Profile Blog Joined March 2009
Canada4217 Posts
Last Edited: 2010-01-27 01:21:00
January 27 2010 01:05 GMT
#35
Meh. I still think it's better to just do a comparison to a known ideal situation. Like saying "24 workers on 9 patches is 70% of the ideal mining rate", or something along those lines.

EDIT - just tested. 24 workers on 9 patches (setup identical to 12 o'clock on Destination) is 81% of ideal efficiency. 36 workers is just barely under 100% efficient (although close enough that it can be rounded).

36 workers costs a lot more than 24, is it worth the extra 19% efficiency? It costs roughly 30% more to get a 19% increase in mining rate..... Not worth it.....
~ \(ˌ)im-ˈpər-vē-əs\ : not capable of being damaged or harmed.
ix
Profile Joined July 2003
United Kingdom184 Posts
Last Edited: 2010-01-27 01:49:22
January 27 2010 01:21 GMT
#36
I'm giving the numbers. If you want it in that form it's something like:

Probes Minerals/min % of Max (avg)
27 (wander) 1080-1180 87.8%
27 (stable) 1286 100%

It's too time consuming to do a complete list, perhaps at somepoint. I'll write a post about wandering though as that's more interesting. The Chinese result for 27 workers, presumably in wander mode (not sure which race, I always use probes as I play P) was 1056 so as you can see wander is significantly damaging and somewhat variable. I've manged to get 26 workers stable and in theory 25 or 24 may be possible to max out 9 minerals but I think you'd need the AI to do the micro to set it up, it will never settle by itself from what I've seen.

The idea of efficiency and payback time doesn't seem relevant to any kind of reality in Starcraft (unless you can give an example?) for P and T at least. Z's economy is totally different obviously. You're always going to be tactically limited by what is defendable and this dictates how many expansions you take for P and T. You're either powering up units, teching or should be heading toward maximum economy as quickly as possible as far as I see it. It's worth investigating the correct transfer numbers and overproduction to achieve this of course. Maxing out your 9 mineral main and two 7 mineral gas expos requires a total worker count of 57 so I don't think food count is all that important either (better player correct me?). Workers take 12.6 seconds each so 2 or 3 nexuses can produce this is 6 and four minutes. Each worker pays for itself in about one minute, why would you ever choose not to max out?
Impervious
Profile Blog Joined March 2009
Canada4217 Posts
January 27 2010 01:24 GMT
#37
Wandering is a very damaging thing, however, it is unavoidable in any realistic situation. If you could micro every worker perfectly, 2 workers per patch would be about as good as possible (it could be possible that an extra 1 or 2 workers more or less will be the minimum required to be ideal, but it's a good start). Unfortunately, we can't do that. As such, we need to adapt, and find where the most benefit for the least cost is, so we can try to approach that point, allowing us to play efficiently, yet not have to worry about it.
~ \(ˌ)im-ˈpər-vē-əs\ : not capable of being damaged or harmed.
ix
Profile Joined July 2003
United Kingdom184 Posts
Last Edited: 2010-01-27 01:49:01
January 27 2010 01:36 GMT
#38
I've already corrected you on this but you ignored me. 2 workers will only max out 2 or 3 of the mineral patches at a normal main. Stop repeating it, it's not true. I would estimate, based on the 9 worker figure that 18 perfect workers (microed by the AI before anyone accuses me of thinking this is plausible) would produce around 1152 minerals per min, probably somewhat less as the end of mining and journey times fail to line up efficiently between the two workers on suboptimal mineral patches. These economics are possibly an interesting consideration for the BWAPI people.

7 mineral naturals are noticeably less bad for wandering and will quickly max out at 3 workers per patch. Wander seems to set in when I try to optimize with 3x -1. 2.5 per patch is very definitely costing you minerals here.

Perfect micro would max out a normal natural at around 24 or 25 workers, depending on the exact mineral placement (2 or 3 2 worker patches). Wander is avoidable, time or slight over production of workers will make them settle down at a speed that matters at sufficient probe numbers. 22 probes (the 1.5 value people tend to recommend) gather around 1020 minerals per minute, 288 less than 27 stable probes but not much less than unstable ones so the critical thing is achieving stability. The conditions for this I am still figuring out.
Impervious
Profile Blog Joined March 2009
Canada4217 Posts
Last Edited: 2010-01-27 02:05:31
January 27 2010 01:49 GMT
#39
The only reason that it takes 3 workers to mine out a patch is if it is more than 3 squares from the edge of the CC/nexus/hatchery..... They are placed like that for the looks, not for being effective.....

On those patches where it is only 3 squares away, it only takes 2 to max it.....

Lets say there is 3 patches where this happens, out of the 9..... That is 6 workers.

Now, lets also assume that you can micro 5 workers to cover 2 nearby patches that are not able to be mined by 2 workers/patch. 6 patches, times 5 workers/2 patches = 15

Note that I am not assuming that it could actually be something like 5 workers able to mine 3 patches at peak efficiency.....

Add that up - 21 workers to cover 9 patches, at maximum. It can probably be done with 20, and if the resources were placed in a way to be friendly to mining (not fastest, but 3 squares away), then it would take only 18.

Both of those is less than the 24 or 25 you are suggesting..... I don't get where your numbers are coming from.....

EDIT - just ran it. 2 workers, on an ideal patch, is just as efficient as 3 workers on an ideal or non-ideal patch.....

But, through trial and error, as well as studies for how the workers behave over the course of time, it's found that mid 20's is the ideal number - the greatest return for the investment. Above that is okay, as long as it is planned for an expansion. Below that is also okay, as long as there is some kind of all-in attack being planned, because the extra workers would not make their cost back by the time the game should be over, or at least the damage done.

Also, since Zerg is gas-heavy, they don't need as much minerals, and, as such, less drones is actually ideal for them.....
~ \(ˌ)im-ˈpər-vē-əs\ : not capable of being damaged or harmed.
ix
Profile Joined July 2003
United Kingdom184 Posts
Last Edited: 2010-01-27 02:36:05
January 27 2010 02:04 GMT
#40
Nope, make a map and test it. Central mineral patch, 1 extra matrix away from the natural and you will see little gaps between the workers' mining. This is a better patch than the diagonal ones which have larger gaps as they are further away which seems to lose about 1 second of mining time every 2 times it's mined as the 2nd probe is still travelling. There's a more obvious and undebateable way of proving you're wrong. Measure the mining rate of 1 patch, put infinite workers on it and measure over 5 mins say, tell me what value you get. Now measure the rate of 9 workers on 9 patches on a normal spawn like Python. See, the number is less than half the rate suggested by 9 times the maxed out single patch. Therefore it is not possible to max out the minerals with patches times 2 workers.

I said where my numbers are coming from, you don't seem to read my posts properly. Most patches require 3 workers to saturate it. 2 or possibly 3 patches per natural only require 2, therefore it might be possible to max it out with 3 * 7 + 2 * 2 = 25 or 3 * 6 + 3 * 2 = 24 workers. In reality this seems impossible, the AI might be able to do it or someone determined playing at Slowest speed using control groups to set them up.

Patches that are 3 squares away but not in a straight line are further away as units do not move faster on diagonals and it's 1.6 times further (for each diagonal square), plus the AI starts to screw up the path for some of them.

Mid-20s is a terrible number as wander is at its worst. The perceived wisdom is 22 and in my tests this is shown to be a good number because wander becomes much worse after 22.

Now, lets also assume that you can micro 5 workers to cover 2 nearby patches that are not able to be mined by 2 workers/patch. 6 patches, times 5 workers/2 patches = 15


That's quite a clever idea and would be worth trying for the AI people (we really need an AI guy to settle this debate 100% in any case). I don't know if the 5th worker could cover the missed time by the other two probes, would need to know the exact timings. This might be capable of saturating with computer micro, my number is the number of probes that can potentially be stable and maxed if it were possible to get them into the stable state so it might be humanly achievable if there's a clever technique of some kind. I mean once you start them going they require no intervention.
Prev 1 2 3 Next All
Please log in or register to reply.
Live Events Refresh
Next event in 12m
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
ProTech155
mouzStarbuck 59
RotterdaM 45
Tasteless 8
StarCraft: Brood War
Soma 214
Mind 204
Zeus 177
Dewaltoss 98
ggaemo 57
Hm[arnc] 51
Backho 37
Noble 21
Sacsri 20
League of Legends
JimRising 454
Heroes of the Storm
Trikslyr32
Other Games
singsing1264
Happy322
crisheroes188
monkeys_forever113
Organizations
Counter-Strike
PGL13084
Other Games
gamesdonequick654
StarCraft: Brood War
UltimateBattle 23
StarCraft 2
Blizzard YouTube
StarCraft: Brood War
BSLTrovo
[ Show 16 non-featured ]
StarCraft 2
• StrangeGG 117
• LUISG 43
• Adnapsc2 3
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• LaughNgamezSOOP
• Migwel
• sooper7s
StarCraft: Brood War
• iopq 6
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
League of Legends
• Jankos1918
• Stunt444
Upcoming Events
RSL Revival
12m
Clem vs Rogue
Bunny vs Lambo
IntoTheiNu 27
IPSL
6h 12m
Dewalt vs nOmaD
Ret vs Cross
BSL
6h 12m
Artosis vs Sterling
eOnzErG vs TBD
BSL
9h 12m
Bonyth vs Doodle
Dewalt vs TerrOr
Patches Events
12h 57m
GSL
22h 12m
Cure vs herO
SHIN vs Maru
IPSL
1d 6h
Bonyth vs Napoleon
G5 vs JDConan
BSL
1d 9h
OyAji vs JDConan
DragOn vs TBD
Replay Cast
1d 23h
Monday Night Weeklies
2 days
[ Show More ]
Replay Cast
2 days
The PondCast
3 days
GSL
3 days
Replay Cast
4 days
GSL
4 days
Replay Cast
5 days
Sparkling Tuna Cup
6 days
Replay Cast
6 days
Liquipedia Results

Completed

Escore Tournament S2: W7
WardiTV TLMC #16
Nations Cup 2026

Ongoing

BSL Season 22
ASL Season 21
IPSL Spring 2026
KCM Race Survival 2026 Season 2
Acropolis #4
KK 2v2 League Season 1
BSL 22 Non-Korean Championship
SCTL 2026 Spring
RSL Revival: Season 5
2026 GSL S1
Heroes Pulsing #1
Asian Champions League 2026
IEM Atlanta 2026
PGL Astana 2026
BLAST Rivals Spring 2026
IEM Rio 2026
PGL Bucharest 2026
Stake Ranked Episode 1
BLAST Open Spring 2026
ESL Pro League S23 Finals
ESL Pro League S23 Stage 1&2

Upcoming

YSL S3
Escore Tournament S2: W8
CSLAN 4
Kung Fu Cup 2026 Grand Finals
HSC XXIX
uThermal 2v2 2026 Main Event
Maestros of the Game 2
WardiTV Spring 2026
2026 GSL S2
BLAST Bounty Summer Qual
Stake Ranked Episode 3
XSE Pro League 2026
IEM Cologne Major 2026
Stake Ranked Episode 2
CS Asia Championships 2026
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 © 2026 TLnet. All Rights Reserved.