🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.games.starcraft
Article #292117

Re: Battlecruiser vs. Carrier

#292117
From: Spyderizer
Date: Thu, 17 May 2007 09:48
18 lines
1571 bytes
Jon wrote:

> So I guess the questions I have are as follows:
> (1)Could a carrier beat a battlecruiser in a one-on-one battle? And
> how?

Possibly... We have tested the theory, I don't recall the result though.

> (2)Could any unit outrun a charging yamato gun? More specifically,
> could a carrier? If so, what is the difference between moving the
> carrier away, and using an ability, such as recall, to transport the
> unit away.


 From what I recall, moving doesn't have any effect once the yamato 
canon starts charging, the game mechanics will guide the shot to its 
target regardless of position. I'm not sure if that's still the case if 
you use  something like recall or the canals.
Technical Details
Message-ID: <f2h88r$7c4$1@lust.ihug.co.nz>
Path: mbox-mo1.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail
References: <1179387227.008384.71360@q75g2000hsh.googlegroups.com>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!g2news1.google.com!news1.google.com!news.glorb.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail
From: Spyderizer <n...@spam.com>
Newsgroups: alt.games.starcraft
Subject: Re: Battlecruiser vs. Carrier
Date: Thu, 17 May 2007 21:48:30 +1200
Organization: Ihug Ltd
Lines: 18
Message-ID: <f2h88r$7c4$1@lust.ihug.co.nz>
References: <1179387227.008384.71360@q75g2000hsh.googlegroups.com>
NNTP-Posting-Host: 203-118-178-45.bliink.ihug.co.nz
Mime-Version: 1.0
X-Trace: lust.ihug.co.nz 1179395164 7556 203.118.178.45 (17 May 2007 09:46:04 GMT)
X-Complaints-To: ab...@ihug.co.nz
NNTP-Posting-Date: Thu, 17 May 2007 09:46:04 +0000 (UTC)
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
In-Reply-To: <1179387227.008384.71360@q75g2000hsh.googlegroups.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit