Dont spend your VPs on your brandnew ilvl 600 epic cloak

Article View: alt.games.warcraft

Article #349664

Back to alt.games.warcraft Previous Next

#349664

From: Peter T.
Date: Fri, 29 Nov 2013 10:17

10 lines
1485 bytes

My alt got his epic ilvl 600 cloak a few days ago.  I decided _not_ to 
spend 500 VPs for the upgrade as the legendary cloak was just around the 
corner.  That was a wise decision.  When I transformed the cloak to 
Legendary 10 mins ago it also included 2 free upgrades to ilvl 608.  So 
save your VPs. :)

-- 
Peter T.

<https://elite.frontier.co.uk/>

Technical Details

Message-ID: <l79pk4$t9p$1@speranza.aioe.org>

Path:

mbox-mo1.pugleaf.net!hj15ni1076wib.0!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.130.MISMATCH!xlned.com!feeder1.xlned.com!feed.xsnews.nl!border02.ams.xsnews.nl!feeder.de.xennanews.com!border-2.de.xennanews.com!news.roellig-ltd.de!news.mb-net.net!open-news-network.org!aioe.org!.POSTED!not-for-mail

Show Full Headers

Complete Article Headers

X-Received: by 10.14.179.134 with SMTP id h6mr1352743eem.7.1386080863112;        Tue, 03 Dec 2013 06:27:43 -0800 (PST)
Path: mbox-mo1.pugleaf.net!hj15ni1076wib.0!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.130.MISMATCH!xlned.com!feeder1.xlned.com!feed.xsnews.nl!border02.ams.xsnews.nl!feeder.de.xennanews.com!border-2.de.xennanews.com!news.roellig-ltd.de!news.mb-net.net!open-news-network.org!aioe.org!.POSTED!not-for-mail
From: "Peter T." <pinoc10@hotmail.cum>
Newsgroups: alt.games.warcraft
Subject: Dont spend your VPs on your brandnew ilvl 600 epic cloak
Date: Fri, 29 Nov 2013 11:17:41 +0100
Organization: Aioe.org NNTP Server
Lines: 10
Message-ID: <l79pk4$t9p$1@speranza.aioe.org>
NNTP-Posting-Host: qoi5KAMYsHu4c26JwxJRBg.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.1.1
X-Antivirus-Status: Clean
X-Notice: Filtered by postfilter v. 0.8.2
X-Antivirus: avast! (VPS 131128-1, 28-11-2013), Outbound message
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit