Numpad 0 is mapped to vehicle secondary fire by default

[bad_nade]

Description:
On BF2's default control mappings numpad 0 is mapped to vehicle secondary fire. So after installing the game or resetting the conrols, Mumble's squad channel conflicts with vehicle secondary fire, which leads to accidental bomb car explosions or unintended release of ammo boxes when talking on the squad channel.

Steps to Reproduce:
Start PR, go to BF2's options > control and press reset. Or make a fresh install of the game like many players have to do time to time. Go to vehicle controls tab and notice how numpad 0 is mapped to secondary fire.

Expected behaviour:
PR Launcher should make sure that there is no this kind of conflicts either using BF2's VOIP keys for Mumble by default or deleting other numpad 0 entries from control mappings.

Tested on:
Version: 1.1.1.0

[JTtheOKIE]

I remember the first time I played in a armor squad(I almost always play INF), was firing rockets all over the place. My SL kept yelling me to stop firing, and of course I kept replying "What?!?!". I didn't even realize I was firing. Funny little mishap.

[Meerkat]

This happened to me yesterday when I was driving a logistics truck. Middle way to marker I spoke squad chat and then I accidentally drop both crates and I didn't even notice that because truck's noise is very loud.
So, when I reached the marker and squadleader wants me to drop both crates to build stuff and .. well .. you can imagine the rest