10.05.2005, 07:15:44
PaD;date=May 9 2005, 11:18 AM Wrote:I don't have plans, though ArmorTypes aren't a bad idea.While you're in there you might want to look into fixing an error.
What about Verses? We'd need defaults. Set them to 0%? (not saying I know anything about how armors work, it's just a question).
[right][snapback]1140[/snapback][/right]
If a Versus= percentage early in the list is >0%, and is followed by several 0% values, then the values that follow are considered to also be 0% even if they are not. This happens for secondary weapons, when both the primary and secondary have the same Versus= values, and targeting differences are determined by the projectile (anti-ground & ant-air, for example). I would guess this is happening either simply because the secondary is read differently than primary, or else when the game seems to believe the primary has it covered so why check the secondary any further.
I know that sounds confusing.
For example -
[WarheadUsedByPrimaryAnti-GroundWeapon] ; this one gets used
Verses=100%,100%,100%,0%,0%,0%,0%,0%,0%,100%,0%
[WarheadUsedBySecondaryAnti-AirWeapon] ; this one won't be
Verses=100%,100%,100%,0%,0%,0%,0%,0%,0%,100%,0%
If I shoved a non-zero value in the middle of that, like -
Verses=100%,100%,100%,0%,0%,0%,1%,0%,0%,100%,0%
- then the 2 weapons would get used properly. From my tests it seems to be only 4 0% values in a row are tolerated; 5 0% values in a row will trip things up.
C-GEN: The site with the 'log the f*ck in' forum. And now we make you validate your f*cking e-mail address too.
CannisRules: It's a YR mod.
CannisRules: It's a YR mod.