Request - Please provide two more vars to Me TLO

[AmericanNero]

I would very much like to see a couple more pieces of information to help manage character behavior in macros. If this is already there, I would greatly appreciate knowing how to access it.

1) Time elapsed (in microseconds is great) since the last moment the character was moving. This would complement Me.Moving and allow for better movement fine tuning and behavior.
2) Whether the user is typing something / has pressed a key. I envision pressing a key to do something different, like pausing the macro while a person manually fine tunes movement or pulling, or performing some special sub / event.

Thank you,
AN

 

[Sic]

1. this is something you could keep track of in a macro not sure if a tlo for it would make sense?
2. not sure if that's even possible - interesting thought tho

 

[kaen01]

1. you could technically just have variable you set with a timecode whenever me.moving is false, and then when you need to knkow last time you moved just read that var.

2. moveutils, and mq2nav does have options to stop movement if oyu touch keys. so i think it would be possible?

 

[Sic]

2. moveutils, and mq2nav does have options to stop movement if oyu touch keys. so i think it would be possible?

on keypress yeah, but i think AN wants something if someone pressed / and are now in the chat window like they're typing

like blinky cursor line thing in the chat input box

 

[saar]

Me tlo is already too inflated. The first option can for sure be done in a macro/plugin most likely a macro, but I don't see a benefit to it, I mean you can time slice the event of me moving the you time slice the next instance and compare them. As for the second it would have to be a plugin to grab the keypress.

 

[Kasino7]

To relate to number 2.

I often am typing messages to guildmates, DKP team, officer, etc etc during a raid. When I'm tied away, I'll throw KA on so I can still help the raid while doing what I need to do.

One of the biggest peeves I have, is that memming songs or opening spellbook, erases EVERYTHING I've typed.

GRRRRR

 

[kaen01]

there is an option in mq2 to pause any macro you are running while you are in type window, its in the default section of your macroquest.ini

MQPauseOnChat=0

and i think there is a command to turn it on and off.

yes found it.

/mqpause chat [on|off]

 

[Sic]

there is an option in mq2 to pause any macro you are running while you are in type window, its in the default section of your macroquest.ini

MQPauseOnChat=0

and i think there is a command to turn it on and off.

neat so looks like you can already pause while chatting
ah there's an eq address if you are not in chat mode *EQADDR_NOTINCHATMODE
so that definitely could be turned into a tlo member

 

[Kasino7]

there is an option in mq2 to pause any macro you are running while you are in type window, its in the default section of your macroquest.ini

MQPauseOnChat=0

and i think there is a command to turn it on and off.

yes found it.

/mqpause chat [on|off]

Thanks. Anything that will let me type unintruded with macro still running?

 

[Ladon]

I'm amazed at how even after years of use there are still intricacies of MacroQuest to learn. It's usually Kaen teaching those things, too.

 

[AmericanNero]

I guess I could keybind a hotbutton that would /bct myself and trigger an event. Look, I don't want to pause or cease the macro, I want the macro to respond. Big difference that I think people are not understanding. It's just a cluster solution, you know?

 

[saar]

depending on what you want just make a bind that is just a pseudo event.

 

[Lemons]

Input detection would be nice.

While !userInput.Length {
if keypress N varset userInput No
if keypress Y varset userInput Yes
}
As for moving, there's two things you need to consider. Moving and Velocity. You can be moving but your character can be stuck not actually going anywhere.

As others have mentioned, if you want to know the last time you issued a movement command you should take a timestamp each time you issue the command. The most granular time available is EverQuest.Running. Just minus the current time from your stamp to get your number.

 

[AmericanNero]

All these solutions require a hotbutton / keybind through the UI interface.

I think the one that does a /bct ${Me.Name} DOTHIS, would best provide the functionality I seek.

Then the macro could catch the particular event within a loop: /doevents DOTHIS

----

Keypress workaround:
1) User presses a particular hotbutton or keybind.
2) That eq macro does a /bct ${Me.Name} //bindcommand
3) The bindcommand then does a say which the event handler picks up.

Or

Press a hotbutton, etc.
/bct ${Me.Name} DOTHIS
Which triggers the event handler directly.

Or

Press a hotbutton
/mqp
Do something outside of mq
/mqp

Or

User presses a button / keybind that toggles mq
User does something else
User presses a button / keybind that toggles mq

---

 

[AmericanNero]

if you want to know the last time you issued a movement command you should take a timestamp each time you issue the command. The most granular time available is EverQuest.Running. Just minus the current time from your stamp to get your number.

That makes sense. I was unaware of that timestamp. I could wrapper certain movement commands and set an outer.

 

[kaen01]

for your key event thing, you could just use bind for your macro

#bind dothis /dothis

Sub event_dothis
    /echo i am telling macro to do this now
    /varset shouldidoit yes
/return

 

[Knightly]

I put your TLO request here: https://gitlab.com/macroquest/next/mqnext/-/issues/271 . It helps us a lot if people "thumbs up" those kinds of things so we see how much interest there is in specific features.