10-year old games usually stick (no pun intended) with spritesheets as far as I've seen. I'm not too familiar with vector art but I assume that a basic keyframe system, as seen in 3D models, would do just fine. Basically, you define the positions and orientations of these sticky man parts at certain points in time and interpolate between them for the frames in-between, hence the name key-frame.

basically it's not normal, you could look on the net for a "sprite" set for king of fighters or SFIII, just to use to learn from

I'm doing a scrolling beat-em-up at the moment and trying to figure out the same thing at the moment. Currently I'm going for canned animation sequences (eg. a punch) defined in xml (including hit and vunerable boxes), and linking them together with a state machine in code. The state machine is getting a little hairy
though, so I might make it slightly more generic and move some of the state transition logic into data files so I don't end up with loads of code duplication for near identical attacks.

Personally to make things easier I'd use sprites in-game rather than vectors (although you could still draw with vectors and export to png or whatever).

Quote:Original post by hogarth
basically it's not normal, you could look on the net for a "sprite" set for king of fighters or SFIII, just to use to learn from

Most sprite sheets from commercial games you'll find on the internet are made by fans piecing them together using output from emulators. It's highly unlikely they'll bear any resemblance to what was actually used by the code.