Topic: Probable HET bug

[kevlar]

Don't know if this is a bug...but really looks like such. And i'm sorry to post this both on the bug forum and  the general starfleet command one.

let's say you make your first HET. since it 's the first you make, the chance for success  is 100%. As the player makes the HET, while conducting the mentioned high energy turn, the chance is reduced to lets' say 87%. Until now no problem since you are performing a HET and so the chances for another should decrease...but when you are you completing the same HEt, the chances from 87 are reduced to 67 or 71....what means that the HET chance is reduced  two times in a row, one while the player performs the HET and another when that same HET is finished.

I was getting odd HET failures when, in 1.00,  i normally could make 2 almost consecutive without great problems....and so i started to pay considerable attention to the HET chances, finding  that I was going from 100 % to 67% in the time it took to complet a single HET.

Question: is this a bug or a "miss-feature"?

[kevlar]

Don't know if this is a bug...but really looks like such. And i'm sorry to post this both on the bug forum and  the general starfleet command one.

let's say you make your first HET. since it 's the first you make, the chance for success  is 100%. As the player makes the HET, while conducting the mentioned high energy turn, the chance is reduced to lets' say 87%. Until now no problem since you are performing a HET and so the chances for another should decrease...but when you are you completing the same HEt, the chances from 87 are reduced to 67 or 71....what means that the HET chance is reduced  two times in a row, one while the player performs the HET and another when that same HET is finished.

I was getting odd HET failures when, in 1.00,  i normally could make 2 almost consecutive without great problems....and so i started to pay considerable attention to the HET chances, finding  that I was going from 100 % to 67% in the time it took to complet a single HET.

Question: is this a bug or a "miss-feature"?