Article View: alt.games.diablo
Article #368Re: Damn Goat Shrines!
From: jcon... John Conklin II
Date: Tue, 28 Jan 1997 00:00
Date: Tue, 28 Jan 1997 00:00
33 lines
1808 bytes
1808 bytes
The tactic I use, which purists may consider cheating, but "Oh well!" is to save the game just before using the shrine or pool; as all this stuff is generated when the dungeon is created, and will stay that way no matter what until you restart a new game, you save, look over your spells and Inventory, close them, bring up the Character screen, tough the pool/shrine and keep an eye on all the info in the Char. window. If anything goes down that you don't want to go down or can't live with losing just yet, you reload the game and don't touch that pool/shrine until/if you want. John. On 23 Jan 1997 22:52:51 -0600, all...@Starbase.NeoSoft.COM (Allen) wrote: > >So I started a local IPX multiplayer game for my level 18 Warrior (with >maxed out Magic and tons of spells) to travel through solo, building up >stats before tackling the Caves and Hell. I encountered several Goat >Shrines. The first four Goats Shrines ALL LOWERED MY MANA PERMANENTLY! >This really pissed me off. My mana went from 71 to 55, always with >messages like "Intensity comes at the cost of wisdom". Has anybody else >encountered such Goat Shrines that all do the same thing? After that, I >was afraid to try any more Goat Shrines that I encountered. I can't >afford to lose any more Mana, and I don't know of any Shrines that will >increase it back up. > >Other than that, its a great game... > >Later... "BluesBoy" Allen >
Technical Details
Message-ID:
<32ed5559.8625125@nntp.best.com>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<5c9f73$gn@Starbase.NeoSoft.COM>Show Full Headers
Complete Article Headers
From: jcon...@best.com (John Conklin II) Subject: Re: Damn Goat Shrines! Date: 1997/01/28 Message-ID: <32ed5559.8625125@nntp.best.com> X-Deja-AN: 212733046 references: <5c9f73$gn@Starbase.NeoSoft.COM> newsgroups: alt.games.diablo,comp.sys.ibm.pc.games.rpg MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit