-
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! 👋
Question - Possible to get a pre-dannet version of 11.05?
- Thread starter Dozecar
- Start date
There were no changes to the follow code this round, Navigation No changes to the follow, or chase code. Buffing Null is a bigger problem than kiss, everything I have seen posted points to an MQ2 Issue.
/echo Buffing MA >> ${Spawn[=${MainAssist}].CleanName} << with ${SpellToCast}.
Showing:
Buffing MA >> NULL << with Vicarum's Retort Rk. II.
That is only possible if you started casting on the MA and then the MA left the current zone. So basically the MainAssist was not in the casters current zone. Kiss will not try and cast on a character if they are NOT in the current zone.
The jiggle dance should of be fixed. The Assisting issue I am not aware of.
Give this a try first.
/echo Buffing MA >> ${Spawn[=${MainAssist}].CleanName} << with ${SpellToCast}.
Showing:
Buffing MA >> NULL << with Vicarum's Retort Rk. II.
That is only possible if you started casting on the MA and then the MA left the current zone. So basically the MainAssist was not in the casters current zone. Kiss will not try and cast on a character if they are NOT in the current zone.
The jiggle dance should of be fixed. The Assisting issue I am not aware of.
Give this a try first.
Dozecar
Well-known member
- Joined
- Mar 21, 2016
- RedCents
- 1,696¢
Basically Last night I logged in with just a few toons, I didn't notice the buff issue but I only had the cleric on, which so far I haven't seen it buff null yet. But the other 2 toons were behaving oddly. The mage was doing nothing. One time I did get it to summon a pet and buff it, gave toys and armor, but still didn't assist or send in pet. Just sat there with nothing in the target box while I killed things. Also the bard for at least the first half of the session was only meleeing. No Songs or mezzing. Then finally it did begin twisting and mezzing. I was grouped with friends, and only on for a short time, so I really didn't trouble shoot or anything.
The buffing issue I'm trying to get you a debug, but I logged everyone in yesterday morning, loaded kiss and logging and debug, and of course it didn't happen.
When it did happen, no one had left zone. The first time I noticed it, was about a week ago, with the bard. It would click it's sword 3 times in a row for symphony of battle. Kept happening Song. Then click null click null click null. Song, Click null click null click null. This was on start up. It is possible that it was only a double click though, I believe my ini (Sic's) calls for it twice in the buffs, once for ME and once just generic. Something I've been meaning to edit.
Next time I noticed it was the BL, again on start up. Double casting on null. Then we had a few deaths, and the chanter was just chain casting VoP on null. Like 4 times. Stopped, loaded the spell that was supposed to be in gem8, then reloaded vop in gem8, and 4 more casts on null. Whole group in zone. It's possible that it was a fresh load though. I have an unload key that unloads zerk and rog plugins and ends macs. Especially lately, I've gotten in to the habit of unloading/ending and reloading/restarting whenever I change zones, or play for a while. That particular night every thing was shit. My zerk and rogue were only doing 200k on burn calls and averaging 120k without. So I reloaded a bunch of times trying to fix it. My zerk and rogue usually do 1.5m on a group named burn and 3-400k for just normal mobs. (Combined not seperate, they aren't that great lol)
Another issue and I need to test without MQ running. My toons regularly crash zoning since the patch. Actually EQ just locks up. Almost every zone, 1 of the 6 just locks up when zoning. I had blamed wineq for it, because I purchased isoboxer, which updated me to eqwin2 pro, but I've run eq with wineq not running, and I still lockup. Then I have to kill the process and restart. Not sure if this means anything, but when I kill the process, that's when the toon leaves eqbs2. That's why I say it locks up, rather than crashes. This happens across 2 laptops or just one, so it's not isolated to just just 1 install.
Also, my zone times have increased. Prior to the last patch, my zone time was 16 seconds. That was with 3-6 EQ running. I timed it this morning and with just a single EQ instance, I'm at 24 second zones.
Btw, I'm just mentioning all this because it's all been happening since the last EQ Patch. And maybe others are having the same issues. Also, quite recently one of the devs said they were working on something that would combat mq2. The take I got from it was not more GM presence, but more of a code issue. You're saying (in this and other threads) that some of the issues are MQ related. Is it possible they altered the core EQ code in such a manner that is making MQ have issues?
I'm about to try logging in multiple toons without MQ and see if I get the lockup or not. I have run around zoning over and over again with just 1 EQ and MQ running and no lock up.
The buffing issue I'm trying to get you a debug, but I logged everyone in yesterday morning, loaded kiss and logging and debug, and of course it didn't happen.
When it did happen, no one had left zone. The first time I noticed it, was about a week ago, with the bard. It would click it's sword 3 times in a row for symphony of battle. Kept happening Song. Then click null click null click null. Song, Click null click null click null. This was on start up. It is possible that it was only a double click though, I believe my ini (Sic's) calls for it twice in the buffs, once for ME and once just generic. Something I've been meaning to edit.
Next time I noticed it was the BL, again on start up. Double casting on null. Then we had a few deaths, and the chanter was just chain casting VoP on null. Like 4 times. Stopped, loaded the spell that was supposed to be in gem8, then reloaded vop in gem8, and 4 more casts on null. Whole group in zone. It's possible that it was a fresh load though. I have an unload key that unloads zerk and rog plugins and ends macs. Especially lately, I've gotten in to the habit of unloading/ending and reloading/restarting whenever I change zones, or play for a while. That particular night every thing was shit. My zerk and rogue were only doing 200k on burn calls and averaging 120k without. So I reloaded a bunch of times trying to fix it. My zerk and rogue usually do 1.5m on a group named burn and 3-400k for just normal mobs. (Combined not seperate, they aren't that great lol)
Another issue and I need to test without MQ running. My toons regularly crash zoning since the patch. Actually EQ just locks up. Almost every zone, 1 of the 6 just locks up when zoning. I had blamed wineq for it, because I purchased isoboxer, which updated me to eqwin2 pro, but I've run eq with wineq not running, and I still lockup. Then I have to kill the process and restart. Not sure if this means anything, but when I kill the process, that's when the toon leaves eqbs2. That's why I say it locks up, rather than crashes. This happens across 2 laptops or just one, so it's not isolated to just just 1 install.
Also, my zone times have increased. Prior to the last patch, my zone time was 16 seconds. That was with 3-6 EQ running. I timed it this morning and with just a single EQ instance, I'm at 24 second zones.
Btw, I'm just mentioning all this because it's all been happening since the last EQ Patch. And maybe others are having the same issues. Also, quite recently one of the devs said they were working on something that would combat mq2. The take I got from it was not more GM presence, but more of a code issue. You're saying (in this and other threads) that some of the issues are MQ related. Is it possible they altered the core EQ code in such a manner that is making MQ have issues?
I'm about to try logging in multiple toons without MQ and see if I get the lockup or not. I have run around zoning over and over again with just 1 EQ and MQ running and no lock up.
Download the latest kiss I posted earlier today, I was able to find 1 of the Buffing NULL issues. I will need a debug log of this happening to help trace down where in the Buffs routine this could be happening. I was looking through a log someone PM'd me this morning and the log had the buffing MA NULL message, and there is only one place in Kissassist where that message is displayed. The problem is there is code in place that won't let you get to the message if ${Spawn[=${MainAssist}].CleanName} returns NULL.
Looking at the code I don't see how the /echo Buffing MA >> ${Spawn[=${MainAssist}].CleanName} << with ${SpellToCast}. is ever executed if either of the ${Spawn[=${MainAssist}].CleanName} or ${SpellToCast} return NULL.
Looking at the code I don't see how the /echo Buffing MA >> ${Spawn[=${MainAssist}].CleanName} << with ${SpellToCast}. is ever executed if either of the ${Spawn[=${MainAssist}].CleanName} or ${SpellToCast} return NULL.