That issue is not mine... This is just a work around for players while they work on the fix :) Don't direct the attack to me! :)
'); document.write(''); var yuipath = 'clientscript/yui'; var yuicombopath = ''; var remoteyui = false; } else // Load Rest of YUI remotely (where possible) { var yuipath = 'https://ajax.googleapis.com/ajax/libs/yui/2.9.0/build'; var yuicombopath = ''; var remoteyui = true; if (!yuicombopath) { document.write(''); } } var SESSIONURL = ""; var SECURITYTOKEN = "guest"; var IMGDIR_MISC = "warmane/misc"; var IMGDIR_BUTTON = "warmane/buttons"; var vb_disable_ajax = parseInt("0", 10); var SIMPLEVERSION = "422"; var BBURL = "https://forum.warmane.com"; var LOGGEDIN = 0 > 0 ? true : false; var THIS_SCRIPT = "showthread"; var RELPATH = "showthread.php?p=2583744&t=314204&viewfull=1"; var PATHS = { forum : "", cms : "", blog : "" }; var AJAXBASEURL = "https://forum.warmane.com/"; var CoTTooltips = { rename: true, icons: false, iconsize: 15, qualitycolor: true, overridecolor: { spells: '#839309', items: '', npcs: '#fff', objects: '#fff', quests: '#ffb100', achievements: '#fff' } }; // -->
That issue is not mine... This is just a work around for players while they work on the fix :) Don't direct the attack to me! :)
You mean something like... reading all the posts and information I shared over many posts on this thread, instead of covering your eyes and complaining about "lack of communication" until the communication is gone?
Well,that issue is "ours",which includes all the players,even you. It's obvious that you were suggesting a temporary solution,but next time rephrase it so it won't hinder us,it took almost 4 weeks to get a damn confirmation on Bugtracker,just because they weren't "convinced" .
Sarcasm and irony might look elegant in a discussion,but as we speak the situation stays the same and neither of us posses any valid information regarding the time it will be fixed,we're just supposing it will be fixed soon.
I really appreciate you Obnoxious,for the fact that you were the only one that tried to provide us information, but what most of us expect is a statement from the dev team.
You have your statement already, even explanations about why, which others have accepted and thanked me for since they understood the situation.
If you want to pick and choose who statements come from, get comfortable on your chair.
Thanks for the clarification, and info about the Fel Iron thing. Its a shame it wont be fixed for wrath, but honestly, outside of that, and a few other minor issues, Lord has been great so far.
The bug was reported a month ago and is still "unconfirmed", i doubt it's gonna change any time soon.
Upvoting the bug might help though https://www.warmane.com/bugtracker/report/11236
https://www.warmane.com/bugtracker/r...#comment-14605
Still unconfirmed. Just WOW!
It's allrdy the highest voted issue by far if that doesn't help i don't know what will.
Dont expect this to be fixed any time soon. Northrend content is actually the most important to be fixed.
The only solution for ppl getting through it is to run slave pens and underbog normals and mine fel irons from there. Adamantite can be found in auchindoun dungeons. Find friend/friends who will help u with that.
You can only enter instances so many times, and they have limited veins. We shouldnt have to do this to get a few skill points. Still UNCONFIRMED bugtracker. /facedesk
why to not expect it? Is this like scripting Ulduar or smth?
Because it wasnt fixed during TBC content and is still "unconfirmed" on bugtracker.
Right now they will focus on fixing northrend content, not on fel iron nodes, even if its actually pretty serious bug.
If you do Steamvault in Normal 3-4 times you'll get enough nodes to reach 350 BS and move on to Northrend. It's sad we have to do this, but it's what I did during TBC.