Difference between revisions of "Template talk:Damage table"
GrampaSwood (talk | contribs) (→Holster/deploy speed: new section) |
BrazilianNut (talk | contribs) (→Option to remove "See also: Damage": new section) |
||
(7 intermediate revisions by 2 users not shown) | |||
Line 90: | Line 90: | ||
The only thing that would have to be special about it is maybe having a tooltip on the holster one that says something similar to "Holster speed is the speed at which the next weapon is being deployed". The only issue with that is that the [[Thermal Thruster]] is unique because it is the only weapon with an actual holster animation.<br>[[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 17:13, 7 July 2022 (UTC) | The only thing that would have to be special about it is maybe having a tooltip on the holster one that says something similar to "Holster speed is the speed at which the next weapon is being deployed". The only issue with that is that the [[Thermal Thruster]] is unique because it is the only weapon with an actual holster animation.<br>[[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 17:13, 7 July 2022 (UTC) | ||
+ | |||
+ | :The list of weapons with a holster/deploy stat: [[Degreaser]], [[Atomizer]], [[Thermal Thruster]], [[Weapons#demomelee|any Demo sword]], [[Ullapool Caber]], [[Gloves of Running Urgently]], [[Fists of Steel]], [[Reserve Shooter]], and [[Panic Attack]].<br>[[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 17:21, 7 July 2022 (UTC) | ||
+ | |||
+ | :{{Pro}} I agree on adding an additional parameter that states the deploy speed of the weapon. However, this new stat would only really benefit a niche group of players within the TF2 community, and that niche being the ones in the competitive landscape, since the deploy speed of any weapon can affect the strategy of a team during the match, or in other scenarios the deploy speed that be a turnover for one of the teams, in my opinion. | ||
+ | |||
+ | :Regarding how to measure the deploy speed, I have two thoughts, either we can: | ||
+ | |||
+ | :* Use the stock/default weapons' deploy speed as base variable and compare it to the weapon in question. | ||
+ | :** For example, (and I'm using fake numbers, just for demonstration purposes) if it takes 0.2 second to deploy the [[Shotgun]], and the article is about the [[Flare Gun]], we state something like "The Flare gun is deployed 40% faster than the :shotgun". | ||
+ | |||
+ | :* Or just measure like any other stat and use actual seconds it takes as measurement, without comparing it to any weapon. | ||
+ | |||
+ | :[[User:Yossef|Yossef]] | ''[[User talk:Yossef|Talk]]'' | ''[[Special:Contributions/Yossef|Contributions]]'' 18:14, 7 July 2022 (UTC) | ||
+ | |||
+ | :: I think it also benefits the general userbase, as seeing "50% faster deploy speed" without any reference for the base speed makes it basically just guess guess work. Deploy speed of a weapon doesn't matter in competitive at all, it's just a good stat to have similar to reload time of a weapon or a firerate. Also, it would just simply be the time it takes in seconds. For most it would just be the usual 0.5 seconds.<br>[[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 18:18, 7 July 2022 (UTC) | ||
+ | ::: Regarding the "compared measurement proposal", we can use a toolnip that explains to which stock item is that weapon being compared to, of course it'll be with the respective weapon category (Primary, Secondary, Melee), so users won't have to guess if they see "50% faster deploy speed". Regardless, having the detailed time in seconds would also work. [[User:Yossef|Yossef]] | ''[[User talk:Yossef|Talk]]'' | ''[[Special:Contributions/Yossef|Contributions]]'' 18:32, 7 July 2022 (UTC) | ||
+ | |||
+ | == Option to remove "See also: Damage" == | ||
+ | |||
+ | The articles for multi-class weapons use this table more than once in case their stats change for one or more classes, and everytime the "''See also: Damage''" is there. | ||
+ | |||
+ | I've noticed it's related to the<code>damage</code> parameter; however, removing it removes not just the See also, but several of the table's lines as well. | ||
+ | |||
+ | Would it be possible to add an option to remove the "''See also: Damage''", similar to how {{tl|Set}} has an option to remove "''Main article: Item sets''"? - [[User:BrazilianNut|BrazilianNut]] ([[User talk:BrazilianNut|talk]]) 09:08, 22 September 2023 (UTC) |
Latest revision as of 09:08, 22 September 2023
Contents
- 1 DPS
- 2 Trumpeting time
- 3 Using non-integers
- 4 Non-damage related values
- 5 Rehit rate/damage interval
- 6 Attack interval (ru)
- 7 Random Critical Type
- 8 flame particle maximum distance
- 9 Charge Damage
- 10 Many entries of the same language
- 11 Are damage tables...broken?
- 12 Recharge parameter broken
- 13 Effect range section broken
- 14 Holster/deploy speed
- 15 Option to remove "See also: Damage"
DPS
On this page uses this notion. I think need add it. — The preceding unsigned comment was added by Nik9990 (talk) • (contribs)
- For now, you should use a tooltip for DPS values. For an example, see Syringe Gun. — nVis 16:30, 6 March 2011 (UTC)
I think that DPS on a tooltip, the way it is today, is not readily visible, and it's not dictated by the template, creating fragmentation. In my opinion we should add DPS as another column, as doubling the number of rows for this purpose would be too much. --Marcotulio (talk) 16:24, 17 March 2014 (PDT)
Trumpeting time
Parameter is missing. "Trumpeting Time" for Battalion's Backup and Buff Banner. --Nik9990 Talk | Cont 19:58, 6 March 2011 (UTC)
- Done
activation time
— nVis 09:27, 7 March 2011 (UTC)
Using non-integers
Would it be more accurate to state damages as real numbers? Degreaser afterburn is 2.25 per tick, Fan O' War has a base of 3.5, Powerjack has a base of 81.25, and so on. Toomai Glittershine 14:51, 11 March 2011 (UTC)
Would it be possible to add parameters for other aspects of weapons, such as the self-damage reduction for the Gunboats; the fire and explosive resistance, and charge length for the Chargin' Targe and Splendid Screen? TheChrisD Rants•Edits 00:38, 22 June 2011 (UTC)
Rehit rate/damage interval
Something should be added to accomodate for the Righteous Bison's rehit rate. Toomai Glittershine 09:32, 25 July 2011 (PDT)
Attack interval (ru)
Attack interval в русской версии: Интервал атаки
Может правильнее Интервал между атаками? [RUS] ANGEL_UNDEAD 12:56, 25 September 2011 (PDT)
Random Critical Type
It'd be great if there was a way to see what kind of random crit a weapon did, be it rapid-fire, single-shot, or none.Darkychao (talk) 19:45, 1 July 2014 (PDT)
flame particle maximum distance
just tested it along 2 axes, and the very edge of the reach is 330hu, not 384 as the damage table's tooltip states. Isildur4 (talk) 12:28, 9 September 2014 (PDT)
Charge Damage
I plan to add Charge Damage, Mini-crit charge damage, and Charge Speed. This will be for the Demoman's shields. Tell me if any are too similar to another already in existence. I can add them once an OK is set. DC64 (talk) 13:06, 17 December 2014 (PST)
Many entries of the same language
"metal cost repairing"
ja = 修理の消費メタル ja = 修理コスト
"drop expiry"
fr = Durée de disparition de l'objet jetté fr = Expiration de l'objet jeté
"zoom headshot delay"
pt-br = Atraso de headshot com zoom pt-br = Delay de headshot de zoom
"aim fatigue"
pt-br = Cansaço de mira pt-br = Fadiga da mira
Funandjoy (talk) 15:20, 12 December 2015 (PST)
Are damage tables...broken?
Right now, every damage table I see has white spaces instead of the normal information. For example, on Sandvich, this is what I see:
I know it looks like some terrible MS Paint editing, but I swear, I didn't alter the photo other than crop it.
This has only started happening recently, maybe at the same time as the Internal Error shenanigan, though I'm not sure if both are related. Anyar (talk) 18:48, 24 February 2017 (PST)
- Probably my fault, I made an update to the template and I guess it wasn't tested thoroughly enough. Darkid « Talk — Contribs » 20:26, 24 February 2017 (PST)
- Still not completely fixed. The white bars are gone, but for some tables like the one for the Frontier Justice, the formatting is off. Anyar (talk) 17:03, 25 February 2017 (PST)
Recharge parameter broken
For Razorback, Jarate, and more, the "recharge" parameter that is used and is also included in the documentation does not show up in the actual table. I do not know how to fix this. ⇒ Anyar (talk/contributions/giveaway) 17:10, 20 October 2017 (PDT)
Effect range section broken
The effect range stat is broken: it shows up to the right of the table (as seen on Battalion's Backup). Can someone please fix it ? I've tried, without success :/ Azsofe (talk) 13:56, 25 March 2019 (UTC)
Holster/deploy speed
Some weapons have a slower/faster deploy/holster speed than other weapons, however this is something that more than 1 weapon shares. On Common weapon mechanics (a now-deleted page), someone felt the need to add the default switch speed and add some of the values for other weapons. I think it would add quite a lot of value to weapon pages if there was a deploy/holster parameter.
The only thing that would have to be special about it is maybe having a tooltip on the holster one that says something similar to "Holster speed is the speed at which the next weapon is being deployed". The only issue with that is that the Thermal Thruster is unique because it is the only weapon with an actual holster animation.
GrampaSwood (talk) 17:13, 7 July 2022 (UTC)
- The list of weapons with a holster/deploy stat: Degreaser, Atomizer, Thermal Thruster, any Demo sword, Ullapool Caber, Gloves of Running Urgently, Fists of Steel, Reserve Shooter, and Panic Attack.
GrampaSwood (talk) 17:21, 7 July 2022 (UTC)
- I agree on adding an additional parameter that states the deploy speed of the weapon. However, this new stat would only really benefit a niche group of players within the TF2 community, and that niche being the ones in the competitive landscape, since the deploy speed of any weapon can affect the strategy of a team during the match, or in other scenarios the deploy speed that be a turnover for one of the teams, in my opinion.
- Regarding how to measure the deploy speed, I have two thoughts, either we can:
- Use the stock/default weapons' deploy speed as base variable and compare it to the weapon in question.
- Or just measure like any other stat and use actual seconds it takes as measurement, without comparing it to any weapon.
- Yossef | Talk | Contributions 18:14, 7 July 2022 (UTC)
- I think it also benefits the general userbase, as seeing "50% faster deploy speed" without any reference for the base speed makes it basically just guess guess work. Deploy speed of a weapon doesn't matter in competitive at all, it's just a good stat to have similar to reload time of a weapon or a firerate. Also, it would just simply be the time it takes in seconds. For most it would just be the usual 0.5 seconds.
GrampaSwood (talk) 18:18, 7 July 2022 (UTC)- Regarding the "compared measurement proposal", we can use a toolnip that explains to which stock item is that weapon being compared to, of course it'll be with the respective weapon category (Primary, Secondary, Melee), so users won't have to guess if they see "50% faster deploy speed". Regardless, having the detailed time in seconds would also work. Yossef | Talk | Contributions 18:32, 7 July 2022 (UTC)
- I think it also benefits the general userbase, as seeing "50% faster deploy speed" without any reference for the base speed makes it basically just guess guess work. Deploy speed of a weapon doesn't matter in competitive at all, it's just a good stat to have similar to reload time of a weapon or a firerate. Also, it would just simply be the time it takes in seconds. For most it would just be the usual 0.5 seconds.
Option to remove "See also: Damage"
The articles for multi-class weapons use this table more than once in case their stats change for one or more classes, and everytime the "See also: Damage" is there.
I've noticed it's related to thedamage
parameter; however, removing it removes not just the See also, but several of the table's lines as well.
Would it be possible to add an option to remove the "See also: Damage", similar to how {{Set}}
has an option to remove "Main article: Item sets"? - BrazilianNut (talk) 09:08, 22 September 2023 (UTC)