• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EDT 17:42
CEST 23:42
KST 06:42
  • 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
[ASL22] Ro16 Preview: Rough Waters8[ASL22] Ro24 Preview: Siren's Call8[ASL22] Ro24 Preview: Summer's End9Serral wins HomeStory Cup 2915Serral wins Maestros of the Game 244
Community News
Weekly Cups (Aug 30-Sep 7): herO thrives amid growing schism4Official StarCraft website teases new content ahead of BlizzCon?117Stellar Fest TWO the Moon (Dec 16-20)9Weekly Cups (August 24-30): Patches' balance mod takes over3New 3v3 BGH Ladder (and more) on ShieldBattery!46
StarCraft 2
General
Weekly Cups (Aug 30-Sep 7): herO thrives amid growing schism Nexon wins bid to develop StarCraft IP content, distribute Overwatch mobile game Balance hotfix patch 5.0.16b (July 16) SC4ALL: II Winner Will Earn a Spot at HSC 30! Weekly Cups (August 24-30): Patches' balance mod takes over
Tourneys
Sea Duckling Open (Global, Bronze-Diamond) 2026 GSTL Announcement Sparkling Tuna Cup - Weekly Open Tournament Stellar Fest TWO the Moon (Dec 16-20) IntoTheTV X SOOP SC2 League : Weekly & Monthly
Strategy
[G] Having the right mentality to improve
Custom Maps
Nexus Wars 2021 GUIDE [M] (2) Industrial Park
External Content
Mutation # 542 The Ascended Mutation # 541 Binary Choice The PondCast: SC2 News & Results Mutation # 540 Dodge This
Brood War
General
Official StarCraft website teases new content ahead of BlizzCon? ASL22 General Discussion Pros React To: Calm's Big Brain Play Vs Mini New 3v3 BGH Ladder (and more) on ShieldBattery! BGH Auto Balance -> http://bghmmr.eu/
Tourneys
[ASL22] Ro16 Group B 2v2v2v2 Tournament [ASL22] Ro16 Group A [ASL22] Ro24 Group F
Strategy
Replay Review Process - What do you do? Simple Questions, Simple Answers Odyssey Mineral Stack Saturation Game Theory for Starcraft
Other Games
General Games
Nintendo Switch Thread EVE Corporation Diablo IV [Maplestory Hardcore] Let's Play~!! General RTS Discussion Thread
Dota 2
Official 'what is Dota anymore' discussion
League of Legends
[TL LoL EUW IHs] Teemo shall perish TSM pausing esports and CLG Dead
Heroes of the Storm
Heroes of the Storm 2.0
Hearthstone
Deck construction bug
TL Mafia
TL Mafia Power Rank TL Mafia Community Thread NeO.D_StephenKing vs This Guy From 1 Million Dance
Community
General
US Politics Mega-thread Things Aren’t Peaceful in Palestine Russo-Ukrainian War Thread UK Politics Mega-thread Artificial Intelligence Thread
Fan Clubs
MarineLorD Fan Club The Creator Fan Club The ShoWTimE Fan Club
Media & Entertainment
Movie Discussion! Anime Discussion Thread
Sports
Football (Soccer) Thread TeamLiquid Health and Fitness Initiative For 2023 MLB/Baseball 2023
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread
TL Community
The Automated Ban List Northern Ireland Global Starcraft
Blogs
F* the Children and Get Off …
TrAiDoS
Dreaming of BW patches (mod…
c3rberUs
Regacy Esports: The Bh…
regacyesports
LOCKPICKING NOOB
LUCKY_NOOB
Customize Sidebar...

Website Feedback

Closed Threads



Active: 8463 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
Next event in 2h 18m
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
mouzHeroMarine 327
CosmosSc2 10
StarCraft: Brood War
Britney 10990
Dewaltoss 161
Dota 2
monkeys_forever296
Counter-Strike
minikerr25
Super Smash Bros
C9.Mang0163
Other Games
summit1g8287
Grubby2939
Liquid`RaSZi2454
fl0m819
FrodaN778
shahzam471
ToD223
RotterdaM112
ArmadaUGS51
Chillindude19
Organizations
Other Games
WardiTV40
BasetradeTV29
[ Show 14 non-featured ]
StarCraft 2
• musti20045 15
• RyuSc2 3
• intothetv
• AfreecaTV YouTube
• Kozan
• IndyKCrew
• Migwel
StarCraft: Brood War
• Azhi_Dahaki45
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
Dota 2
• masondota21972
League of Legends
• TFBlade772
Other Games
• Shiphtur243
Upcoming Events
PiGosaur Cup
2h 18m
Kung Fu Cup
13h 18m
Replay Cast
1d 2h
The PondCast
1d 12h
KCM Race Survival
1d 12h
Escore
2 days
IntoTheTV X SOOP
2 days
CranKy Ducklings
3 days
Sparkling Tuna Cup
4 days
Shopify Rebellion Sundays
4 days
Spirit vs Mixu
Clem vs TBD
[ Show More ]
RSL Revival
4 days
BlizzCon
4 days
Replay Cast
5 days
Afreeca Starleague
5 days
WardiTV Weekly
5 days
Afreeca Starleague
6 days
GSL
6 days
Liquipedia Results

Completed

Proleague 2026-09-02
PiG Sty Festival 8.0
Big Dog Cup 2026 Div 1

Ongoing

KCM Race Survival 2026 Season 3
K-JUNGMAN
ASL Season 22
Super Anchor Qualifying S3
CSL 2026 AUTUMN (S22)
Acropolis #5
Acropolis #5 - TRS
RSL Revival: Season 6
Calamity Invitational
FISSURE Playground #3
BLAST Open Fall 2026
Esports World Cup 2026
BLAST Bounty Summer 2026
BLAST Bounty Summer Qual
Stake Ranked Episode 3
XSE Pro League 2026

Upcoming

Escore Tournament S3: King of Kings
Acropolis #5 - GSA
Blizzard Classic Cup 2026
Acropolis #5 - GSB
Acropolis #5 - GSC
SC4ALL II: Brood War
HSC XXX
Stellar Fest 2: Lunar Cup
SC4ALL II: StarCraft II
Kung Fu Cup 2026 Grand Finals
RSL Offline Finals
Blizzard Classic Cup 2026
Stake Ranked Episode 6
BLAST Rivals Fall 2026
IEM Beijing 2026
Stake Ranked Episode 5
PGL Masters Bucharest 2026
1win Private Club #2
Thunderpick World Champ. '26
ESL Pro League Season 24
Stake Ranked Episode 4
1win Private Club #1
Logitech G Play Connect 2026
SL StarSeries Fall 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.