Dungeon ID Fix

[Addicted 0]

I still got a Dire Maul ID after the server restarts. I cannot reset the instance via command. I even deleted my WDB Folder but still did not get rid of this stupid Dungeon ID. Any ideas?

[Spionida 10]

Any possible, and I stress possible fixes are via in-game ticket.

[Addicted 0]

yesterday i already spoke to a gm after writing an ingame ticket and he said i had to wait for the server wide fixes and that he cannot delete my ID...

[Spionida 10]

GMs can not fix Raid IDs - they do not have the software commands to do so. Some of them can clear or partially clear messed up raids. 

Yesterday a fix was put in to correct these things. It did not work on the live servers and was reverted. 

So, if it's a messed up raid ID, there is nothing that can be done. if it's a messed up raid, i.e. bosses respawned etc, then a GM ticket may help. If there are the GMs to get through them.

[Addicted 0]

First of all it is not a Raid ID, its a Dungeon ID. I only have the problem with Dire Maul. The problem is that i cannot reset the instance. If i look under the Raid Info it says:

 

Instance:       ID

Dire Maul      117

Resets in

 

Cause Dire Maul is a normal Dungeon and not a Raid it should not be listed in the Raid Info in the first place.

 

When i walk into the Dungeon the trash is there but the Bosses arent. And if i try to reset the instance by typing /script ResetInstances() nothing happens...

 

There has to be a way even for a GM to Delete the Dungeon ID out of my Raid Info...

[SoulSharer 0]

Having the same problem but for BRD: 

https://forum.elysium-project.org/topic/51188-brd-raid-id/

[Thari 15]

Unfortunately there is nothing we can do until a fix is applied.

[Addicted 0]

Is there any ETA when a hotfix will be applied?

[Spionida 10]

I would think Wednesday at the earliest, not 100% sure. Sometimes communication is not all that it could be.