-
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! 👋
Problem - Inject Failed
- Thread starter spudz90
- Start date
I don't believe this is specific to the SK, as I get this as well after the latest EQ update (and my SK was not one of them). It's sporadic for me, and occurs before I even select a character from the select screen, but it is occurring somewhere between the server select and the character select screen. I am using the latest update, as of this morning 10/28/18 it says it's up to date. I am not using autologin, but logging in on each of my accounts manually.
Yesterday it happened to 4/6, today it was just 1/6, and the 1 today was not any of the ones it hit yesterday. Also, yesterday after I got logged in and running on all of them they ran fine until I quit last night, at which point I got the error again when I was camping to desktop with at least one account, but 3 of the 6 locked up when I got the error, and eventually either finished the camp or CTD, but I was unable to tell from how they appeared as they closed.
Yesterday it happened to 4/6, today it was just 1/6, and the 1 today was not any of the ones it hit yesterday. Also, yesterday after I got logged in and running on all of them they ran fine until I quit last night, at which point I got the error again when I was camping to desktop with at least one account, but 3 of the 6 locked up when I got the error, and eventually either finished the camp or CTD, but I was unable to tell from how they appeared as they closed.
spudz90
CASH GRAB
- Joined
- Sep 8, 2015
- RedCents
- 150¢
I have the newest update, and it doesn't matter what toon I log in with. I think I fixed it, deselected plugins logged in fine then selected them back and it logs in except I don't have the MQ2 box anymore, all the MQ2 spam is in my regular window.
- Joined
- Dec 14, 2010
- RedCents
- 189¢
/plugin mq2chatwnd
Warl0ck45
Well-known member
- Joined
- Jan 31, 2014
- RedCents
- 8,554¢
Toad I have seen the same thing recently. You will find that the crashed eqgame.exe went to a background service. For instance if you recently updated, the updater may have paused to say X amount of instances of eqgame.exe was running, even though you have none up.
I haven't a clue whats causing it, EQMule seems on the job. Right now it appears MQ2Melee is the issue, or part of the issue. Just unloading that for now ought to kep EQ working stable for ya for the time being.
As for the toons you crashed out on (and propably finding you can not log them back in with out the same error) try restarting your PC (a "cold boot" is best... powering off for 10s+ before restarting) This seems to work for me until the next time that toon crashes out again (as in, I can log in that toon)
You can also try logging in a different toon on the same account and then switching characters (what I do when I crash out during a "get this toon ehre to loot" time)
At the least though, wanted to say "you are not alone!" =)
Personally, I am leaning towards this being a windows issue... invariably when this starts getting worse I see a "installing update" on reboot.
I haven't a clue whats causing it, EQMule seems on the job. Right now it appears MQ2Melee is the issue, or part of the issue. Just unloading that for now ought to kep EQ working stable for ya for the time being.
As for the toons you crashed out on (and propably finding you can not log them back in with out the same error) try restarting your PC (a "cold boot" is best... powering off for 10s+ before restarting) This seems to work for me until the next time that toon crashes out again (as in, I can log in that toon)
You can also try logging in a different toon on the same account and then switching characters (what I do when I crash out during a "get this toon ehre to loot" time)
At the least though, wanted to say "you are not alone!" =)
Personally, I am leaning towards this being a windows issue... invariably when this starts getting worse I see a "installing update" on reboot.
Ok, with the help and advice of a few friends I tried several different things, with the final fixing the issue for me. I ended up fully reinstalling MQ2 from the Very Vanilla download by first backing up my MQ2 Release folder, closing all related MQ2 programs (very vanilla, eqbc, etc.), and then uninstalling. Uninstalling didn't completely wipe my folders, so I renamed the old Release folder to Release.old and the ran the current Very Vanilla (RedGuides_VeryVanilla.exe) again. After which I copied back my .ini files and some .mesh and .json files from the MQ2Nav folder. This fixed it for me and I'm no longer getting the Inject Failed messages on any of my toons. Just thought I'd pass along what worked for me. Hope this helps.
Also, I'm not sure how, but I think the updater is not updating some files, because our guess was that some of the .DLL files were out of sync and thus causing the problem. Perhaps there needs to be a thorough file check available (via a checkbox or something) so that we can be sure that every file is current, and if not, to update it. Perhaps a thorough check is already happening but somehow what passed as my previous updated install and my new install isn't the same. Both check out as being the current/updated version but only the reinstalled version works. ? Anyway, I hope this helps. Ttyl, Sam
Also, I'm not sure how, but I think the updater is not updating some files, because our guess was that some of the .DLL files were out of sync and thus causing the problem. Perhaps there needs to be a thorough file check available (via a checkbox or something) so that we can be sure that every file is current, and if not, to update it. Perhaps a thorough check is already happening but somehow what passed as my previous updated install and my new install isn't the same. Both check out as being the current/updated version but only the reinstalled version works. ? Anyway, I hope this helps. Ttyl, Sam
The updater checks a single file which tells it the last time you updated. If you modify your dll or macro files it won't have a clue, but it will overwrite them next update.
If you want a fresh copy of the compile without installing, grab the zip (first post of release thread).
All .dll files are included and updated, except for mq2eqwire and mq2slotcolors which you must grab manually each patch (for now).
If you want a fresh copy of the compile without installing, grab the zip (first post of release thread).
All .dll files are included and updated, except for mq2eqwire and mq2slotcolors which you must grab manually each patch (for now).
Throughout the past five days of playing I've observed repeated behavior on my 7 instances. The "inject failed" issue happens when changing screens. the vast majority occur when logging in or logging out, and always related to the character select screen, either entering it from the server select option or when camping a character out to switch to a different toon. The few exceptions have been due to zoning, usually a gate spell from one zone to another causing the other occurrences.
Don't know if that's helpful, but it seems to be repetitious for me, so thought I'd bring it up.
Don't know if that's helpful, but it seems to be repetitious for me, so thought I'd bring it up.
thank you
Jakeman750
New member
- Joined
- Nov 20, 2017
- RedCents
- 10¢
Still happened to me this morning. Redguides fully updated. Got all 5 characters up and loaded. Turned on very vanilla and immediately got the message "The parameter is incorrect." 3 of the 5 toons had crashed.
Darn, I'm unable to replicate.
Possible fixes:
https://www.redguides.com/community/threads/crashing-and-minidumps.65489/
Possible fixes:
- In your EverQuest folder, rename/backup/delete eqclient.ini and let EverQuest make a new one
- Make sure "compatibility mode" is off for EverQuest & Macroquest2. (Right-click the exe & shortcuts > properties > compatibility)
- If you have mq2eqwire or mq2slotcolors, makes sure you re-download them each patch.
https://www.redguides.com/community/threads/crashing-and-minidumps.65489/
1. Per Redbot: Renamed eqclient..., compatibility mode off for EverQuest and Macroquest2... no love.
2. Complete new MQ2 install and update... no workie, same crash.
3. Unloaded MQ2melee... nope.
Sent eqmule 3 independent crash dmp files.
For me, it always happens when KISS is started. 9/10 of the bots crash (no pattern to which ones). I have a small routine I run for rezzing my corpses in Guild Lobby. Runs the routine, buys a Soulstone, hands to the corpse summoner fine. Macro ends fine. When I rez the corpse the moment the corpse disappears... eqclient crashes out.
I probably should spend the day raking leaves and preparing the garden for winter anyway!!
JJB
2. Complete new MQ2 install and update... no workie, same crash.
3. Unloaded MQ2melee... nope.
Sent eqmule 3 independent crash dmp files.
For me, it always happens when KISS is started. 9/10 of the bots crash (no pattern to which ones). I have a small routine I run for rezzing my corpses in Guild Lobby. Runs the routine, buys a Soulstone, hands to the corpse summoner fine. Macro ends fine. When I rez the corpse the moment the corpse disappears... eqclient crashes out.
I probably should spend the day raking leaves and preparing the garden for winter anyway!!
JJB
Last edited:
May I see the plugin section of your macroquest.ini?
Thank you for helping us find this crash
DanteAlgier
Member
- Joined
- Nov 22, 2017
- RedCents
- 50¢
Is there a way to roll back the update of today patch, the last build was working for me with zero problems?
If anything I should change, or even if not, please let me know and I will check
Code:
[Plugins]
mq2aaspend=0
mq2advpath=1
mq2afnuke=0
mq2autoaccept=1
mq2autocamp=0
mq2autoforage=0
mq2autogroup=0
mq2autologin=1
mq2autoloot=0
mq2autosize=0
mq2bandolier=0
mq2bardswap=0
mq2bucles=0
mq2bufftool=0
mq2bzsrch=1
mq2camera=0
mq2cast=1
mq2charnotes=0
mq2chat=0
mq2chatwnd=1
mq2clipboard=0
mq2combat=0
mq2cpuload=1
mq2cursor=0
mq2custombinds=1
mq2damageparser=0
mq2dannet=1
mq2debuffs=1
mq2discord=0
mq2dpsadv=0
mq2easyfind=1
mq2eqbc=1
mq2eqbugfix=1
mq2events=0
mq2exchange=1
mq2fearrunner=0
mq2feedme=0
mq2finditem=0
mq2fps=0
mq2gmail=0
mq2gmcheck=0
mq2headshot=0
mq2heals=0
mq2hud=1
mq2hudmove=0
mq2ic=1
mq2irc=0
mq2itemdisplay=1
mq2killtracker=0
mq2labels=1
mq2linkdb=0
mq2log=0
mq2map=1
mq2medley=0
mq2melee=1
mq2missing=0
mq2moveutils=1
mq2mybuttons=0
mq2nav=1
mq2netbots=1
mq2netheal=0
mq2nonagwindows=1
mq2notepad=0
mq2paranoid=0
mq2plattracker=0
mq2portalsetter=1
mq2posse=1
mq2pvpalert=0
mq2radar=0
mq2raidutils=0
mq2randomstuff=0
mq2relaytells=0
mq2reward=0
mq2rez=1
mq2search=0
mq2slave=0
mq2spawnmaster=0
mq2spawns=0
mq2spawnsort=0
mq2speaker=0
mq2spellhotkeys=0
mq2spellsearch=0
mq2targetinfo=1
mq2targets=0
mq2telnet=0
mq2tooltip=0
mq2tracking=0
mq2tributemanager=0
mq2twist=0
mq2vendors=0
mq2viewport=0
mq2worsthurt=0
mq2xptracker=0
Last edited:
We're about to push another update in ~30 minutes that will hopefully fix some crashes. If that update doesn't help,
Try with
mq2nonagwindows=0
mq2portalsetter=0Nope. Didn't work.
For those eqclients that did not crash, per what Dreamflux says, when I do /endmacro, those also crash...
So far that seems to be working. Got through a few pulls.
I realized that my 'startup' macro calls other macros (depending on the character/class), so I guess if that includes an implicit /endmacro... then that would mean my problem was the "/endmacro".
Many thanks. Will report back as soon as I see an issue. I've got my team running now, so if you don't hear back, it means everything is happy.
