I've used Autohotkey in other situations for macro'ing up complicated command batches or command timings that would otherwise be possible for me but kill my fingers/hands, for other games. I'm curious how people would feel about an internal alias/macro system for MWO; accessible through the options section with an imported plaintext config file in your game directory that would give you option of not only toggling weapon states on and off at the press of a button, but having those commands respond to overheating events, component destruction events, ammunition count -- switch ammo bins to load balance perhaps? I don't know. I feel like there could be a lot of room here for our battlemechs computers to function in some small degree as computers, without actually taking the human pilot out of the loops in any way. I, personally, would like to see complicated mech loadouts be more straightforward to play from a button-pressing standpoint, once a player has the knowledge and instincts for the actual playstyle of versatile multi-range setups. As opposed to having to hold down tag or bind it to everything, while manually emulating a 2-weapon-at-a-time chain fire feature, etc.
Some ideas -
Adjustable chain fire delays
Number of weapons (and possibly number of weapons of each type of weapon) to be fired per chainfire
Weapongroup fire state toggle on/off
Being able to select, or describe how ammunition is to be drawn.
Command for emergency / early halt of laser discharge
Command to select an arbitrary location under reticle and lock that location / relay that location to friendlies for indirect fire of LRM / artillery.
Edit: Ability for an ingame commander to add a target to a list of lance/company objectives, and a command for any to cycle through commander designated targets.
Meh, just some random thoughts. Does the current scope of options available to pilots feel complete?
Edited by Doomerang, 15 June 2015 - 11:51 AM.
0
