Recent content by Denethor

Those notes are back from the alpha build of LDoN support. We're well past that. Not sure what'd it be, but I can DM you and we can set up a Zoom meeting to take a look at things. (I haven't played EQ now in several years, but I am still providing support for this macro.)

As I said, ANYTHING on the XTar list triggers the combat handler. Also mentioned in the FAQ. You can set the xTar's back after you finish with the macro.

Sorry, was out of town on business so I haven't been doing my usual checks on this thread. You have someone/something on your Xtar list. So the macro things we have something on aggro and is entering the combat handler subroutine. Clear your XTar so all slots are Auto.

That isn't a bug in the macro. It's an issue with the mesh (E/W Cab is the big stand-out example of this). Use the meshes I provide from my repo (https://github.com/BDeakins/DeneCore-Meshes) instead of the one from the downloader. This is also mentioned in the FAQ for the macro. (You can...

Set all of your extended targets to Auto. You have something hard-set in there and the macro is seeing a target on the list and thinking we have agro. So it is jumping into the combat handler.

Do you have DeneCore installed? Doesn't appear so, or it's not installed correctly. Click THIS to add it to your subscribed macros, repatch MQ so it installs it (it'll put it in the correct location) and try again. Cheers!

This is a known issue caused by using different / unsupported meshes. The mesh requirement is mentioned in the Requirements section of the macro, This exact issue mentioned in the FAQ: It's only the East Cabilis mesh that needs replacement, IIRC, but I'd just replace both. You can always...

Will correct and publish soon. Thanks.

xxraptorxx's issue should be resolved. Waiting for a response to PM from KS1980.

Please try the workaround posted here: If you still have issues, let me know. I may need to forego supporting EQBC and just make Dannet the single comms mechanism for the macro.

Did you write the AA name in there yourself originally?

Is it the rogue or the necro having the issue? Or both? Sorry, but the minimal punctuation and the speech-to-text program you're using (or whatever is effecting your word choice) is confusing. Regardless, to answer your original question: You can't put an AA into the INI for the invis clickie...

The macro doesn't store the AA in the INI. Is scans for it each time the macro starts (Explore.mac, line 619): /varset invisAbility ${Select[TRUE,${Me.AltAbilityReady[Cloak of Shadows]},${Me.AltAbilityReady[Shauri's Sonorous Clouding]},${Me.AltAbilityReady[Group Perfected...

I'll DM you to set up a time to look at this on your system. We'll get it sorted. Sorry for the trouble.

If you are seeing the "Let's Get Dangerous" message, it comes from this section of Sub combathandler: /while (${Me.XTarget}) { |- Did we just get jumped? /if (${Me.XTarget}) { /if (!${haveSaid}) { /message \amLet's get dangerous...