Spring RTS Engine

heyya, [Leo] has engulfed itself in building XTA CE.

anyway just editing the weapon files.

and accuracy tag has been added to alot of weapons where it wasnt present before... is accuracy a required field in the new spring?

also is there a wikipage or infopage about the weapon.tdf files?
i have searched but come up trumps...

alternatively...
is accuracy expressed as an interger, or percentage?
and higher values indecate more accuracy?
what does it default to?
and
(if its not %) what would emphisise 100% accuracy?

TODO list.
organise wiki.

thanks alot
D.R

Go here:
http://spring.clan-sy.com/wiki/Weapon_Variables

that's, um, outdated. somebody willing to bring that up to date? sources:

http://spring.clan-sy.com/fisheye/brows ... r.h?r=4271
http://spring.clan-sy.com/fisheye/brows ... cpp?r=4316 (concentrate on ParseTAWeapon method.)

Accuracy is a degree value in terms of 0-65535. It will spray the shell(s) randomly in a cone as defined by this value. Multiply the value in degrees you want by 182 to get the value accuracy uses.

For 100% accuracy (discounting things like gravity, target movement, etc--physical variables) remove the accuracy tag.

Gnome wrote:Accuracy is a degree value in terms of 0-65535. It will spray the shell(s) randomly in a cone as defined by this value. Multiply the value in degrees you want by 182 to get the value accuracy uses.

What exactly would a 360 degree "cone" entail? The unit possibly shooting in the exact opposite direction?

Probably, though keep in mind it's random. Think of a shotgun spread (or if you've played Unreal Tournament, the flak cannon) in any FPS game. Raising the accuracy value enlarges the cone, which decreases chances of a perfectly accurate shot. So for a full 360 degree cone with a 5 shell burst, in theory it could fire one in each direction and one straight up, but that'd be an incredibly rare occurance. And I've never tested angles that great, so I'm not entirely sure.

Gnome wrote:For 100% accuracy (discounting things like gravity, target movement, etc--physical variables) remove the accuracy tag.

IIRC the default is 3000, not 0. You have to explicitly set it to 0 for perfect accuracy.

That's tolerance, not accuracy you're thinking of. I think the only thing tolerance does is define the cone in which a turretless weapon will consider the weapon lined up.