Saradomin team cape

Saradomin team cape
Release7 March 2005 (Update)
MembersYes
Quest itemNo
Properties
TradeableNo
EquipableYes
StackableNo
DisassemblyNo
DestroyDrop
ExamineA Castle Wars cape in Saradomin blue.
Options [?]
BackpackWear
Values
Value100 coins
AlchemyNot alchemisable
On deathAlways kept outside dangerous area
Weight0.453 kg
Advanced data
Item ID4514
LinksMRID • recipe
[view][talk]

A Saradomin team cape can be bought from Lanthus at the minigame Castle Wars for 10 silver Castle Wars tickets. The blue cloak represents the god Saradomin, and had the same appearance as the cape players wear during a Castle Wars game when playing on the Saradomin team before being graphically improved. This cape, like all other Castle Wars achievement capes, can be stored in the costume room of a player-owned house.

The Saradomin team cape should not be confused with the Saradomin cape. Bandits will not attack players who wear this cape. Visually, the difference is that the Saradomin cape is a darker blue and has a yellowish-white trim.

Combat stats

edit
Requirements
None
Class
None
Slot
TierType
NoneCosmetic
Saradomin team cape equipped.png: Saradomin team cape equipped by a player
Style attributes
 
Damage0.00.00.00.0
Accuracy0000
Defensive attributes
 Armour0.0Reduction
 LP0PvM0%
 Prayer0PvP0%

Shop locations

edit

Update history

edit
This information has been compiled as part of the update history project. Some updates may not be included – see here for how to help out!

Trivia

edit
  • There was a major glitch when non-member players were getting the capes, by taking a ride on the gnomecopters to Castle Wars and reading the signpost. Then they would go to the next floor, click on the ground then select "report abuse", allowing them to enter. This would end in players being muted for 24 hours.
  • At one point, there was a glitch with this cloak and the Zamorak team cape. The hood and parts of the cloak itself appear to change colour based on what top your character is wearing when no armour is equipped. This glitch has effectively been resolved.