Article View: alt.games.warcraft
Article #351228Passive resource income..
From: Peter T.
Date: Sat, 27 Dec 2014 19:03
Date: Sat, 27 Dec 2014 19:03
11 lines
1712 bytes
1712 bytes
We have this passive resource income at the right side of the door in our castle. My playtime stops in 10 days so I wonder if I should level the rest of my alts to 91 so I get my garrison and also get this income. The biggest sack of resources I've got so far was somewhere around 350ish. Is there a limit how much resources this spot can accumulate or does it keep growing like weed to a max of 10k resources? :) -- Peter T. <https://www.elitedangerous.com/>
Technical Details
Message-ID:
<m7mvp8$7ao$1@speranza.aioe.org>Path:
mbox-mo1.pugleaf.net!s2ni52145lbo.0!nntp.google.com!goblin1!goblin.stu.neva.ru!feeder2.news.elisa.fi!newsfeed3.funet.fi!newsfeeds.funet.fi!newsfeed1.swip.net!aioe.org!.POSTED!not-for-mailShow Full Headers
Complete Article Headers
X-Received: by 10.152.170.201 with SMTP id ao9mr270709lac.5.1419706992152; Sat, 27 Dec 2014 11:03:12 -0800 (PST) X-BeenThere: alt.games.warcraft@googlegroups.com Received: by 10.152.234.169 with SMTP id uf9ls804484lac.75.gmail; Sat, 27 Dec 2014 11:03:09 -0800 (PST) X-Received: by 10.112.137.70 with SMTP id qg6mr3128lbb.14.1419706989443; Sat, 27 Dec 2014 11:03:09 -0800 (PST) Path: mbox-mo1.pugleaf.net!s2ni52145lbo.0!nntp.google.com!goblin1!goblin.stu.neva.ru!feeder2.news.elisa.fi!newsfeed3.funet.fi!newsfeeds.funet.fi!newsfeed1.swip.net!aioe.org!.POSTED!not-for-mail From: "Peter T." <pinoc10@hotmail.cum> Newsgroups: alt.games.warcraft Subject: Passive resource income.. Date: Sat, 27 Dec 2014 20:03:07 +0100 Organization: Aioe.org NNTP Server Lines: 11 Message-ID: <m7mvp8$7ao$1@speranza.aioe.org> 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:31.0) Gecko/20100101 Thunderbird/31.3.0 X-Antivirus-Status: Clean X-Notice: Filtered by postfilter v. 0.8.2 X-Antivirus: avast! (VPS 141227-0, 27-12-2014), Outbound message Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit