missileguidance - fix MCLOS direction error

[TheCandianVendingMachine]

When merged this pull request will:

• Fix MCLOS direction error

The controls were named wrong. The comments changed show that left was always bound to right, and vice versa.

Strictly speaking, not tested in game. But this is realistically the only path which this got changed so it should work - hopefully.

IMPORTANT

• If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
• Development Guidelines are read, understood and applied.
• Title of this PR uses our standard template Component - Add|Fix|Improve|Change|Make|Remove {changes}.

[PabstMirror]

Suggested change

	["ACE3 Weapons", QGVAR(mclosLeft), LLSTRING(mclosLeft), {
	["ACE3 Weapons", QGVAR(mclos_Left), LLSTRING(mclosLeft), {

this is clunky but i think nessacary

the first time a keybind is added, the default binding gets added to the user profile and will stay that way
even if the default bind changes

so the only way to fix is to change the naming-key
otherwise everyone who played with have backward keys

[TheCandianVendingMachine]

well thats not ideal. since people are already saying how they rebound the controls to other keys, wouldn't this split their control scheme? I think that reversing direction is going to be more wanted than just losing control completely

[PabstMirror]

probably best to just rename all 4

[TheCandianVendingMachine]

is there any way to add a keybind but not have it be rebindable? I would rather keep these bad names and have them mapped as expected, but then add the correct ones as well

[PabstMirror]

sorry, just though of this now
should we make a unified missileguidance_adjustLeft key
and use the same key for both mclos and spike?

all we have to do right now is change the name
and can handle the code change in spike pr

[TheCandianVendingMachine]

I'm keeping the strings the way they are right now, they can be changed in the Spike PR