Brynne Fair Mine Shafts: Difference between revisions

From Twilight Heroes Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 33: Line 33:
|items=[[uncut diamond]], [[uncut emerald]], [[uncut ruby]], [[uncut sapphire]]|chips=|EL=|HP=|exp=350}}
|items=[[uncut diamond]], [[uncut emerald]], [[uncut ruby]], [[uncut sapphire]]|chips=|EL=|HP=|exp=350}}


[[Category:Locations]]
==Notes==
==Notes==
* Foes in this area had an odd resistance/weakness behavior where they would inherit the weakness (and sometimes the resistance) of the last foe fought. Later [[Ryme]] [http://www.twilightheroes.com/forums/viewtopic.php?f=2&t=437&p=13910#p13910 said] this was a bug, and the behavior was not witnessed in the next area to open.
* Foes in this area had an odd resistance/weakness behavior where they would inherit the weakness (and sometimes the resistance) of the last foe fought. Later [[Ryme]] [http://www.twilightheroes.com/forums/viewtopic.php?f=2&t=437&p=13910#p13910 said] this was a bug, and the behavior was not witnessed in the next area to open.

Latest revision as of 23:52, 27 October 2009

Brynne Fair Mine Shafts
Location: Sunset Strip Mine
Unlocks: 18th-21st 2009
Combat %: 100
Foe XP range: unspecified
ID: unknown

Adventuring here after Yes, Even Further Down the Rabbit Hole results in:

This part of the mine has already been cleared. You'll have to delve deeper to find foes to fight.

Combat Adventures

skreel

Item Drops: uncut emerald, uncut ruby, uncut sapphire


Experience Gained: 350




rockupine

Item Drops: uncut emerald, uncut ruby, uncut sapphire, sweet lichen


Experience Gained: 350




inverted shadow

Item Drops: uncut diamond, uncut emerald, uncut ruby, uncut sapphire


Experience Gained: 350




rotaviola

Item Drops: uncut diamond, uncut emerald, uncut ruby, uncut sapphire


Experience Gained: 350




Notes

  • Foes in this area had an odd resistance/weakness behavior where they would inherit the weakness (and sometimes the resistance) of the last foe fought. Later Ryme said this was a bug, and the behavior was not witnessed in the next area to open.