On the new TWGS servers i have noticed it has become inefficient to try to cap alien ships.

in command center tweditor the ] option is defaulted to 75% meaning 75% of the time even a 1fig attack on empty ship will blow it up, in alot of edits thats no good. like being blue in a subzero if u cant cap alien ships and cant cash like a red it leaves a big advantage to reds who can afford to buy a couple redrums and dump cash to try to cap. Its not a gripe just something i wanted to mention to other sysops if alien ships should be part of the integral edit strategies this should be adjusted

What was the default before?

I'm not sure what you're seeing. The default is "never", or 0%.

in every game i have banged on my server Distinct Tradewars using several .twa's from helix's twa database it has defaulted to 75% fail rate

i also noticed on a few of the recent bangs that alien ships are blowing up even with 0shields and 0 figs.

example on microblaster.net i was attempting to assist a returning player. i left an ascian troller 1 sector outside SD with 0 shields 0 figs he hit it with 1 fig in a corp battleship and it blew up

so i went a step farther and bought a redrum and moved it to the same sector. again 1fig attack ship was destroyed. i pm'd micro and from his response i believe his setting defaulted to the same 75% failure rate that is happening on mine.

also in older twgs versions u could cap alien ships easily once shields are popped 1 fig let them attack till figs gone next wave of 1 its urs

recently 3 out of 4 are blowing up even with 0 shields 0 figs anda 1 fig attack wave

The tedit shows the default is never however importing .twa's that were created prior to the new TWGS it defaults to 75% instead of never. im not saying its a bug im just stating its a setting sysop's should make sure to check.

Yes, it was 75%. I have changed it to 0%/never.

Ah, ok, I see what you're saying now. I'll make sure there isn't a data conversion bug going on there.

I looked at the field and it's new to this version, which means it should have a value of zero. If you can email me the TWA in question I'll look it over and see how this is happening.

The TWA i used after installing the beta was the 1 BIG D posted in the twa archives forum here on classictw. one of the sticky posts.

i also didnt put it in the bug forum because its not a bug. after the initial import if u change the setting it will save it when rebangs are done. as long as sysops know to change/set it initially

If somehow there's a non-zero value in this field after updating its data to the current version, that's a bug that could effect many different settings. I always work under the assumption that a new field will have a zero value.