New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tomb of Sargeras - fix in initial comment #13
Comments
How I was able to get the raid finder IDs was /script local id,name; for i=1,GetNumRFDungeons() do id,name = GetRFDungeonInfo(i);print(i..". "..name.." ("..id..")");end Which returns this
Manually confirming that the 1400 IDs are tomb. So all I need to know is what exactly is parent in the code and I can look up for tomb of sargeras. |
Using http://wow.gamepedia.com/API_GetLFRChoiceOrder It seems either 1525, 1526, or 1527 is the parent id for tomb. This is the dump of the following script /run for i, v in ipairs(GetLFRChoiceOrder()) do print(i, v, GetLFGDungeonInfo(v)) end 1 -53 Legion Normal 1 |
Only problem is I still am getting the following [04:10:15] SavedInstances: SavedInstances: ERROR: Refresh() failed to find instance: Tomb of Sargeras : enUS : 1676 So what I am wondering is where else are you now saving normal and above raid instances?! |
Found the fix for this...and its quite silly. SavedInstances is currently only grabbing instance data for instanceID's through 1500, and Tomb of Sargeras has ID's 1525, 1526, and 1527. So the code is not even getting to those ID's. Line 1398 currently reads The proper parentID for ToS should be 1527 to keep it in line with previous raids using the highest instanceID for the parent. We won't know the proper remaps until all four LFR wings open. If you recall the remap issues with Nighthold, they were all initially not remaped, providing proper LFR appearance when Arcing Aqueducts (wing 1) opened. However, when Royal Athenaeum (wing 2) opened, we had to remap wings 2-4 as |
Thanks for finding that. I was trying to find this late last night and was tired lol. I think that id has to go to 1700 as the instance ID for tomb is actually 1676 but the lfr choice order is 1527 for the parentID |
One more thing. I think that maxid variable should be global to the addon and set at the top of the code so it is easily found and changed as more dungeons and raids are added. 1700 works for now to add tos |
Where are you getting 1676 from? I'm not seeing that in any data dumps. Regardless, 2000 or 1700 will work for ToS, I do agree that maxid should be at the top, perhaps right below maxdiff and maxcol. I moved it below them as this: local maxid = 1700 -- highest possible value for an instanceID, current max (Tomb of Sargeras) is 1676 |
It's right form the error printout as well as actually going into the raid and dumping via /dump GetInstanceInfo() I would assume you don't want to set maxID too far past the highest current raid ID to prevent the potential for taint or other errors to form. |
Oh, ok. I didn't do that dump while I was inside, but there isn't really any cause for taint from going too high as it'll just return I uploaded a .zip on ticket #8 that includes the ToS fixes, as well as emissary and keystone fixes. This fix goes to 2000, but you can adjust it down to 1700. |
Leave it to 2000. I bet there won't be an issue and if there is it can get adjusted as needed ;) |
EDIT...
I am editing this initial comment to suggest changes to add in TOS
For LFR
After line 149.
[1494] = { total=3, base=1, parent=1527,altid=nil }, -- TOS1: The Gates of Hell
[1495] = { total=3, base=4, parent=1527,altid=nil, remap={ 1, 2, 3 } }, -- TOS2: Wailing Halls
[1496] = { total=2, base=7, parent=1527,altid=nil, remap={ 1, 2} }, -- TOS3: Chamber of the Avatar
[1497] = { total=1, base=9, parent=1527,altid=nil, remap={ 1 } }, -- TOS4: Deceiver's Fall
This is based on the current information that wing 1 is 3 bosses, wing 2 is 3 bosses, wing 3 is 2 bosses, then kiljaeden is alone in the last wing. The remap may not be correct but it is my best educated guess.
To open TOS for normal and above change
local maxid = 1500
to
local maxid = 1700
TOS is instance ID 1676 so it needs to be above to include. 1700 should be the closest without risking possible errors.
The text was updated successfully, but these errors were encountered: