MQ2Melee Functionality - /melee range=?

[Aberham]

This is starting to infuriate me. I will admit, I am not an expert at how this plugin works, but I've read the Wiki and tried to fix this several times.

If I have my bow equipped and I target an NPC it'll instantly shoot an arrow. I've tried doing /melee range=0, which it says will turn it off, but it doesn't. I've also tried different values to see if I can just screw around with it. I even set /melee bow=###### to an item that isn't a bow to try and circumvent the issue, but to no avail.

Anyone here able to help me out? I'm actually using something copied from the Wiki at the moment:

[MQ2Melee]
version=4.513
aggro=1
disarm=1
enrage=1
forage=1
kick=1
melee=15
range=250
plugin=1
facing=1
stickdelay=0
stickrange=50

Thank you for your time


EDIT:

From the Wiki, "range=[0-250]
Enables ranged attacks when target is at or beyond this range. Note that 0 disables ranged attacks completely. "

 

[tagger]

after you type in /melee range=o then type /melee save which i found a must anytime you make adjustments in order forthem to do what they are supposed to do .

 

[ac1dgenocide]

if this macro is assisting someone then try typing /assist off

 

[Aberham]

No fixes yet. I've got the range set to 0, but she's still shooting arrows =\

EDIT: Here's the new .ini I have

[MQ2Melee]
version=4.513
aggro=1
disarm=0
enrage=1
forage=0
kick=1
melee=15
range=0
plugin=1
facing=1
stickdelay=0
stickrange=50
assist=0

Also have a problem with target switching. I'd like for it to not to stop attack when the target is switched.

 

[Aberham]

Hmm. I noticed something...

I have my "Target Nearest NPC" set to "X". If I target something with X, or hit X while something is targetted, it fires an arrow... however, only when this plugin is working. If I target an NPC with the mouse, it doesn't fire. Any idea? Is it hardcoded to fire arrows with the use of "X"?

 

[Aberham]

Alright. I set the "Target Nearest NPC" to a different key and it wont fire when I target, so it is hardcoded to fire an arrow with X. Anyone know how to change/fix this?

EDIT: It seems as if the functions "/killthis" and "/throwit" are set to Z and X respectively. I need to get this changed :|

 

[fatal!]

It's at the top of the code.

//=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//
// Projet: MQ2Melee.cpp     |
// Author: s0rCieR          |
//=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//
// SHOW_ABILITY:    0=0ff, 1=Display every ability that plugin use.
// SHOW_ATTACKING:  0=0ff, 1=Display Attacking Target
// SHOW_ENRAGING:   0=0ff, 1=Display Enrage/Infuriate
// SHOW_FEIGN:      0=0ff, 1=Display Fallen Detected
// SHOW_OVERRIDE:   0=0ff, 1=Display Override Warning
// SHOW_STICKING:   0=0ff, 1=Display Stick Arguments
// SHOW_SWITCHING:  0=0ff, 1=Display Switch Melee/Range
//=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//

#define   PLUGIN_NAME  "MQ2Melee"   // Plugin Name
#define   PLUGIN_DATE   20061027    // Plugin Date
#define   PLUGIN_VERS      4.482    // Plugin Version
#define   NPC_TYPE        0x000A    // NPC TYPE

#define		MELEE_KEY					  "a"		// Plugin Melee Key (Not same as eq please)
#define		RANGE_KEY					  "z"   // Plugin Range Key

Obviously the change has to be made before the code is compiled.

 

[Roguish]

Have you tried MQ2Combat?

 

[LemurGuy]

I also have a quick question about MQ2melee, when I'm tanking, how do I stop from doing the "/stick behind" and just stay fronted?

 

[fatal!]

Stick is a moveutils command. From the wiki:

/stick

* /stick [on|off]

Turn stick on and off. The default for /stick is to stick at max melee range.

* /stick [hold]

Sticks to current target even if you lose/change target

