Difference between revisions of "Melissa's Cloak"
(Reworded a bit.) |
|||
Line 1: | Line 1: | ||
[[Image:Melissa's_Cloak.png|frame]] | [[Image:Melissa's_Cloak.png|frame]] | ||
+ | '''Melissa's Cloak''' is the only cloak with the [[property]] of additional [[durability]]. It has +5% fire [[resistances|resistance]] but cannot be [[enhanced]]. It can be [[blessed]] using a [[Clothing Bless Deed]], and can also be [[Dying Tub|dyed]]. The cloak will lose durability as any other piece of equipment and can be repaired. However [[Powder of Fortifying]] can not be used on it. | ||
− | + | It was obtained by fighting [[Melissa the Mage|Melissa the Servant of Nosfentor]] at the end of the [[Royal Council Massacre]] investigation and dropped into the backpack of anyone who got looting rights. | |
− | + | A bug initally existed in which the cloak erroneously behaved like [[Powder of Fortification]]. Double-clicking the cloak brought up a target cursor and asked which item to fortify. The target would gain 10 durability and the cloak would be destroyed. This bug was fixed in the update following [[Publish 54]]. | |
− | + | ||
− | + | ||
[[Category:Artifacts (Other)]][[Category:Cloaks]] | [[Category:Artifacts (Other)]][[Category:Cloaks]] |
Revision as of 14:36, 13 August 2008
Melissa's Cloak is the only cloak with the property of additional durability. It has +5% fire resistance but cannot be enhanced. It can be blessed using a Clothing Bless Deed, and can also be dyed. The cloak will lose durability as any other piece of equipment and can be repaired. However Powder of Fortifying can not be used on it.
It was obtained by fighting Melissa the Servant of Nosfentor at the end of the Royal Council Massacre investigation and dropped into the backpack of anyone who got looting rights.
A bug initally existed in which the cloak erroneously behaved like Powder of Fortification. Double-clicking the cloak brought up a target cursor and asked which item to fortify. The target would gain 10 durability and the cloak would be destroyed. This bug was fixed in the update following Publish 54.