• 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

Problem - Possible issue with the new ImmuneData functionality

Joined
Jun 17, 2015
RedCents
154¢
I am clearing NToV on EQMight server.

I was manually changing loadouts between fights to have the appropriate spells memmed following the details outlined on the EQM page about each bosses resists, but I thought I would test the new resists system to see if its as easy to use as it seemed. This is with default config, I ensured that UseImmuneData was set to True, and that Lord Kreizenn was appropriately marked as Fire Immune by the Named List.

Hop into combat and watch my necromancer cast Funeral Pyre of Kelador on repeat until about 50% mana when i manually enabled SkipFireSpells and the combat continued how I would have expected it to with the Fire Immune flag being on Lord Kreizenn. Am I expecting the wrong behavior from the UseImmuneData setting, or was there something not working as intended?
 
I am clearing NToV on EQMight server.

I was manually changing loadouts between fights to have the appropriate spells memmed following the details outlined on the EQM page about each bosses resists, but I thought I would test the new resists system to see if its as easy to use as it seemed. This is with default config, I ensured that UseImmuneData was set to True, and that Lord Kreizenn was appropriately marked as Fire Immune by the Named List.

Hop into combat and watch my necromancer cast Funeral Pyre of Kelador on repeat until about 50% mana when i manually enabled SkipFireSpells and the combat continued how I would have expected it to with the Fire Immune flag being on Lord Kreizenn. Am I expecting the wrong behavior from the UseImmuneData setting, or was there something not working as intended?
Add this NPC as a custom NPC with that immunity and please let me know if the issue persists.

We want to know if there's a typo, etc, in the default named list, or a deeper issue through the system. I was using it elsewhere last night and did not have the issue.

Cheers!
 
Will try it on the next named and report back!
Thanks my dude much appreciated
If no light bulbs go off when you try that then I'll just jump into the zone myself later today (and review the code ofc, maybe I bollocksed something while I was cleaning up or smth)
 
Okay - so instead of waiting for the next named i thought I would just flag the next few trash mobs as named, and mark them all as immune to fire.

Same result, Necromancer would attempt to chain cast Funeral Pyre of Kelador (these particular trash mobs are mostly fire immune anyway but it helped prove the concept)

I am going to try deleting the necro config file itself and repatching it jus to ensure there is nothing wrong there itself and report back again.

Edit: Will also report that my Ranger is also casting his fire based nukes on targets I have flagged as Fire immune.
 
I deleted the entire RGMercs folder and reloaded it through redfetch.

Same result, not respecting the immunities that are assigned.

If there is anything that you'd like me to check in the logging I am happy to do so
 
I deleted the entire RGMercs folder and reloaded it through redfetch.

Same result, not respecting the immunities that are assigned.

If there is anything that you'd like me to check in the logging I am happy to do so
This wasn't my experience when I was using it last night but I will certainly take a look and let you know. Thanks.

I was also not fully updated last night so maybe that matters.
There is one commit I'll have a look at.
 
The issue was as I suspected. There will be a fix soon(ish). Cheers!

Edit: Fix should be in, please let me know if you have further issues. Sorry for the inconvenience!
 
Last edited:
Problem - Possible issue with the new ImmuneData functionality

Users who are viewing this thread

Back
Top
Cart