* /stick [<dist>]

Stick at <dist> units to your target

* /stick [-<dist>]

Subtract the dist used from the current stick distance (ie. it will put you <dist> units closer to your target)

* /stick [<pct>%]

Stick at <pct> of max melee range from target. Eg. if max melee range is 20, then /stick 50% will stick you at 10 range

* /stick [behind]

Sticks you behind your target.
Note: Be careful with this option if you do not have the Health of Target's Target Leadership Ability. If you have HoTT active and you are the Target of your Target, then you will not try to get behind. However if you do not have this ability and you gain aggro, you will spin around very quickly as you try and get behind your target while it continues to face you.

* /stick [behindonce]

Get behind the target once then convert to a regular stick

* /stick [pin]

Sticks you to the side of the target, same considerations as /stick behind apply

* /stick [!front]

Sticks you anywhere but in front of the target, will only reposition you if you would be in front. Same considerations apply to this as the "behind" and "pin" options

* /stick [moveback]

Moveback will back your toon up to the current <dist> value, keeping you at a consistant distance from your target

* /stick [loose]

Uses a time delay so adjustments to your position do not occur as frequently, simulating a more human-like control

* /stick [uw]

This changes the facing of your toon, and is very useful under water, where you will try and follow the Z coordinate of the spawn you are facing

* /stick [id <spawn>]

Allows you to stick to a specific spawn ID

* /stick [mpause]

By enabling mpause, manually moving your toon will not break stick and will rather put it on hold. When you are done manually moving, the /stick command will once again kick in and you will continue following the same target as before

* /stick [pause|unpause]

Pause and unpause the stick command

* /stick [save|load]

Some settings are stored in the INI file. This allows you to save your current preferences to the INI file, or load the saved preferences this file

* /stick [mindelay <time in ms>]

When used with /stick this delay is used when mpause is enabled to decide the smallest value to use to resume the /stick command after a manual move

* /stick [maxdelay <time in ms>]

When used with /stick this delay is used when mpause is enabled to decide the largest value to use to resume the /stick command after a manual move

 

[Learningcurve]

I also have a quick question about MQ2melee, when I'm tanking, how do I stop from doing the "/stick behind" and just stay fronted?

/melee aggro=on



/melee aggro=off assumes your monk or rogue not tank type and all hits from the back are more likely to score withj any class

 

[fatal!]

damn it all. He is correct. I missed the tanking part when i read it.

 

[EvenLessSpam]

The newer versions of MQ2Melee seems very buggy to me

First of all, it starts auto-attacking whichever target I have after a short while targeted, this is with regular mouse target. I've tried using the /killthis command to commence attacks (which is basically what the custom bound keys calls) instead of auto attack (Q), that doesn't make a difference

Also the new re-stick feature where it sticks back on your previous target is rather annoying. Often I move a tad to each side if I want to break stick for whatever reason I might have, and then just re-attack (which re-sticks too) when done being in free-mode

And as someone else mentioned, the entire "stop attack on target change" is annoying too, should be an option which can be enabled/disable. This was however something I could live with in the earlier version, the other 2 issues made me unload the plugin after yelling at it (I don't yell unless I'm really really really annoyed).

 

[fatal!]

The attacking when you switch target is because of the mapping of attack keys in mq2melee. If you use A as the ingame attack key, and mq2melee uses A as its attack key, when you hit A you are telling EQ to turn attack on/off and at the same time telling mq2melee to turn attack on /off. You are basically getting in a fight between eq and mq2melee. Easiest fix is to change the default keys in the .cpp and recompile OR switch the attack keys in the EQ options.

I'm not sure what you mean by restick? Are you saying that when engaged on a mob, you respoition yourself, breaking stick, and then a couple seconds later it resticks?

I have noticed that myself. Not sure if I like it or not.

 

[s0rcier]

This is starting to infuriate me. I will admit, I am not an expert at how this plugin works, but I've read the Wiki and tried to fix this several times.

