:))) you are kidding but thats ok.
I am not kidding at all. It makes for a much more enjoyable gaming experience for the majority of players, which outweights a minority taking advantage of it.
Vast majority of the players won’t encounter and/or fully understand this guard behaviour, let alone take advantage of it. But it does provide them with the opportunity to do some cool sniper kills from a distance without immediately going into combat and getting gunned down.
Just want to re-affirm the truth of this post from the perspective of a mediocre Joe Schmoe Hitman player who doesn’t speedrun or use exploits. This was a very welcome solution to the Colorado problem, for me.
It wouldn’t be a proper Hitman game without batshit insane bugs and exploits.
2 & 3 aren’t really glitches. Both are just really particular AI behaviours that can be abused in a variety of ways. But that’s what Hitman is all about, so I don’t think they should necessarily be fixed (though 3 could be rebalanced a bit). You can always choose not to use them.
Better question is why fix these things that a player can take advantage of (and have fun with) and not the serious bugs (like 4, which happens in way more maps than those two).
EDIT: to explain 2 a bit - 2 is supposed to only be possible in a guard disguise. The idea is if an NPC sees a weapon and goes to report it, then shortly after they see you as a guard carrying that same weapon, they will stop reporting it and tell you off. Theoretically it shouldn’t be possible to do it while not in a guard disguise, as being seen with a weapon would usually get you spotted and override that behaviour with crime noticed behaviour, but if you’re able to only get seen a little bit, while not getting ‘spotted’, the behaviour still kicks in without being overridden, and they still follow you to tell you off…
Another point of interest is that if you change disguise while they follow, they will stop following you and instead go to the disguise you left rather than you… suggesting that the NPC’s are somewhat coded to associate it with the disguise and not 47 specifically.
The 3rd one is absolutely a glitch, No doubt about that. But your explains about the 2nd one is correct. If this feature was only applicable when you are disguised as a guard, it would have been a good feature of course, because they follow you and tell you not to leave your weapon on the ground which makes sense. But when it happens even when you are not disguised as a guard, it becomes a glitch, and its a powerful one indeed
Nah, 3 is not a glitch. It’s the “Sniper Shot Location” mechanic which has worked like that since IOI patched it in a February Hitman 2 patch: HITMAN 2 – February Update - IO Interactive
And also updated again in a March patch: HITMAN 2 – March Update - IO Interactive
I know the story and history, and i know your point, but i don’t understand how do you wanna describe the videos i attached saying its not a glitch. You are carrying a gun in your hand in hostile area and passing guards and they just ignore you.
PS: i’m watching your videos on YouTube right now, just found your channel, they are beautiful…
IOI’s goal for WoA was basically a modern Blood Money. If you’ve seen any speed runs of that, you’ll already know how crazy that can get. 47 can be chased around the map by guards riddling him with bullets and still exit with silent assassin. There’s nothing more ‘Hitman’ than bending the rules of silent assassin. Guard panic opens up the game and allows way more creativity and freedom when doing self-imposed challenges, but also doesn’t really stand in the way of those who enjoy a more traditional stealth game experience. It seems like WoA at its most Blood Money to me.
I didn’t read all the posts above me, mostly just the first one, so if I repeat some points of others I apologize.
The following is from the point of view of a Hitman 3 speedrunner as well as leaderboard moderator for Hitman 3 on speedrun.com. I wrote all the rules for Hitman 3 on speedrun.com, with community input. I’m not an admin for Frote’s speedrun community or other community run events.
IOI Glitch Fixing Priority
There’s a difference between a glitch that affects everyone, and a glitch that only affect a few hardcore speedrunners who actively look to use these obscure tricks.
From a developer point of view, what is the point of targeting glitches that don’t affect most players, that development time is better spent on something that enhances the casual experience.
I do think that IOI’s approach to this has changed over time, they seemed a lot more active in trying to tweak things in Hitman 2016 and Hitman 2 (2018) than in Hitman 3 (2021). To date, there have been no major changes to Hitman 3’s rating system since launch, while Hitman 2016 and Hitman 2 got several tweaks over time.
Perhaps IOI want to just keep things stable as everything mostly works now. Remember, “tranq glitch” was born from the last major change to Hitman 2’s rating system (introducing the legal accident KO’s mechanic). Maybe they don’t want to risk change anymore. But I don’t want to put words in their mouth.
In-Game Leaderboards
So what is the big deal if some glitches aren’t fixed anyways? Are you afraid you need to use all these glitches to get the top times on the in-game leaderboards?
Frankly I’ve never put much credibility on the in-game leaderboards considering that
A) The in-game leaderboards aren’t cross platform, someone on Steam won’t see the times on Epic. Even though these are functionally identical game versions both on PC.
B) They never remove cheaters on PC.
C) They don’t remove any runs from old patch, even runs that literally aren’t possible anymore. The leaderboards for A Gilded Cage (Marrakesh) and many other maps (for platforms other than Steam which released later) have a bunch of 7 second SA runs on the in-game leaderboard. These aren’t cheated times either, it used to be possible to shoot through all walls with Druzhina 34 Arctic rifle but this was patched a few months in like February 2021. I understand why IOI don’t bother to remove old patch runs that no longer work, but it also destroys their credibility.
Community Leaderboards
Most community run leaderboards for speedrunning and whatnot have their own “house rules” anyways. Frote7’s Speedrun Community and speedrun.com leaderboards both ban some glitches, with tranq glitch being one of the main ones.
Now, if you don’t agree with which glitches are banned from speedrun.com, Frote’s Speedrun community, or elsewhere, fine.
Make up your own “glitchless” ruleset, form a community, get like-minded people to compete with you, no one is stopping you. The current speedrun.com rules and Frote’s speedrun Community rules are unlikely to change in the near future however.
Like it or not, a lot of Hitman speedrunners like using at least some of these glitches and the community leaderboards and events reflect that mindset.
PS: I’m not gonna debate what is or isn’t a glitch cause that is a bottomless rabbithole and a huge reason why I have never bothered implementing an all-encompassing “glitchless” ruleset for Hitman 3 on speedrun.com either.
This is mere opinion, not fact. If you were right, wouldn’t we still have other things like Wallbangs? Coin Lure? And any other thing they changed cuz it wasn’t about their intended design?
People who are panicking about something get very narrow tunnel vision in real life so I buy the various behaviors there. Wall hacks should be fixed (though they’re probably harder than we think to fix). Gun lures are funny but ultimately it’s something you have to intentionally set up and they enable interesting kills.
My only real gripes are boosting, tranq kill and mud shots which are very clearly glitches.
As funny as they are to watch, it kind of kills me that speedrun comps have to be won by launching 47 through a ceiling, off the side of a building or even into the stratosphere or launching another bomb onto the other side of the map.
Kill boxes being set-up above ground would ensure ceiling and map breaking would end but it would also make normally non-lethal explosions lethal depending which angle an NPC was thrown.