AI War Beta 5.050 Botnet Escape

[Eternaly_Lost]

I have to say, after moving and starting my new job, this is a nice patch to see after I finally got my internet up at my place.

Now to go give it a try, there been about 5 patches from the last time I played, so I think I just go with a nice new game and see how well 3x exo waves goes against Fallen Spire Fleets.

[Coppermantis]

Are my existing games with Botnet golems (I have one with a broken golem that I plan to capture and another with an activated one) affected?

[Wingflier]

I suggest you read the bottom of the second page

[keith.lamothe]

I should have had this in the release notes to begin with, but I just edited it in: *** Note: none of this affects the old saves except the change in base energy from 40k to 80k (and potentially the Moderate numbers for the Botnet will automatically go up, not sure).

[TechSY730]

Quick release notes thing:

Fixed several issues where units with "infinite engine health" were not being handled consistently.

    For example, a neinzul enclave starship had an internal engine health value high enough to be listed as "infinite" but not high enough to actually refuse to set engine damage to a value > 0. This could lead to protracted (and expensive, in previous versions) periods of trying to repair engine damage.
    Thanks to bongotron2000 and Minotaar for the reports and saves leading to this discovery.

Was that supposed to be "refuse to set engine damage to a value < 0"?

Also, since for some reason the release notes pages are not locked to mods or admins and above only, can I edit small little typos such as these?

[keith.lamothe]

Was that supposed to be "refuse to set engine damage to a value < 0"?

No, engine damage is supposed to stay at exactly zero for infinite engine health units.  And engine damage never goes negative, so practically speaking it refuses to set engine damage to a value greater than zero.

Also, since for some reason the release notes pages are not locked to mods or admins and above only, can I edit small little typos such as these?

Edit rights to that whole wiki are by invitation-only, and we assume that anyone thus invited will practice restraint (or, failing that, not want to see Hybrids when they dream)   Once or twice someone's fixed a typo in the release date of a patch or whatever.  In general please just tell us the error and we'll fix it ourselves, because it's possible the error was cleverly correct

[TechSY730]

Was that supposed to be "refuse to set engine damage to a value < 0"?

No, engine damage is supposed to stay at exactly zero for infinite engine health units.  And engine damage never goes negative, so practically speaking it refuses to set engine damage to a value greater than zero.

Ah, I see.

Also, since for some reason the release notes pages are not locked to mods or admins and above only, can I edit small little typos such as these?

Edit rights to that whole wiki are by invitation-only, and we assume that anyone thus invited will practice restraint (or, failing that, not want to see Hybrids when they dream)   Once or twice someone's fixed a typo in the release date of a patch or whatever.  In general please just tell us the error and we'll fix it ourselves, because it's possible the error was cleverly correct

Like in this case.

[Minotaar]

Fixed several issues where units with "infinite engine health" were not being handled consistently.
For example, a neinzul enclave starship had an internal engine health value high enough to be listed as "infinite" but not high enough to actually refuse to set engine damage to a value > 0. This could lead to protracted (and expensive, in previous versions) periods of trying to repair engine damage.
Thanks to bongotron2000 and Minotaar for the reports and saves leading to this discovery.

Great, now where can I get a refund? 

[keith.lamothe]

Great, now where can I get a refund? 

The Vogon Customer Complaints Department will be happy to take up the issue with you   Mr. Hale is currently out of the office, however.

[Wanderer]

Great, now where can I get a refund? 

The Vogon Customer Complaints Department will be happy to take up the issue with you   Mr. Hale is currently out of the office, however.

*beep*beep* We're sorry, but sector Double Z Plural is no longer in existance.  Please dial in again from another sector that is recogonized.  *beep*beep* We're sorry, but sector...

... *beep*beep* While you wait, please allow us to offer you some poetry to wile away your time... *beep*beep*

[keith.lamothe]

New one

[Draco18s]

Edit rights to that whole wiki are by invitation-only, and we assume that anyone thus invited will practice restraint (or, failing that, not want to see Hybrids when they dream)   Once or twice someone's fixed a typo in the release date of a patch or whatever.  In general please just tell us the error and we'll fix it ourselves, because it's possible the error was cleverly correct

I've fixed several, generally long after a patch has been released.  Did about five a week ago.

While such fixes are likely to go unnoticed, they make me feel good (as I tend to read the updates once every few months and have several to catch up on, so I'm probably not the only one).

Think I've fixed one math related error once, but it would have been a long time ago.

(Oh, and just so everyone's clear, I was invited after having started over a dozen threads and mantis entries related to very minor wiki typos; the "teh" and "n" kind.  And it's about all I use my edit powers for.)

[keith.lamothe]

I've fixed several, generally long after a patch has been released.  Did about five a week ago.

While such fixes are likely to go unnoticed, they make me feel good (as I tend to read the updates once every few months and have several to catch up on, so I'm probably not the only one).

Yea, thanks   If you're really sure it's just a typo or whatever, go ahead, we appreciate that we don't have to catch and/or fix every one of our little mistakes while we sprint through whatever it is (for better or worse).

Think I've fixed one math related error once, but it would have been a long time ago.

Hopefully it was a math error in the release notes and not in the actual change made to the game

[Draco18s]

Think I've fixed one math related error once, but it would have been a long time ago.

Hopefully it was a math error in the release notes and not in the actual change made to the game

I think that one I verified first.  It was a long time ago.  Looking at my contributions I don't see it off-hand so I could be mis-remembering.