If I have my bow equipped and I target an NPC it'll instantly shoot an arrow. I've tried doing /melee range=0, which it says will turn it off, but it doesn't. I've also tried different values to see if I can just screw around with it. I even set /melee bow=###### to an item that isn't a bow to try and circumvent the issue, but to no avail.

You prolly have an eq key already bind to the x key (default key to tell mq2melee to perform a range attack right now what ever range= setting set to) usefull for pulling. If you have read mq2 vip forum thread you should know about those change and also know that the mq2melee's hotkeys are settable via an ini files likes:

mq2melee.ini

[Generals]
SpawnType=0 + all selected type [+1 PC] [+2 NPC] [+4 PC PET] [+8 NPC PET] [+16 PC CORPSE] [+32 NPC CORPSE]
MeleeKeys=Melee Attack Key (not same as eq please)
RangeKeys=Range Attack Key

[Settings]
SpawnType=10
MeleeKeys=a
RangeKeys=x

if this macro is assisting someone then try typing /assist off

1st) this is a plugin not a macro, 2nd) their is no /assist perform in here!

It's at the top of the code.

//=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//
// Projet: MQ2Melee.cpp |
// Author: s0rCieR |
//=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//
// SHOW_ABILITY: 0=0ff, 1=Display every ability that plugin use.
// SHOW_ATTACKING: 0=0ff, 1=Display Attacking Target
// SHOW_ENRAGING: 0=0ff, 1=Display Enrage/Infuriate
// SHOW_FEIGN: 0=0ff, 1=Display Fallen Detected
// SHOW_OVERRIDE: 0=0ff, 1=Display Override Warning
// SHOW_STICKING: 0=0ff, 1=Display Stick Arguments
// SHOW_SWITCHING: 0=0ff, 1=Display Switch Melee/Range
//=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//

#define PLUGIN_NAME "MQ2Melee" // Plugin Name
#define PLUGIN_DATE 20061027 // Plugin Date
#define PLUGIN_VERS 4.482 // Plugin Version
#define NPC_TYPE 0x000A // NPC TYPE

#define MELEE_KEY "a" // Plugin Melee Key (Not same as eq please)
#define RANGE_KEY

Well editing those will just change built-in defaults, editing ini like i post above is still the best solutions cause you wont need to redo each time you download a new version of mq2melee.

also have a quick question about MQ2melee, when I'm tanking, how do I stop from doing the "/stick behind" and just stay fronted?

Well stick is a mq2moveutils command, i dont like way it's working, i dont like some of it's functionnality but im stuck with it till someone write up something working better.

Your issue look like issue i have in mq2melee 3.x and their always been an alternative to tell mq2melee to not to use built-in stick behavior and instead use your own custom stick command lines. Im guessing you never took 5 mins to check out mq2melee wiki pages cause their is a lot of examples on how to fix / avoid this and that you didnt take times to read mq2melee vip thread on mq2 websites cause again lots of people posted their own custom stick command lines.

You could always search forum thread looking for keywords stickcmd or stickmode. stickmode=1 tell mq2melee to use stickcmd from ini instead of built in stick command line, and this is an example of a stickcmd but you could customize it way you wished...

stickmode=1
stickcmd=13 ${If[!${Me.GroupSize} || ${Melee.AggroMode},moveback, ${If[${Melee.BackStabbing},behind,!front]}]} ${If[${Me.Underwater} || ${Me.Levitating},uw,]}

The newer versions of MQ2Melee seems very buggy to me

First of all, it starts auto-attacking whichever target I have after a short while targeted, this is with regular mouse target. I've tried using the /killthis command to commence attacks (which is basically what the custom bound keys calls) instead of auto attack (Q), that doesn't make a difference

Also the new re-stick feature where it sticks back on your previous target is rather annoying. Often I move a tad to each side if I want to break stick for whatever reason I might have, and then just re-attack (which re-sticks too) when done being in free-mode

