• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
Explore.Mac - An Explorer / Traveler Achievement Macro

Release Explore.Mac - An Explorer / Traveler Achievement Macro 1.3.1

Overview Commands Instructions F.A.Q. Updates (6) Reviews (18) History Discussion Terms and conditions
When I start this my toon goes no where just spams heading to steamfront moutains in Mq window
 
somewhat off topic but can someone link the end item for this ?
 
There's no "end item", it just allows you to evolve the TBL Evolving Boots. Completing the achievement itself doesn't give you anything beyond passive movement speed.
 
I just wondered what the end stats were on the boots once they are fully evolved. Being lazy, will go look it up.
 
surfdog21 said:
I just wondered what the end stats were on the boots once they are fully evolved. Being lazy, will go look it up.
Click to expand...
These items are slightly better than TBL raid gear once evolved by group methods. There is an even higher level if you are able to complete all TBL raid vanquisher adjustments.
 
ok I noticed a few issues with this now if running on a paladin it tries to summon a horse indoors gets stuck no clue on that and now crashing every time I zone
 
Sorry to hear you are having trouble. However, I will point out that a macro cannot / should-not-be-able to cause a 'crash' in EQ. However, I'd like to help you resolve whatever issue you're encountering, if it's within my ability. So, when is the crash occurring? When zoning? Middle of a zone? When pausing or unpausing the macro? Was there a error message or a crash dump? What plugins do you have loaded? (Unnecessary plugins are the most common cause of crashes. Not the macro.)

Most reports of crashing are when zoning. However, crashing on zoning isn't cause by the macro. It's typically caused by plugins. But since my macro zones more often than any macro around pretty much, it 'seems' like the macro causes it. So, I understand your frustration with crashes and why you'd assume it was Explore.mac triggering it. So, let's start figuring out what you have that's causing it. Look in your ../Release/MacroQuest.ini file, and find the [Plugins] section. Copy/paste it here. There's a lot of plugins enabled by default that you probably don't need / aren't using. And some have not been maintained for 8+ years.

Are you using 1.0.3 or 1.1.0 Alpha? And what does your Explore_<server>_<toon>.ini have in the General section?
 
no I have run it on this computer but now crashes every zone I have used this for weeks and no issue all of a sudden It wont work at all
 
Then obviously, it's not the macro. The macro hasn't changed in that time. So, it must be a plugin in MQ2 (since that has been updated) that HAS changed, and therefore is triggering the crashes. Listen, I'm just trying to help you solve your problem.

So, again:
Are you using 1.0.3 or 1.1.0 Alpha of the macro?
And what does your Explore_<server>_<toon>.ini have in the General section?
When is the crash occurring? When zoning? Middle of a zone? When pausing or unpausing the macro?
Was there a error message or a crash dump?
Look in your ../Release/MacroQuest.ini file, and find the [Plugins] section. Copy/paste it here.

That is the info I need to troubleshoot this, be it an issue with the macro or a plugin. Can you please answer each of those question?
 
That's a 1.0.3 problem, IIRC.
And that's NOT what you were asked to do. That completely invalidates your problem description. I'm not going to beg someone for the info to fix their problem. You're on your own. Good luck.
 
Hi Denethor, bought the macro and tried using the 1.1 version. Instantly received crashes, switched to 1.0.3 and have had no issues with crashes.
 
Sorry to hear you are having trouble. However, I will point out that a macro cannot / should-not-be-able to cause a 'crash' in EQ. However, I'd like to help you resolve whatever issue you're encountering, if it's within my ability. So, when is the crash occurring? When zoning? Middle of a zone? When pausing or unpausing the macro? Was there a error message or a crash dump? What plugins do you have loaded? (Unnecessary plugins are the most common cause of crashes. Not the macro.)

Most reports of crashing are when zoning. However, crashing on zoning isn't cause by the macro. It's typically caused by plugins. But since my macro zones more often than any macro around pretty much, it 'seems' like the macro causes it. So, I understand your frustration with crashes and why you'd assume it was Explore.mac triggering it. So, let's start figuring out what you have that's causing it. Look in your ../Release/MacroQuest.ini file, and find the [Plugins] section. Copy/paste it here. There's a lot of plugins enabled by default that you probably don't need / aren't using. And some have not been maintained for 8+ years.

And what does your Explore_<server>_<toon>.ini have in the General section?
 
