Article View: alt.games.warcraft
Article #351180Re: Quest bugged: Easing into Lumberjacking
From: Peter T.
Date: Sun, 21 Dec 2014 09:11
Date: Sun, 21 Dec 2014 09:11
14 lines
1732 bytes
1732 bytes
Den 21-12-2014 00:14, Urbin skrev: > Does anyone here have an idea on how to solve this? Known bug as you also said. Luckily I got it on the first xrealm invite when I got the quest on an alt while a guildie I was grouped up with couldnt lumber the same tree. He got it when he was invited to another realm though. If you dont know other peeps you can always add me and let me invite you to my realm (darkmoon faire). PeterT#2642. -- Peter T. <https://www.elitedangerous.com/>
Technical Details
Message-ID:
<m762rg$5du$1@speranza.aioe.org>Path:
mbox-mo1.pugleaf.net!s2ni20806lbo.0!nntp.google.com!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mailReferences:
<slrnm9c0mc.bdn.urbin@stinky-local.trash.net>Show Full Headers
Complete Article Headers
X-Received: by 10.194.173.97 with SMTP id bj1mr127364wjc.2.1419153079143; Sun, 21 Dec 2014 01:11:19 -0800 (PST) X-BeenThere: alt.games.warcraft@googlegroups.com Received: by 10.152.42.133 with SMTP id o5ls762399lal.78.gmail; Sun, 21 Dec 2014 01:11:15 -0800 (PST) X-Received: by 10.112.154.232 with SMTP id vr8mr27579lbb.10.1419153075975; Sun, 21 Dec 2014 01:11:15 -0800 (PST) Path: mbox-mo1.pugleaf.net!s2ni20806lbo.0!nntp.google.com!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: "Peter T." <pinoc10@hotmail.cum> Newsgroups: alt.games.warcraft Subject: Re: Quest bugged: Easing into Lumberjacking Date: Sun, 21 Dec 2014 10:11:14 +0100 Organization: Aioe.org NNTP Server Lines: 14 Message-ID: <m762rg$5du$1@speranza.aioe.org> References: <slrnm9c0mc.bdn.urbin@stinky-local.trash.net> NNTP-Posting-Host: pvUGIXhczZBaNE1+jDNPLA.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: ab...@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 X-Antivirus-Status: Clean X-Notice: Filtered by postfilter v. 0.8.2 X-Antivirus: avast! (VPS 141220-1, 20-12-2014), Outbound message Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit