When using Kissassist, or mule's variant my casters will frequently mem the spell set loaded by name defined in my characters ini, but subsequently will unload and memorize an older spell instead, which is not defined in my loaded spell set, nor anywhere in the ini. it's very frustrating, because the dps section and buff section fall apart when the needed spells aren't loaded. DPS especially as there isn't a trigger to load the spell to cast it like there is with a buff wearing off. This habitually happens if i have a DD spell or something similar loaded in my gem 8 slot, which is my swap out, so I'm wondering if that's the culprit. I don't recall offhand if I see it in other gem slots or not. I've moved those DD's, but it does seem to be a bug, perhaps with mq2cast? Where a variable is being defined with a spell, and when you upgrade, it's over-riding with what's been stored in the variable prior? If i reboot I don't have the problem again until i'm leveling a lowbie and upgrading spells/spell sets get where spells get redefined and I /end and reload kiss again to utilize the updated ini for that character.
-
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 - spell memming/rememming (1 Viewer)
- Thread starter toadwart
- Start date
- Joined
- Mar 9, 2017
- RedCents
- 13,167¢
Is the older spell on the toon's spell bar when you start KA? If so, MiscGemRemem is trying to set it back to whatever was there when you started. It checks when you start KA, not when you load your spellset.
This tells KA, use slot 13 for any random spells you need to load/cast and afterwards re-memorize whatever was in 13 when I started KA :
You can just turn it off if it's throwing your spell set off:
This tells KA, use slot 13 for any random spells you need to load/cast and afterwards re-memorize whatever was in 13 when I started KA :
Code:
MiscGem=13
MiscGemRemem=1You can just turn it off if it's throwing your spell set off:
Code:
MiscGemRemem=0
Last edited:
Makes sense I guess, but it's a bit of an abrupt left turn for low level characters, who might start with a level 1 spell in spot 8, but by the end of a days play session they're level 35 or whatever, and that spell slot has been rotated through 10-30 other spells during the play session. That initial spell sticking around is going to be annoying all day unless you quit out and restart, but I guess that works either way. Generally I do want it to remember the last spell there and remem it, but the last spell there wasn't necessarily the spell that was there when I logged into the game, it was the spell that was there 30 seconds ago when KA removed the spell in that spot and memmed a new one. It ought to refresh that variable when it "forgets" a spell to mem a new one I would think.
There are instances where you want the routine to ignore the re-meming back the previous spell. if you look through the code and search for -nomem. You can figure out why there are times we force the routine to NOT re-mem the last spell. One good example would be when buffing your group with a single target spell. If we don't ignore re-meming the spell. Then the caster would 1 - mem buff spell, 2 - cast buff, 3 - re-mem previous spell, repeat starting at step 1, until all characters buffed. By skipping the re-mem step things work much better.
Because you can have a mob come into camp while you are in the middle of buffing. When that happens the buff routine is aborted and the DPS routine kicks in. Would you want your buffer to try and re-mem a spell while a mob is in camp?
The best I can think of doing is to add a check in the DoMiscStuff routine and if the MiscGem has the wrong spell, then re-mem the correct spell.
The best I can think of doing is to add a check in the DoMiscStuff routine and if the MiscGem has the wrong spell, then re-mem the correct spell.
Just to circle back around on this, and addressing your post #4 above Ctaylor, I've found that there is still some odd functionality going on here. I've had characters mem a spell, cast it on one group member, re-mem the original spell, then immediately forget it and memorize the buff again to cast it on the next character, rinse and repeat 6 times. Watched them do this on several occasions yesterday while playing.
There are also times when my SK has just pulled a mob into camp and as the MA he should be melee'ing, but for some reason the routines decide he needs to sit down and mem a new spell, halfway through the first round of combat, even though he already established aggro on the mob he was pulling back to the group. Other times I'll cast a spell on a mob to pull it, and partway back to camp my character will try to stop and sit down to mem a spell while I'm actively running back to camp, as if the aggro mob beating the crap out of my ass isn't important or anything. I know this is part of the functionality of MQ2Cast, it's just that it's more of an oddity that I dislike about the plugin.
There are also times when my SK has just pulled a mob into camp and as the MA he should be melee'ing, but for some reason the routines decide he needs to sit down and mem a new spell, halfway through the first round of combat, even though he already established aggro on the mob he was pulling back to the group. Other times I'll cast a spell on a mob to pull it, and partway back to camp my character will try to stop and sit down to mem a spell while I'm actively running back to camp, as if the aggro mob beating the crap out of my ass isn't important or anything. I know this is part of the functionality of MQ2Cast, it's just that it's more of an oddity that I dislike about the plugin.
First off I would check and make sure that any of the spells you need for pulling and DPS are perma memmed in one of your spell gems. If you have a spell using your MiscGem slot that you need for DPS or pulling, then there is nothing the macro can do about it.
We have made so many changes in Kiss 11 that this may be a mute point, or we could of made it worse. I appreciate you circling back around, because I keep a list of this kind of stuff and review it as we are making changes.
We have made so many changes in Kiss 11 that this may be a mute point, or we could of made it worse. I appreciate you circling back around, because I keep a list of this kind of stuff and review it as we are making changes.
I've not played with 11 yet. I'm still learning my way through 10, and the nuances of what does and doesn't work. A lot of the base settings I've got down, aside from wierd things such as this that more often than not are just pet peeves about how I wish it ran the way I think it should run. I still dont understand why you'd want to stop running to cast a spell for instance. I'd rather parse the info to a text message or an array and cast it when I stop moving. 99% of the time I'm going somewhere so either a mob's on my ass, or im moving a group on follow. A stop to cast a spell in either situation is a recipe for disaster. I'd like some instacast oh shits , or maybe some fast casts if the spell is memmed, but otherwise hold off on that crap. Its livable as is, but annoying at times, and frustrating that I lack the time to spend learning ways to correct it myself.