🚀 go-pugleaf

IN TEH PALECE KNOWEN AS alt.games.starcraft, TEH FAGGORTER
"alvinst...@hotmail.com" <alvinst...@hotmail.com> DUMPED HIS
GHEYE SHIET ON MY COMPUTAR SCREEN!!!!:
>I know this is group is pretty much dead, but I have some Starcraft
>questions that have been bugging me for years including a recent one.
>
>
>1.	Is there a computer crash hack?
>
>This happened to me 3 times over the weekend.  I win on bnet and
>instead of going to the stats screen, my screen goes blank.  I can not
>even do a ctrl-alt-delete.  I have to reboot my pc.  I find hacks
>annoying, but this one crosses the line.
>
There are hacks to make the game crash (go out of synch), but I don't
think they should really affect the rest of your system, at least to
that degree, unless it's already fudged up seriously by some other
(unrelated) means. Or you're running windows 98 or something.

>
>2.	Why is there a long delay before games are listed in bnet?
>
>This one drives me nuts.  I click the list of games, and it is blank
>for 30 - 60 seconds.  Then the list displays.  If I get booted from a
>game, I have to go back to waiting again for the game list to refresh.
>Does this happen to everyone?   It is majorly frustrating when you
>have players dropping, leaving games, lagging out, then you have to
>wait again.  Any way to avoid this problem?
>
That's the way it just is? I dunno.

And if you get booted, people usually wouldn't want you to rejoin that
game, no?
Alternatively, you can just type the game's (exact) name into the game
box and hit enter even if it doesn't show up in the list.

>
>3.	Ok, how the hell am I supposed to select the workers at the
>beginning?
>
>	This totally baffles me.  I am often accused of being a noob within
>the first 5 seconds of the game because of the way I select my workers
>to start mining.  If a pro is on my team, they quit the game simply
>because of my mining technique saying that I don't know how to micro.
>I simply double click one unit to select them all and send them to a
>patch.  What else can you do?  It takes longer to select one
>individually, or hot key all 4 of em.  It is a very stupid
>accusation.  What do they save? Three seconds of build time?
>
People call you a newbie because if you don't know how to the worker
thing, chances are you don't know how to do a whole lot of other stuff
in the game.

Anyway, the basic gist is to first select all 4 workers, send them to
a patch, and then, while they're on the way to that patch, select 3 of
the workers individually in succession and send them to a different
mineral patch each. If you do this right, you'll have all 4 workers
mining different mineral patches by the time they get there. 

If you just send all 4 workers to the same patch, you're letting the
inefficient game AI spread them to mine other mineral patches (but
only once they reach the patch and go "oh crap, someone else is mining
this one already), which loses you some critical seconds in the early
game while waiting for the cash to build your first things.

This is also why you should make sure to send all of your initial
workers to a different, free mineral patch whenever they are built, to
maximize the efficiency. Once you got more workers than patches you
can start to give up on that exercicse and concentrate on other
things.


Small stuff like that adds up easily in the early game, and  yes, if
your pool/rax/Gate builds 10-15 seconds later because of that, it can
be the difference between losing and continuing the game. 

>
>4.	How do you do the tank drop on the ledge thing?
>
>	I just can't pull it off.  I give my drop ship the command to unload,
>and it refuses.
>
If they refuse to unload it's because there's not enough space below
them to unload. If you select to unload just at the edge of the cliff,
try to move in to more center so there's clear ground space to unload
to on all sides of the dropship. Also, if you use several dropships,
give each one of them an unload command of their own to a slightly
different location - Don't just select all of them and hit unload on
the same spot on the ground.


>5.	When launching an attack, what should be targeted?
>
>So you get an army going, and ready to attack.  Now, strategy really
>plays a big part especially if I am doing an early rush.  The strat
>guides will tell you to use the	attack move command and click
>somewhere inside the base.  I usually end up with a failed attack with
>this method.  For example, if the terran has bunkers at his choke, and
>I can just run by them, the attack move would have me wasting mytime
>on the bunkers.  I need to do the most damage in the minimal time
>because in 	a team game, his buddies are on the way.  So which is most
>important for hurting him?
>
The workers, always go for the workers first. But ONLY if you can. No
point in wasting 8 zerglings to kill 1 probe, etc. In fact, in team
games you should  only rush if you can get a partner to go along with
you, otherwise it's just pointless as the chances that you'd do any
damage is minimal.

And likewise, if you rush him with 8 lings and he has like 1 zealot
defending, don't just ignore the guy and go whack at probes - Always
kill whatever army he has there if you can, that is, without it
severly hampering the strength of your own assault. 

Second from workers in priority would be his tech if he has anything,
and lastly his army, but you should never challange that uless you can
emerge as the clear victor. A mutual annihilation only serves to gimp
your own team, as chances are one of his teammates could be
counter-rushing you at that very moment, or coming to his aid and raze
your army, resulting in a loss-loss situation.


Anyway, all your points can be summed up with "You need more units,
get a teammate to go along with your attack". People in team games
always play conservatiely, eg, go for units before tech because of the
obvious rush factor (well, known and well-practiced teammates are
another matter), so if you just rush in alone, you SHOULDN'T do any
major damage. If you do, it means that player sucked and wouldn't have
been much of a threat anyway.


Anyway, it's hard to say one "do this, this is always the correct
thing", because very much of all this is situational. Sometimes you're
better off to go for workers. Sometimes it's better to kill whatever
defences he has (eg morphing sunkens, but you got reinforcements on
route for example). Sometimes it's all the better just to leave him
all alone and save your troops for something more useful.


But, you're playing a team game, so get some damn teamwork going! If
nothing else, tag along someone else's rush if the people on your team
don't talk to each other - Much better than having what would
otherwise constitute pretty much more or less 3 different 1v1 games on
the same map.