Crashes instantly upon issuing the /mac explore command with that version. While the macro in itself can't cause the crash it can trigger the crash. This was a repeated occurrence and crashed exact same way each of the 5 times I attempted to start the macro with the toon (I had no issues with 1.0.3 version doing this.


Explore_<server>_<toon>.ini would be whatever it creates by default, I can't get 1.1 to work at all as it instantly results in the character crashing.



[CODE lang="ini" title="Plugins"][Plugins]
mq2autologin=1
mq2autoaccept=1
mq2bzsrch=1
mq2cast=1
mq2chatwnd=1
mq2cpuload=1
mq2custombinds=1
mq2debuffs=1
mq2eqbugfix=1
mq2eqbc=1
mq2events=1
mq2exchange=1
mq2hud=1
mq2ic=1
mq2itemdisplay=1
mq2labels=1
mq2map=1
mq2melee=1
mq2moveutils=1
mq2nonagwindows=1
mq2rez=1
mq2viewport=1
MQ2Posse=1
mq2advpath=1
mq2nav=1
mq2easyfind=1
mq2autoloot=0
mq2xptracker=1
mq2autoforage=1
mq2tracking=1
MQ2Twist=1
mq2heals=0
mq2aaspend=1
mq2eqwire=1
mq2bucles=0
mq2plattracker=1
mq2killtracker=1
MQ2TargetInfo=1
mq2damageparser=1
mq2farmtest=1
mq2berzerker=1
MQ2XAssist=1
mq2dannet=1
mq2sqlite=1
mq2kissbuffs=1
mq2collections=1
mq2cleric=0
mq2bst=1
mq2monk=0[/CODE]
 
[CODE lang="ini" title="Plugins"][Plugins]
mq2cpuload=1
mq2custombinds=1
mq2debuffs=1
mq2exchange=1
mq2nonagwindows=1
mq2viewport=1
mq2tracking=1
mq2damageparser=1
mq2farmtest=1
[/CODE]

Any of these that are you aren't specifically keeping loaded for a specific reason i'd unload
especially mq2nonagwindows - since its not been supported and hasn't been built in a very long time - not sure if you even have the file - but i would start there
 
No it means it used to load it, the file is no longer there so it no longer loads it.
 
Stripped plugins down to only include the following, started macro and immediately after the startup flashed the client instantly crashed, no dump was stored:


INI: 
targetinfo
eqwire
easyfind
nav
advpath
posse
moveutils
melee
map
labels
hud
exchange
events
eqbc
eqbugfix
debuffs
custombinds
cpuload
chatwnd
cast
bzsrch
itemdisplay
autoaccept
autologin
ic
 
@Denethor

Further stripped down the plugin list, and same problem happens. Doesn't matter which class I've tried it on, new or previously created configuration for the character. Same problem, pretty sure it's safe to say more things are pointing at an issue with 1.1.

INI: 
targetinfo
easyfind
nav
moveutils
melee
map
labels
exchange
events
eqbc
eqbugfix
custombinds
chatwnd
cast
bzsrch
itemdisplay
autoaccept
autologin
ic
 
unload these 3:
labels custombinds bzsrch
and keep em unloaded forever

for having as much unloaded that could cause issues, unload these too.
targetinfo exchange events
 
A macro can very much cause a CTD not sure why you think it cannot. I did experience CTD using this if housing =0 and it was the next step or the only one left.
 
william12 said:
A macro can very much cause a CTD not sure why you think it cannot. I did experience CTD using this if housing =0 and it was the next step or the only one left.
Click to expand...

@Denethor Something changed in the code between what was posted in early November and now in 1.1 that is causing CTDs, not sure what it is but it's in the macro code not otherwise.
 
Eltai86 said:
@Denethor Something changed in the code between what was posted in early November and now in 1.1 that is causing CTDs, not sure what it is but it's in the macro code not otherwise.
Click to expand...

The code has not changed since Nov. 7th... That's when I published 1.1.0 (Alpha) adding LDoN support. No updates have been published since (I need to, I need to publish the bard Selo's fix and a few minor tweaks like that). Now, there have been updates to MQ2 itself, MQ2Nav, MQ2EasyFind, and / or MQ2AutoLoot. I could be potentially aggravating a CTD bug in one of them.

