Difference between revisions of "Splendid Screen"

From Team Fortress Wiki
Jump to: navigation, search
(This is not a glitch, this is merely how disguises work)
(assuming that the bug is true (not sure, didnt post it, not gonna remove it cuz that seems like more of an admin decision), reworded and fixed grammatical awkwardness and moved the bugs section)
Line 92: Line 92:
 
'''June 29, 2011'''
 
'''June 29, 2011'''
 
* {{item server}} Fire and Blast resistance were reduced by 5%
 
* {{item server}} Fire and Blast resistance were reduced by 5%
 +
 +
== Bugs ==
 +
* If attempting to view a replay in which a player uses the splendid screen, the replay editor won't start and will give an error, saying: GetDynamicBaseline: FindStringIndex(238-CTFWearableDemoShield) has failed.
  
 
== Gallery ==
 
== Gallery ==
Line 104: Line 107:
 
</gallery>
 
</gallery>
  
== Bugs ==
 
* When viewing a replay, if there was a player with the Splendid Screen on the replay,the replay editor won't start and say an error saying GetDynamicBaseline: FindStringIndex(238-CTFWearableDemoShield) has failed.
 
  
 
==See also==
 
==See also==

Revision as of 23:08, 8 July 2011

Time to get bluttered!
The Demoman

The Splendid Screen is a secondary weapon for the Demoman. It is an iron shield with four knobs in the cardinal directions, and a large boss in the middle.

Compared to the Chargin' Targe, this weapon provides 60% less fire resistance, and 62.5% less explosive resistance. However, its charge ability is more potent; there is no minimum distance required to deliver damage with a shield bash, and a successful charge bash delivers 70% more damage.

Damage

See also: Damage

Alternate fire initiates a charge attack, which deals damage on its own, or may be used in conjunction with another weapon.

  • Charge Damage: 85 (if shield connects with enemy) + 17 per head (up to 5 heads).
    • The shield damage is affected by weapon damage spread, it is not a constant number.
  • Charge Speed: 750 Hammer units/sec (Approximately 2.5 times faster than 'Base' Speed).
    • Charge Speed: 638 Hammer units/sec with Scotsman's Skullcutter equipped (Approximately 2.1 times faster than 'Base' Speed).

Function times

  • Charge Interval: 12 seconds

Times are approximate and determined by community testing.

Item set

Main article: Item sets
One Thousand and One Demoknights
Item icon Timbuk-Tuesday Bundle.png
Effect

No effect

Crafting

See also: Crafting

Blueprint

Reclaimed Metal Chargin' Targe Splendid Screen
Item icon Reclaimed Metal.pngx2 + Item icon Chargin' Targe.png = Item icon Splendid Screen.png
Class Token - Demoman Slot Token - Primary Scrap Metal Possible Results
Item icon Class Token - Demoman.png + Item icon Slot Token - Primary.png + Item icon Scrap Metal.png =
Item icon Loch-n-Load.png Item icon Ali Baba's Wee Booties.png Item icon Bootlegger.png Item icon Loose Cannon.png
Item icon B.A.S.E. Jumper.png Item icon Iron Bomber.png

As a Crafting Ingredient

Refined Metal Splendid Screen Sultan's Ceremonial
Item icon Refined Metal.pngx4 + Item icon Splendid Screen.png = Item icon Sultan's Ceremonial.png

Styles

Main article: Styles

The Splendid Screen's appearance can differ through the use of styles. This, however, has no bearing on the kill icon or client view.

Styles
Splendid Screen.PNG Splendid Screen with spike.png Splendid Screen with arrow.png Splendid Screen with arrow and spike.png
Classic Spike Arrow Spike & Arrow

Update history

June 23, 2011 Patch (Über Update)

  • The Splendid Screen was added to the game.

June 27, 2011 Patch

  • Added the Splendid Screen to the whitelist for Medieval mode

June 28, 2011 Patch

  • Fixed a bug where Demomen kept their leftover charge amount when self-aborting charges (you'll still keep leftovers when stopped by enemy airblasts)

June 29, 2011

  • [Item schema update] Fire and Blast resistance were reduced by 5%

Bugs

  • If attempting to view a replay in which a player uses the splendid screen, the replay editor won't start and will give an error, saying: GetDynamicBaseline: FindStringIndex(238-CTFWearableDemoShield) has failed.

Gallery


See also