Forum Replies Created
-
AuthorPosts
-
Fair enough, but it was a really easy clear for my hunter with 2 boas.
Autosell works if AutoSell.lua from retail is used in 3.4.1 Wotlk.
August 6, 2021 at 4:51 am in reply to: Issue with Midsummer quest completion check-off, TBC 2.110 #169353Ok thanks for the explanation. Sorry to send you on a goose chase for something that’s working as expected.
Is this one of the guides that indicated you had to manually tick the quest complete (back in retail)? I remember having to do that, but can’t remember which quest chain it was.
August 4, 2021 at 11:52 pm in reply to: Issue with Midsummer quest completion check-off, TBC 2.110 #169351Here’s a video to show what’s happening. This was not recorded from the fresh Wow/Dugi-only installation but they both have the same behavior.
August 4, 2021 at 11:04 pm in reply to: Issue with Midsummer quest completion check-off, TBC 2.110 #169350The last test was on a fresh Wow installation and only the Dugi addon installed.
In your video, Swamp of Sorrows was the next quest in the guide — this always works. The issue is when you honor or desecrate a fire “out of order” from the guide. Instead of Swamp of Sorrows go to Westfall. When you honor the fire in Westfall, Swamp of Sorrows will get checked off as complete.
August 4, 2021 at 7:06 pm in reply to: Issue with Midsummer quest completion check-off, TBC 2.110 #169347There is a typo in line 6 of Midsummer_Bonfires_Azeroth_A.lua. There are 2 references to “map”.
A Honor the Flame |QID|11816| |N|(npc:25898) in (map:1429) in (map:) (43.47,62.63)| |E| |Z|1429| |NPC|25898|
Also a typo in line 14 with a missing colon:
A Honor the Flame |QID|11810| |N|(npc:25892) in (map1428) (80.30,62.89)| |E| |Z|1428| |NPC|25892|
August 4, 2021 at 5:43 pm in reply to: Issue with Midsummer quest completion check-off, TBC 2.110 #169346I just did a fresh install of Wow Classic on a spare computer and installed only the Dugi TBC addon. I tested a toon that’s been sitting idle in Loch Modan and selected the Midsummer Events guide. When I clicked on the fire in Loch Modan, the addon marked Elwynn Forest as complete.
I tried the same thing on a horde toon in Razor City. Upon clicking the fire the guide marked Mulgore as complete. If I select (from within the Current Guide window) Reset and Reload the correct quest is marked.
This does not appear to be a horde vs alliance issue, nor the specific Windows/WoW installation or addon compatibility.
August 3, 2021 at 3:56 am in reply to: Issue with Midsummer quest completion check-off, TBC 2.110 #169345This is on alliance side.
/dugi fix didn’t correct the issue. It’s something I should have known to try.
August 2, 2021 at 2:35 pm in reply to: Issue with Midsummer quest completion check-off, TBC 2.110 #169343I tried disabling every addon except DugiGuidesViewer 2.111 and it’s still occurring :confused:.
Since I’m using flight points, I went from SV to Westfall to Darkshore. When I completed Westfall the Darkshore step was ticked completed. Using the Reload button from the guides list marked Westfall complete, but Darkshore was still complete.
Do you have any suggestions on how to debug what’s going on?
Hi Dugi,
Since the error seemed to be related to security, I tried running 1.4.5 as administrator and it started successfully. Subsequent attempts without running as administrator are working also.
Consider my issue resolved with the solution as: run DugiGuides_1.4.5.exe as administrator.
Thanks.
Dugi, looks like the issue is my Win 7. I made a Win 7 VM and copied my existing installation over and 1.4.5 worked fine.
I uninstall classic using bnet and reinstalled into my World of Warcraft along-side _retail_ and it still doesn’t work. So it has nothing to do with the installation directory.
Any other thoughts? I don’t have another Win 7 machine to try this on, but I could spin up a VM to try.
Dugi said:proxydoctor said:“This Folder doesn’t contain the correct version of this game. Please check the installation path and try again” When i lunch the game. World path and Launcher path both in classic. What i’m I doing wrong guys?have you installed wow classic with the Bnet launcher?
Yes, but it was installed into my World of Warcraft Public Test directory (under _classic along side _PTR) because at the time it was still in PTR. I’m able to run it and after this evening’s update to 1.13.2.31650, the Dugi installer still fails.
As a next step, I’m going to try to uninstall and re-install and direct it to my normal World of Warcraft directory. I don’t expect it to make a difference, but it would be very interesting (for you) if it did.
Dugi said:maxhawk said:I manually copied dugiguides_1.4.5.exe to my laptop and it ran fine, properly picking up the installation directories for _classic and _retail, both of which are located in the same directory (as opposed to my desktop).Try downloading and install the latest 4.8 net framework here
https://docs.microsoft.com/en-us/dotnet/framework/install/on-windows-7I already had 4.8 .NET installed but let it do a repair. However I still get the same error.
I manually copied dugiguides_1.4.5.exe to my laptop and it ran fine, properly picking up the installation directories for _classic and _retail, both of which are located in the same directory (as opposed to my desktop).
-
AuthorPosts