3 replies to this topic

[No_One]

I just started playing around with macros, and was wondering if you guys could help me figure what the limits were. Is everything with a autohotkey program allowed? I'm not looking to get suspended/banned, and knowing the limit would be nice so I don't mess up.

This is assuming UAC, TAG, and other current macros are legal, and :
http://mwomercs.com/...wo-game-client/

Spoiler

----------------------------------
Q: My mouse/keyboard came with macro software that lets me emulate a series of clicks or helps me with some process. Is this allowed?

A: Yes, using macros as provided by 3rd party hardware vendors is allowed. Though the use of any modifications to assist with aiming, aimbots, wall hacks, or any attempt to give information or tactical assistance that other players would not have by default, is a serious violation of our Terms of Use and any account found to be using such software will likely be suspended or banned.
-------------------------------

First, I made a macro:

Spoiler

-------------------------------
It modifies Left Shift and the Mouse Buttons. Right and Left mouse buttons are weapon groups 1 and 2, Left Shift+Mouse buttons are 3 and 4, and side mouse button+mouse buttons are 5 and 6. Also, I have Left Shift tied to Zoom 2x and Armlock, and the side mouse button tied to Armlock. I put multiple functions on the same button, namely left shift and the mouse buttons, is that ok? 90% sure it's fine, but I'd like a quick confirm before I make a thread about it.
-------------------------------

Scary things I can do:

Spoiler

I had a bunch of stuff here, but i realized I was probably breaking mechwarrior. I didn't want to give people ideas so i took this out.
-------------------------------

And I have more ideas, but these are the ones that are questionable to me. I think my main hangups are controlling the mouse and automating the movement of legs, but that's why I made this post.

Are there any limits, or can I just go nuts?

(If this isn't in the right place, where do I put macro stuff? It's spread all over the place.)

Edit:Third Spoiler

Edited by Schtimpy, 28 March 2016 - 09:47 AM.

[evilC]

I have written the following macros, and have been reported a number of times for some of them, and PGI has never taken any action or removed my threads.

Fire Control: Rapid fire (eg for chain AC2s), TAG toggle, Jump jet spam

MWOZoom: Enhances mouse wheel zoom support (Fixes issue when you roll the wheel too quickly, allows you to exclude the middle zoom level)

RollMouse: Allows your mouse to emulate a trackball. Move the mouse quickly in a direction and pick it up off the desk while in motion to cause the view to keep moving in that direction until you put the mouse down (Basically what a steam controller can do). Great for allowing you to play with low mouse sensitivity, but not have to keep re-positioning your mouse when making large torso twists.

If you want to send mouse movement (not buttons) to MWO, you cannot use AHK's mousemove, you must use the mouse_event Windows API call.

All MWO AHK scripts that interact with keys or buttons should have the following at the start, else MWO may not recognize the keypress:
SetKeyDelay, 0, 50

[Mystere]

It does not hurt to directly ask PGI support. Doing so also covers your bases in case someone does complain (i.e. "Well, I did ask you guys whether or not it was ok to do so!").

I myself don't use AHK. But I can think of a lot of possibilities using Thrustmaster's TARGET and Logitech's G13 tools.

[S 0 L E N Y A]

Macros are fine.
Been covered to death