![]() It has been known that four mounts would come from the Adventure Table, the Shadowlands equivalent to the mission table from past expansions. In this post, we will talk more about the Adventure Table mount missions, as well as spotlight a very useful Adventure Table addon, Venture Plan!įor more information about Shadowlands Adventures, please check our guide!Ĭovenant Adventures: Missions Upgraded for Shadowlands Before, it would say (ranged).Players have started reaching the higher level missions from the Shadowlands Adventure table, which contains mount rewards from them. ![]() Look in the tooltip at the line below the name, it should now say (melee) at the end. If you want, you can check if the above fix has worked by hovering your mouse over such a Companion or Enemy in the Select Adventurers screen. Hunter Becomes the Hunted, Frenzied Razorwing (73998, see Mission failled: Hunter Becomes the Hunted #62).Piratical Problems, Corsair Cannoneer and Corsair Wavebender (73846, 73848, 73850, 73852, see Mission "Piratical Problems" failed #45).Customary Shakedown, Support Officer (73718, 73720, 73722, 73724, see Mission "Customary Shakedown" failed #39).Learn from the Master, Security Specialist (73654, see Mission failed: Learn from the Master #51).Elwyn (1225, see Mission failed: Sharp Hides, Sharper Teeth #54).The following (using the associated numbers in parentheses): Which Companions, Enemies, and Missions are now simulated correctly by this fix? This way its simulation becomes much more accurate. However, she actually attacks the closest enemy and the above line of code makes sure VenturePlan knows this. She has a role of Heal/Support, so VenturePlan assumes that she will attack the furthest enemy. Take for example Elwyn, a new Companion for Night Fae. These numbers tell VenturePlan when a Companion or Enemy has a different auto attack than what its role would suggest, hence the name overrideAA. If it doesn't, undo the change from step 3 (use Ctrl-Z in your text editor or your backup) and try to copy paste from step 3 again, making sure to get every character of the line of code. Save the file and login to a character in WoW that uses VenturePlan and check if it is still working. Scroll down a bit until you see the line that starts with local overrideAA = Go to your World of Warcraft folder and then to the folder _retail_\Interface\AddOns\VenturePlan\ and open vs.lua in a text editor (like Notepad). ![]() With that out of the way, it is actually only a matter of copy pasting 1 line of code: If you have a backup, this risk should be minimal. Note: an incorrect fix may break VenturePlan, so make sure you have a backup of vs.lua to be safe. I will update this if anyone finds any more fixes, so please comment if I have missed anything. To help others achieve the same I would like to gather here all fixes that are known so far and a guide on how to apply them. I had the problem that certain newer missions would fairly consistently fail, but with the help of the comments on the various issues raised here all my missions seem to be working again now. You only need another one time edit to make the overrideAA variable available outside VenturePlan, just like the fixes for KnownSpells. If you use this cumulative-fixes branch you no longer have to edit the overrideAA variable directly whenever a new issue is fixed. I have also updated the 'Getting it running' instructions there. ![]() While the original instructions below still work for the most part, I have now implemented all these fixes and fixes for 9.1.5 in my fork of this addon (see the cumulative-fixes branch). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |