WowAce

Hey,

In The Rookery, the debuffs put in the RaidDebuffs category (under the proper dungeon's & boss' name) are not displayed at all in the second part of the dungeon (like during the 2nd boss for instance), even though name/ID match, so I think it has to do with the zone ID being different after the very first part of the dungeon? (I know a similar issue was occuring in Spires of Ascension back in Shadowlands at least, during an early build)

If you have any way of fixing this, it'd be greatly appreciated :D

Thanks in advance! <3

Currently i cannot test the dungeons by myself so maybe you can follow this steps:

1. Go to General/About Tab, In debug section enable  the "Grid2RaidDebuffs" checkbox.

2. Do a  Rockery dungeon (in any difficulty)

3. Some Grid2 debug messages should be displayed in chat when entering the dungeon and after changing zones inside the dungeon, something like this:

Grid2: DEBUG Grid2RaidDebuffs Zone[ZoneNAme] C_MapID[xxx] EJID[xxx] mapID[xxx] Status [raid-debufs]: X raid debufs loaded.

Post here those debug messages  specially for first and second part of the dungeon, the most important information are the numbers displayed in the messages.

When you are in the first and second part of the dungeon you can reload the ui for example with the "/reload ui" chat command,  this will reload de raid-debuffs displaying the debug messages too.

Probably the issue should happen only if you reload the UI on the second part of the instance (and the numbers displayed in the debug message should be different).

Hey,

Yeah I just did it, I'll paste here the 2 screenshots from the two parts of the dungeon:

Part 1 (the one that is working):

Part 2 (the one not working):

One thing worth noting btw, is that I did these tests in Normal mode (to be able to solo), and I actually saw debuffs in the last part of the dungeon, but I can't see them in M+ (even though they're the same debuffs, I even put them via name instead of ID to be sure it was not an additional ID with the same name & stuff).
I had to do a /reload though for the 2nd screenshot during my Normal test run, in front of the 2nd boss (otherwise nothing was showing), while in M+ I obviously don't, so maybe they just don't load without a /reload for this second part? (that'd explain why I saw them in this Normal test run while doing the test)

Try out 2.8.74-beta version.

Im assuming the screenshosts where swapped, because in the first screenshot the dungeon was not detected (you can see 0 at the end of the messages, this means an invalid/unknow instance)

But in the second screenshot the correct rockery identifier is displayed, number 1268, and 29 raid debuffs were loaded.

In the first screenshot 11 debuffs were loaded too, but there are no debuffs defined for the instance 0 in the data provided by grid2, so im assuming you used in the past the "Autodetection" feature, and some debuffs were autodetected and assigned to the 0 instance.

You can goto raiddebufs/modules/custom debuffs and check if some unknown instance (with the code 0) exists, there you have the option to remove that autodetected instance.

Hey,

Nah the screenshots were not swapped, and their order is actually correct (you can double check it via the timestamp on the left, first screenshot was made at 10h20, second one at 10h28).

To give some lore: the 1st screenshot was made instantly while zoning into the dungeon (it appeared instantly in my chat). The 2nd one was made in front of the 2nd boss, after a /reload (nothing new was showing before that /reload when I reached him).

I never ever used the Autodetection feature actually (I always put debuffs myself, one by one, for every boss/trash). Some debuffs were already there after updating the add-on, but yeah I never enabled the autodetection feature (I double checked, it's still disabled as of today).

I checked the Custom debuffs (in the RaidDebuffs > Modules section), but I couldn't see any unknown instance with the code 0 unfortunately (I only saw a bunch with a 6-digits code, and none of them matched the debuffs in The Rookery).

I'll still try your new version in any case!

Just did a new Normal test run with the new version you provided, and it seems to work without any /reload now.

I'll still double check in M+ just in case in the near future if it still works, and will reach out to you if necessary of course!

But for now, the new version might have done it, thanks a lot!

Yeah, triple checked, everything works perfectly now, cheers!