I just fired up a rogue and ran the TBM route. No crashes. When I'm done with playing tonight, I'll fire up another 3-4 toons (at least 1 caster, 1 melee, to trigger potion buying and other start-up routines the rogue wouldn't have called), and see if I can't repro the crash. If I can repro, I can fix it. But if I can't repro the crash, I have no way to fix it. (Can't fix what isn't breaking)
 
Denethor said:
In the mean time, did you try unloading the 6 plugins Kaen listed?
Click to expand...

There should be zero reason to have to unload what comes preloaded with VV. Something changed between November and what is available in 1.1 if I download today. A copy originally downloaded by a friend in November=No crashes, the version I download through here crashes within first 3 seconds of launching. So something is different there.
 
actually, preloaded is based on old old standards of what people used mq2 for, and is basically remnants from 10 years ago, some of those plugins havent been updated for 5-6 years, and trust me the coding in mq2 has changed a lot in that time frame, and so has the eq client, i do a lot with running bare minimum plugins, and hardly ever crash unless i want to, or do dumb stuff.
 
kaen01 said:
actually, preloaded is based on old old standards of what people used mq2 for, and is basically remnants from 10 years ago, some of those plugins havent been updated for 5-6 years, and trust me the coding in mq2 has changed a lot in that time frame, and so has the eq client, i do a lot with running bare minimum plugins, and hardly ever crash unless i want to, or do dumb stuff.
Click to expand...
Yet I have zero issues with crashes any other time, nor do I have issues with an older version of Explorev1.1 that was downloaded by a friend in November. The issue is only occurring when I run download, extract and run Explorev1.1 that I download here. It doesn't happen with v1.03 or the v1.1 that my friend originally downloaded in November.

You're right Sic, I am a little bit hot at the moment. This developer has a paid product that they have released, the last two posts from people about the macro have been about repeated crashing. I've given him as much information as I can because there is no .dmp being generated and his initial response was "Macros can't cause CTD" when in fact they can. Initially trying to pass the buck on where the problem lies. @Redbot
 
As there was only been ONE release of the 1.1.0 code (on Nov. 7th), what you're asserting (a code change from early 1.1.0 to the download code now) is not possible. Or at least, there was no code update published by me. As such, could you please send me the copy you downloaded and your friend's? I'd like to do a code comparison of both with what's in Git to see if that can lead us to an answer.

I have not refused to help you solve the issue. Or attempted to 'pass the buck'. What I have done is attempted to eliminate possible causes in an attempt to determine the root problem.

And yes, the last two people (of which you're one) have complained about crashes. So did several people before you. In each of the prior cases, the root cause of the crash was eventually linked to a plugin. Hence, why I include them in the early part of troubleshooting a report of crashing. If I can eliminate them as a source of the problem, I can narrow my troubleshooting to the code in my macro. Without eliminating it, I could potentially rewrite the entire macro and STILL you might experience crashes. And while you have given me as much information as you feel I need, you have not answered some of my questions. And killerclown before you even less. As such:

1. As asked, did you try unloading the 6 plugins Kaen listed? What were the results?
2. Can you please send me the Explore_<server>_<toon>.ini file for the character in question?
3. (New) Can you enable debug logging within the script? (Explore.Mac, Line 389, set to value of 1) Then run the script and send me the \mq2\release\log\explore.mac.log file that is generated?



As I said in my initial response to you, I am sorry to hear you are having trouble. I'd like to help you resolve whatever issue you're encountering, if it's within my ability. I stand by that statement. I will attempt to help you troubleshoot the problem, even if you are unhappy with the methodology.
 
In response to your questions:
1. I did not because in my own trouble shooting (using the friends downloaded copy) it immediately resolved the issue (e.g. no more crashing). Indicating that there was something in the files that were being downloaded (ie the macro files and includes) were the issue rather then a plugin being the offending culprit. I also loaded the full set of plugins I initially had and no crashes occurred from the version I received from the friend.

2) there is zero reason for me to send you the Explore_<server>_toon>.ini files as this was an issue across cleric, shaman, shadowknight, paladin, ranger, warrior that I tested immediately upon initial creation of the ini files (ie first time the characters ever ran the macro they generated the default ini and crashed immediately). Using the precreated INI's from the RG download did not have issues with the friend version or with 1.0.3 which I switched to in the short term before talking with my friend and trying his copy of 1.1.

3) Sure I can, though not sure why you didn't go to that days ago when I initially posted about the problem.
 
You must log in or register to reply here.
Release Explore.Mac - An Explorer / Traveler Achievement Macro
Next unread thread 🦁

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top
Cart

Cart

Total -