And as someone else mentioned, the entire "stop attack on target change" is annoying too, should be an option which can be enabled/disable. This was however something I could live with in the earlier version, the other 2 issues made me unload the plugin after yelling at it (I don't yell unless I'm really really really annoyed).

Well im really sorry to heard all about this, like someone post their was a war between eq and plugins with control of attack, sometimes on win and plugins react or someone times eq wins and plugin doesnt like it, solution for me was to create a unique key to control on/off engage on current target.

randoming chaning target, macros that turn on/off attack or hotkeys that use /assist might cause mq2melee to react weird and auto-attack a target you dont want, or report an override actions that you dont want also, i tried to do my best to filter them out but im stuck with in.

you could try to setup a hotkey that does "/melee reset" this will tell mq2melee to reset all his internal variable including current killing target etc, so it might help ya or not but it's always a good panic button if you need to turn off killing on a specific target.

Re-sticking built-in is triggered each times you evade combat, ie: turn off attack when low hps, stand up after a failed fd, or turn back attack on after an escape, each time sticking flags is reset and stick is normally re-issued. Latest version of mq2melee will detect if you have aa that enables to backstab from front and should not force "behind" exclusive mode. You could always override built-in behaviour playing with "stickcmd and sticmode" settings.

And im not sure how you manage to get so much "stop attack on target change" im raiding all night long with a rogue, playing a warrior and a beast macros and i wont get this messages only once a week or so, so guess that is somethign else, a custom macro or something that play with assist, attack on/off or range attack, wish i could be behind your keyboard one night and point out what you might do wrong for the plugin to react like that it must be really annoying for ya.

The attacking when you switch target is because of the mapping of attack keys in mq2melee. If you use A as the ingame attack key, and mq2melee uses A as its attack key, when you hit A you are telling EQ to turn attack on/off and at the same time telling mq2melee to turn attack on /off. You are basically getting in a fight between eq and mq2melee. Easiest fix is to change the default keys in the .cpp and recompile OR switch the attack keys in the EQ options.

Thanks bro for trying to help out peoples, i didnt check redguides for a while and school is keeping me real busy. Im surprise to heard about so many problems.

I keep receiving emails and testimony from different mq2melee users reporting that version 4.4482+ are the more stable and functional version arounds. Iam really surprise to see all those problems coming back to surface, might it be possible that yourguys didnt try latest version and are reporing old issue? Or all people that tell me that latest builds are the most more functional one are on some heavy drugs?

Well honestly guys you are just making me consider to retire. MQ2Melee is a huge project, over 1200 hours of hard works, supports and developments. Im no longer sure i should invest time to add Burried Sea expension goodies to mq2melee.

 

[PeteyPablo]

The latest stuff has been working great Sorcier. Definitely appreciate the work!

 

[Learningcurve]

This is starting to infuriate me. I will admit, I am not an expert at how this plugin works, but I've read the Wiki and tried to fix this several times.

If I have my bow equipped and I target an NPC it'll instantly shoot an arrow. I've tried doing /melee range=0, which it says will turn it off, but it doesn't. I've also tried different values to see if I can just screw around with it. I even set /melee bow=###### to an item that isn't a bow to try and circumvent the issue, but to no avail.

Anyone here able to help me out? I'm actually using something copied from the Wiki at the moment:

[MQ2Melee]
version=4.513
aggro=1
disarm=1
enrage=1
forage=1
kick=1
melee=15
range=250
plugin=1
facing=1
stickdelay=0
stickrange=50

Thank you for your time


EDIT:

From the Wiki, "range=[0-250]
Enables ranged attacks when target is at or beyond this range. Note that 0 disables ranged attacks completely. "

Dunno if it was answered yet but try /melee melee=150

This will say anything you target within 150 is melee trash and should go after it.

Of course if your attack is not on you will just sit there