Difference between revisions of "Talk:Buffalo Steak Sandvich"
(→Damnit) |
GrampaSwood (talk | contribs) m (→Damage vuln. bug) |
||
| (31 intermediate revisions by 17 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | {{Talk archive |
| + | | arc1name = Archive 1 | ||
| + | | arc1link = Talk:Buffalo Steak Sandvich/Archive 1 | ||
| + | }} | ||
| − | + | == Damage vuln. bug == | |
| − | |||
| − | + | The fact it doesn't stack with crits or mini-crits may be intentional. This is due to the fact it used to mark you for death, and changing it to a vuln. was a buff, but if it did stack with mini-crits then the situations where someone has guaranteed mini-crits (example being the buff banner) then you would end up taking MORE damage than the previous version, making it not a direct buff. [[User:Cheezcracker|Cheezcracker]] ([[User talk:Cheezcracker|talk]]) 20:19, 19 February 2024 (UTC) | |
| − | |||
| − | |||
| − | |||
| − | + | :Having damage vulnerability increase the damage of (Mini-)Crits is expected behaviour. I can't find anything in the code about exceptions either, if you find anything about it then I think we can reasonably call it intentional.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] {{!}} [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] {{!}} [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 20:37, 19 February 2024 (UTC) | |
| − | + | ::I am confused, clearly there is code for an exception or else the "bug" would not exist. [[User:Cheezcracker|Cheezcracker]] ([[User talk:Cheezcracker|talk]]) 21:32, 19 February 2024 (UTC) | |
| − | |||
| − | |||
| − | |||
| − | + | :::If it's a bug, then there wouldn't be code for it. I can't find any code for it, but if you do then feel free to reference it here following [[Team Fortress Wiki:Policies#Leaked content|leaked content policy]].<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] {{!}} [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] {{!}} [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 21:45, 19 February 2024 (UTC) | |
| − | + | ||
| − | + | ::::From what I can tell, there is no universal way to code vulnerabilities and resistances. Sometimes a vuln is just a resistance with a negative value (the pain train), sometimes they scale with ramp up and fall off differently (battalion's backup), and sometimes they just don't happen (the steak), so saying the steak is an exception to some sort of established method seems misleading. [[User:Cheezcracker|Cheezcracker]] ([[User talk:Cheezcracker|talk]]) 15:34, 20 February 2024 (UTC) | |
| − | :: | + | |
| + | :::::I have no idea what you mean. I just said if you have some kind of proof that this is intentional then provide it, otherwise it's a bug. Even if the Pain Train is coded that way, any bugs that result from this (e.g. the [[Enforcer]] not doing extra damage to the [[Pain Train]] because it bypasses this resistance) are still listed as bugs.<br>[[File:BLU Wiki Cap.png|20px|link=List of Wiki Cap owners]] {{!}} [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] {{!}} [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] [[File:PraisetheSun.png|20px|alt=Praise the Sun!]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) ([[Special:Contributions/GrampaSwood|<font color="DB9C1F">contribs</font>]]) 15:47, 20 February 2024 (UTC) | ||
Latest revision as of 15:47, 20 February 2024
| Talk archives | |
|
Archive 1 |
Damage vuln. bug
The fact it doesn't stack with crits or mini-crits may be intentional. This is due to the fact it used to mark you for death, and changing it to a vuln. was a buff, but if it did stack with mini-crits then the situations where someone has guaranteed mini-crits (example being the buff banner) then you would end up taking MORE damage than the previous version, making it not a direct buff. Cheezcracker (talk) 20:19, 19 February 2024 (UTC)
- Having damage vulnerability increase the damage of (Mini-)Crits is expected behaviour. I can't find anything in the code about exceptions either, if you find anything about it then I think we can reasonably call it intentional.
| s | GrampaSwood 
(talk) (contribs) 20:37, 19 February 2024 (UTC)
- I am confused, clearly there is code for an exception or else the "bug" would not exist. Cheezcracker (talk) 21:32, 19 February 2024 (UTC)
- If it's a bug, then there wouldn't be code for it. I can't find any code for it, but if you do then feel free to reference it here following leaked content policy. | s | GrampaSwood (talk) (contribs) 21:45, 19 February 2024 (UTC)
- If it's a bug, then there wouldn't be code for it. I can't find any code for it, but if you do then feel free to reference it here following leaked content policy.
- From what I can tell, there is no universal way to code vulnerabilities and resistances. Sometimes a vuln is just a resistance with a negative value (the pain train), sometimes they scale with ramp up and fall off differently (battalion's backup), and sometimes they just don't happen (the steak), so saying the steak is an exception to some sort of established method seems misleading. Cheezcracker (talk) 15:34, 20 February 2024 (UTC)
- I have no idea what you mean. I just said if you have some kind of proof that this is intentional then provide it, otherwise it's a bug. Even if the Pain Train is coded that way, any bugs that result from this (e.g. the Enforcer not doing extra damage to the Pain Train because it bypasses this resistance) are still listed as bugs. | s | GrampaSwood (talk) (contribs) 15:47, 20 February 2024 (UTC)
- I have no idea what you mean. I just said if you have some kind of proof that this is intentional then provide it, otherwise it's a bug. Even if the Pain Train is coded that way, any bugs that result from this (e.g. the Enforcer not doing extra damage to the Pain Train because it bypasses this resistance) are still listed as bugs.
