Kavanagh wrote:
Nod, you can macro a move between sectors, but you cant macro *past* the move. e.g., to clear a fig in 1234 and avoid an adjacent photon in twgs, I used macro 1234a100^M1^Myy (twarp to fed) or somesuch. Pre twgs, all that macro would do is move you to 1234 and sit there at the attack/retreat/surrender prompt. Similarly, with scripts, you cant script a move to terra, land, grab colos etc without a waitfor " (?=Help) :" after the move to terra, before the land/grab colos etc
Uhm. You can write a script to go to terra, land, and grab without a waitfor. I do it all the time.
If you do m1234a100^M1^Myy ...
You would move to 1234 and sit on the enemy fig, because the move to terra would still
be stuck on the fig. Ie, notice where your ^M is.
If on the other hand you want to kill the fig and twarp off...
m1234^Mza9999^Mm1^Myy
Move, killfig, twarp off. Z-buffer if no fig. Yes, you can still write macros. But you have to be
precise on the macro, and that's probably where the problem is.
Cruncher wrote:
Less hazardous planets = colos that behave like little bunnies!
Depending on the hab rating. Basically it's like this...
The hab rating is multiplied by a base factor and that's the
compound growth rate of the colos. The hazard rating is what
kills them off.
If you have a low haz but high hab rating, they'll grow like
bunnies and never die. If you have a low hab rating, they won't
breed as fast.
Cruncher wrote:
Before TWGS were those levels hard-wired? I knew we used to try to come up with all sorts of goofy stuff to keep them from dying off. Don’t land, keep plenty of org and equip on hand... and finally don’t even look at the planet list for fear of killing more until the death cycle was over.
Yes, it's a gold option in the gold planets editor.
I've ran all the numbers, there is no correlation between landing
and death rate, there is no correlation between eq or org and
death rate. It's a very simple formula.
The only difference is that planets are only updated on certain
events, so while you may not see the change yet... it's just waiting
for you to update the timestamp.