Spring RTS Engine

Gota wrote:Making mines is a big investment of time.
Time micro,time to see where you already have them,time to find where your god damn miner is...etc

Well for people who know how to code minelayers arent that big of a deal.

Det just laid out huge square regularly spaced minefields with click-box-drag. This tactic prettymuch on its own is what lead to the juno change.

I've never ever seen a player over rank 5 build a Juno in BA before in a public game.

juno is way to expensive :< it should be like - 'fookers got jammer, i make juno in 20 sec and own bastards'

*Enemy makes one mine*

"OMG THEY HAVE MINES!!!!!!1111ONEONEONE QUICK EVERY SPAM JUNOS!!!"

It doesn't happen like that. Now, admittedly, I eventually stopped playing public BA games, but like Det, I found mines highly effective, and forced various people to build those rather aggravating Juno.

Noize only changes BA based on 1v1 cometcatcher. Mines were a problem in 1v1 cometcatcher (mainly because of how det used them). The fix noize made was for that.

Well, thats a simplification. But really, they are very effective. You just need to recall that you can spam massive square fields of them and that they always make cost when something runs into them.

If mines are effective then juno is effective.

Noobs just dunno how to make mines (and probably undervalue information warfare).

junos actually work well in 1v1 i discovered.


well usually u just need 1 juno.

Well how did you discover this great secret?

By playing 1v1.

neddiedrow wrote:By playing 1v1.

what a clever lad...