Talk:Crasher

How giants status is achieved

I've decompiled the map and here are my results: When you pick up the intel, multiples "trigger_add_or_remove_tf_player_attribute" brushs are enabled and affect only the carrier. Here a list of all attributes given, with 9999 secs duration:

• +%s1 max health on wearer. There are multiple of those to accommodate for the different classes, but it's always 20 times the stardard max health (items may influences that)
• Cannot be backstabbed 1
• Wearer never takes falling damage 1
• patient overheal penalty 0
•  %s1% reduction in push force taken from damage 0.25
• Attrib_AirBlastVulnerabilityMultipier 0.25
• reduced_healing_from_medics 0.25
•  %s1% slower move speed on wearer 0.75
• TF_COND_CRITBOOSTED_USER_BUFF. Gives the condition 34, which is crit boost from pumpkin
• voice pitch scale 0.75
•  %s1% health from packs on wearer 0.1
• No description 7 . To make all these changes invisible while inspecting the carrier

In addition, there is a "trigger_stun" that activates only for Medics carrier, to not let them match the speed of their healing target. And Giants can't do moving taunts. ~Azsofe (talk) 20:58, 7 October 2022 (UTC)

Could you provide a picture of this.
GrampaSwood (talk) 21:04, 7 October 2022 (UTC)

Hammer 1 Hammer 2 Hammer 3~Azsofe (talk) 21:19, 7 October 2022 (UTC)

Bug, exploit, or balance factor?

Last night, I played Crasher again.

At least twice, the other team had two giants active at the same time. This was when we were near or inside the viaduct. Seems like a Bug. Or an Exploit, with two players standing on the Intel spawn point, waiting to catch the Intel the instant it respawns. We were kicking their butts, so I don't know if it was a balancing mechanic. I don't know if both of the simultaneous giants were full HP giants, as both times we defeated both giants as we Capped the point.

M I K A D O 282 ⊙⊙⊙⊙⊙⊙ ⊙⊙ ⊙⊙ (Contact Mikado282 (SM)) | (contribs) (Help Wanted!) 20:59, 9 October 2022 (UTC)

this is a bug. we've (hopefully) fixed it and are waiting on valve to release a patch. Pont (talk) 00:30, 10 October 2022 (UTC)

Yeah, today, I saw the other side repeatedly spawm two giants at the same time. The last time, they had three giants at the same time! (I still capped the point, anyway.)

It would be interesting to know how they did it.

M I K A D O 282 🎃🎃🎃🎃🎃🎃 🎃🎃 🎃🎃 (Contact Mikado282 (SM)) | (contribs) (Help Wanted!) 20:06, 16 October 2022 (UTC)

One of the map authors said it's an issue with point_hurt, which were changed in the last 2 patches. This is not something on their end and something that Valve has to fix it, once they fix it, it shouldn't happen anymore. I can't link where this information comes from because I don't want people exploiting this bug, as the page that has this info also has an explanation on how to do the exploit by someone else. - ▪ - 20:15, 16 October 2022 (UTC)

I knew that as I asked it.

My real point is that it is still happening, and it is notable (and as bugs goes, hugely notable), and the wiki shouldn't be silent on it, even if we don't say how it is done. I'm pollyannaish enough to think some people look to this wiki for information on current events.

It is big question to me how this didn't seem map-breaking, as the teams I have seen doubling or tripling their giants lost their matches, maybe because the exploiters weren't pressing any advantage. (Again, not the wiki's job). If this isn't griefing the enemy, it is griefing your own team.

On another note, I understand the staff logic of moving the Ghoulpit bug to ConTracker#Bugs, but the non-editor user probably would not think to look anywhere on the wiki to see what is wrong with Ghoulpit than the Ghoulpit page, even if there was only a hatnote saying that the serious bug is covered on another page. I'm about to play Ghoulpit and wanted to know if the bug had been fixed, but I had to use my editor skills, not simple reading, to figure that the topic had been moved, not ignored.

M I K A D O 282 🎃🎃🎃🎃🎃🎃 🎃🎃 🎃🎃 (Contact Mikado282 (SM)) | (contribs) (Help Wanted!) 23:41, 16 October 2022 (UTC)

just popping in here to note that the oct 18th patch finally fixed the issue. we had a lot of trouble reliably killing off giants and had asked valve to add an option for point_hurt to ignore ubercharge, which they did - but only when the point_hurt was set to damage everything within a radius, and not when it was configured to damage a specific target through IO. i don't know why it took them a week to ship this, considering how broken it's been and how it led to out-of-bounds exploits. delfy's video certainly didn't help. it's been a bit of a frustrating time.

Pont (talk) 12:59, 19 October 2022 (UTC)