Current games in 3D are mostly C++ with some assembly code where needed.

For learning, I recommend straight C++ and direct x (or something else that does a lot already for you). I know people have done some cool things with M.U.G.E.N, there might be enough resources and support in that movement to allow someone to hack it into what they need.

The big thing most people underestimate is what is needed to do the actual control/character fighting moves & collision & reaction management. The best way to map out what you will need (just at the basic level- your core gameplay engine requirements) is to ask yourself a series of questions on what a few moves will need & walk through (on paper) how you would implement them.

Example (in order from start to finish):

Q: What systems are involved in making a simple standing jab work in a 2D fighter?

A1: Be in a 'ready' standing state -> State awareness (manager)

A2: Input for button with instant response -> Input at 60fps polling ->A2Q extended: What about coming out of a reaction and pressing a few frames early? A: Need to have some buffering for this to be more friendly -> Polling system with backcheck buffering and command list sort going back x seconds. Note: Critical for 'get up' special attacks!

A3: Animation, about 6 to 8 frames ->Animation system with ability to play few frames recycled over longer time, also at 60fps (even though animation is traditionally at 30fps)

A4: Collision to other character with reaction -> collision system with ability to flag what the reaction should be. A4Q extended: How do draw and place these and where is the best place to manage the collision reactions, is it done with bit flag? etc. A: Need a tool to do the collision assignment/sizing and reaction assignment by name or general level -> Sprite import system, Collision box drawing/export to sprite reference system, collision manager database system, etc.

A5: Character needs to be locked into this move until it is done -> Committed move flag , flag system integrated with State system (for easy management of when things can/cannot be done)

A6: If hits, the character needs to be able to combo to another move -> combo system (insert your favorite stuff here, chain, 2-in-1, whiff chain, etc) with x requirements.

ETC.

That is just a jab, the thing that is the hardest to make feel & look right in 2D or 3D fighting or action fighting games. I also skipped about 10+ other things like:

• Push back
• Block reaction time for victim vs hit reaction
• Hit sparks
• Collision types needed on jabbing arm (Attack, Defense)
• Input windows for the combos
• FX on the jab (motion blur, dust from feet)
• etc