%% Image and caption selected per Image Pickin' thread: http://tvtropes.org/pmwiki/posts.php?discussion=1373150634081334900
%% Please do not replace or remove either without starting a new thread.
%%
[[quoteright:350:http://static.tvtropes.org/pmwiki/pub/images/hitbox_9038.png]]
[[caption-width-right:350:{{Touche}}, or [[Creator/WilliamShakespeare not touché]]... that is the question.]]

->''"There are no hitboxes, there are just ideas."''
-->-- '''LetsPlay/{{Medibot}}''', ''[[http://www.youtube.com/watch?v=YScneARDb2o#t=107s Lets Play Sonic Shuffle]]''
%%
%% Only one quote on the main tab, please.

In video games, a hitbox is the part of an object considered 'solid' for the game's purposes. It would be very mathematically complicated to model all the characters' body parts and check when they've touched, so instead, a rectangular or cubic region of each character is chosen as the hitbox. When two hitboxes overlap, the game knows that the characters have collided; when an attack lands inside a character's hitbox, it has hit the character. FightingGame jargon usually differentiates the two boxes by calling the boxes that hit enemies (causes enemies to flinch) as "hitbox" and the boxes on their body as "hurtbox"[[note]]In most cases they overlap; over time, game developers are able to make boxes that act differently, and so the term "hurtbox" is born[[/note]]; in other genres the term "hitbox" gets used for both.

In the early days it was a box, as a rectangular or circular solid is less math-intensive when doing the collision checks. More modern 3D games have a whole separate model made of hitboxes that closely follows the rendered model in logical space, many including different values for different body parts to enable [[AttackItsWeakPoint hits to weak points]] for massive damage.

Sometimes, whether intentional or not, hitboxes don't match up quite right with the graphics, thus producing Hitbox Dissonance. This can take several different forms:

* An enemy's hitbox is too small. This makes the enemy harder to hit, and tends to happen with small enemies that are already GoddamnedBats to begin with.
* An enemy's hitbox is too large. This is especially problematic for enemies that attack via CollisionDamage, and in extreme cases can break WillingSuspensionOfDisbelief when shooting the ''air'' two feet away from the big guy makes him bleed anyway. On the other hand, a larger hitbox means [[GoodBadBugs you can hit the enemy without your attacks actually touching the enemy]].
* The player's hitbox is too small. Although it makes the game easier against enemies (especially when [[BulletHell dodging bullets]]), it can be more difficult trying to land on a platform when you don't know how much platform you have to work with.
* The player's hitbox is too large, or extends beyond the visible portion of the sprite. This can be a rather glaring form of FakeDifficulty if your character is a OneHitPointWonder.
* Projectiles' hitboxes are too small. On magic, fire, or energy projectiles, this can be HandWaved as only the core of the projectile counting, with the aura around it just being gases or debris of some sort.
* Projectiles' hitboxes are too large. This can prevent the player from shooting through small spaces or around cover, which may or may not be a good thing, depending on the game.
* The hitbox is disjointed: the hitbox and main damaging areas do not follow the physical logic of the attack. For fighting games, disjointed hitbox means the hitbox and hurtbox don't overlap like they usually do, which may mean [[InvulnerableAttack the attack is invulnerable]].
* The hitbox for world objects is broken, meaning shots will incorrectly shoot through an object or be incorrectly blocked by objects.

Some developers intentionally create this difference in collision size. The most frequent intentional use is a small player hitbox, hopefully displayed clearly so the player knows exactly what they can and can not get away with.

FightingGame fans tend to ''explode'' when they encounter this type of problem. Maybe even the ''winner'' will RageQuit, having unearthed the inherent unfairness. Regardless, it occasionally can be considered a {{Good Bad Bug|s}}. Not to be confused with ModelDissonance (although they could overlap).

----
!!Examples:

[[foldercontrol]]

[[folder:Action Adventure]]
* ''VideoGame/MediEvilResurrection'' included [[ItMakesSenseInContext sentient, man-eating pumpkins]] with a headbutting attack that did damage ''before the animation started''.
* One of the many, many flaws of advergame ''VideoGame/DarkenedSkye''. The hitboxes on the enemies are rather smaller than the models (especially, yes, the GoddamnedBats), while your own hitbox is larger but your ''weapon's'' hitbox seems to be smaller. Fights are frustrating, to say the least.
* This is a rare example of hitbox dissonance in a static object. In ''VideoGame/TheLegendOfZeldaTheWindWaker'', stairs in later parts of the game actually act like ramps, probably because it took too much time to make every tiny step in the stair hitbox (the game was nearly over deadline), so the programmers instead created much simpler ramps instead. However, there ''was'' enough time to model every single step in the stair models.
** Also, the Moblins' staff swing attacks seem to have an unusually far range. Link will be standing three feet away from one, and in the blink of an eye, he's been flung onto the ground. This also seems to be the case with the Poes' scythe attacks from ''VideoGame/TheLegendOfZeldaTwilightPrincess''.
* ''Neutopia II'', the Turbografx-16 answer to ''The Legend of Zelda'', doesn't handle jumping and flying very well. For example, you are at the upper section of the room doing something, and there is a jumping enemy at the bottom part of the same room. The enemy makes a huge jump (his shadow is visible on the bottom of the screen), but doesn't actually move anywhere. If the enemy sprite touch yours during the jump, it will actually damage you. And it works the other way around too, as you can attack the enemy while it is "in the air".
* In ''VideoGame/ETTheExtraterrestrial'', the eponymous character's sprite has ''pixel-perfect'' hit detection. The problem with that is the game is in a ThreeQuartersView, meaning his ''head'' can cause him to fall into a pit. It's not [[TheProblemWithLicensedGames the only problem with the game]], but it's one of the most annoying.
* In ''VideoGame/DragonsDogma'', Daimon has an attack where he flies at you & tries to grab you. It works if you're any where near him. Even if you're under his feet which are very far from his hands because he's giant.
[[/folder]]

[[folder:Action Game]]
* The original ''VideoGame/NinjaGaiden'' trilogy nearly falls into the realm of FakeDifficulty because of its poorly sized and placed hitbox areas, both in the player character as well as in the enemies. The [[WarmUpBoss Act I boss of the original]] suffers from this too. You can have your sword be centimeters from hitting him, and you'll still do damage.
* In ''VideoGame/ToyStory'', the hitbox for Buzz during the gas station fight is noticeably large when he's bounding around the stage, so you get hit unless you're directly below the arc, making this fight unfairly hard.
* In ''Bugs Bunny Crazy Castle 2,'' both WesternAnimation/BugsBunny and [[WesternAnimation/LooneyTunes his enemies]] had tiny hitboxes, which could lead to odd situations where Bugs Bunny could walk right through them without any harm. The weapons Bugs could pick up, on the other hand, had large hitboxes, and in most situations, had no trouble hitting an enemy's small hitbox. It almost completely works in the player's favor, at least, and since Bugs is a OneHitPointWonder, you may need all the help you can get.
* In ''VideoGame/BattleCity'' and ''Tank Force'', players and enemies actually "snap" from one half-tile to another even though sprites seem to go smoothly. This was done to ease navigation as the problem was apparent in ''Tank Battalion''.
* The hitboxes for Chief Scalpem/Wigwam's knives in ''VideoGame/SunsetRiders'' don't always seem to be in the same place as the physical knives, meaning that in some cases, the safest place to be is directly in their path.
* ''VideoGame/AlienSyndrome'' for the NES had a severe case of the "bigger" kind. In some cases, you could shoot the air and still kill your foes, and likewise you could die from touching the air near them.
* Presumably this occurred with things like walls (especially oblique ones) in ''VideoGame/{{Superman 64}}'', since a few cases shown in WebVideo/TheAngryVideoGameNerd's review had the player get stuck despite being about three feet from the actual wall. See [[http://www.youtube.com/watch?v=1dJXgJ1c4vY&ob here at about 6:20]]
* In ''Warriors'' games (such as ''VideoGame/DynastyWarriors'', ''VideoGame/SamuraiWarriors'', etc.), horses have their hit boxes located in their torsos so {{Mooks}} take damage when you run into them, making it look like they're being trampled; however, this means that you can park your horse against a wall and have their heads disappear into the masonry.
* Due to a glitch in the ''[[UpdatedRerelease HD Final ReMIX]]'' version of ''VideoGame/KingdomHeartsII'', some of Vexen's ice attacks will hit even when they're clearly not near their intended targets.
* Because [[VideoGame/RabiRibi Rabi-Ribi]] was designed with bullet hell elements in mind, Erina's hitbox is actually much smaller than her sprite, different from the usual fare for 2D Platformers and Action games. It can be viewed either through a hidden technique or just shortly after a boss fight starts (in the later versions). To balance it out and make things look fair, the game designs the rest of the game's hitboxes with both sides in mind:
** The aura/glow around many small bullets are included in the hitbox. Notable example is the pellets that sprout from the swaying stems attack.
** Most bullets that look larger have their hitboxes smaller than the edge of the sprite would suggest. Notable example is Syaro's falling crystals attack; on certain difficulties, going through the middle of 2 of these perfectly placed beside each other is the only way to clear that pattern without damage.
** Hitboxes of enemies are usually a bit larger than their sprite suggests. While this makes landing combos easier without sacrificing difficulty, it also balances it out due to Erina's visual sprite actually hitting the enemy visual sprite to trigger CollisionDamage.
** Despite the game's balance, there are still some projectiles that are quite non-intuitive:
*** Lilith has an attack where lightning shoots down from the sides of the screen and thin-but-long bullets form from them and move towards the center. The hitboxes of these thin bullets extend slightly way past its tail.
*** One of the final bosses of the main game is a long, huge flying creature, and it has an attack which swoops down and immediately flies up towards your location. However, the wings have absolutely no hitbox, meaning you can just walk sideways and completely dodge it. Justified in that the attack is so fast that it would probably be undodgeable otherwise. This does also mean, however, that hitting its wings don't do damage.
*** "Lightning-like" laser attacks' hitboxes immediately form entirely even before the the entire lightning comes down. This means that if you happen to be just in range of where the laser would strike, as soon as the visual forms at the top of the ceiling, Erina can get hit even before it hits the ground. This is most evident when its the fatal attack, as the screen freezes when Erina gets KO'd and you can see the lightning not even anywhere close to the middle of its path.
[[/folder]]

[[folder:Driving Game]]
* Racing series ''VideoGame/{{Burnout}}'' and ''Excite Truck''\Bots also use this, with "near miss" and "tree run" bonuses. The "small hitbox" is your whole car in these games though, and the "large hitbox" is the area around it.
* Many early driving games have entirely rectangular Hit Boxes, which is really JustForFun/{{egregious}} when it extends all the way to the side-view mirrors.
* ''VideoGame/{{Screamer}}'' seemingly has two hitboxes for each car: the front, which massively slows or flips a car when hit, and the back, which goes through other cars but may trigger their front collision. In short, as long as you're even one millimeter ahead of your opponents, sideswiping them causes your car to clip through them and then they wreck.
* While ''VideoGame/{{GRiD}} 2'' has correct hitboxes, all the weight of a car is in the back regardless of its actual shape or the weight distribution of the real car, apparently to combat the [[{{Griefer}} rammer problem]] that existed in the first game. When you hit the back of an opponent, you get knocked off course while they continue on largely unaffected. It took the online community about a day to figure out they can now effortlessly [[{{Troll}} push you off the road]] as long as they are in front. The [[EndlessCorridor track design]] isn't helping.
* Unlike in previous games, ''VideoGame/MarioKart8'' had some bugs in regards to certain walls, fences, ramp sides, and barriers that previous games didn't have. The effects of this dissonance can vary depending on the surface, but players have found themselves stopped completely just by simply brushing up against the surface's side or when boosting, being thrown 90 degrees away from the surface's side. Items that are shot ahead often bounce off these sides back at the users even if the user fires them at an angle.
* In ''VideoGame/WanganMidnight Maximum Tune'', the cars' hitboxes extend infinitely along the Y-axis, so as to prevent one car from getting on top of another (such as on jumps).
[[/folder]]

[[folder:Fighting Game]]
* ''VideoGame/SoulCalibur'': Custom characters suffer from this. Since all custom characters are the same height but use a standard character's weapons, the standard character's hitbox is mapped onto the custom character, which leads to problems when using the style of a particularly tall or short character.
** ''V'' tries to avert this by letting custom characters' heights be chosen. A star is above the choice that matches the standard character's height the closest.
* ''VideoGame/{{Tekken}} 5'' was pretty notorious for [[http://www.youtube.com/watch?v=wk34aY6x4t8 grounded mids]], especially in wall combos. To clarify for non-Tekken players: some mids do have the property of hitting a character on the ground (downward chops, rising kicks, etc). But there were a lot of straight thrusting attacks that hit a person almost completely lying on the ground or rolling to the side. One big offender was Anna's Tread Water kicks to Judgement Kick (f,f+3,4,3~b, 3), the last of which was a front kick which would hit a grounded opponent or sometimes even an opponent ''behind'' Anna.
** During the release week of the console ports for ''Tekken Tag Tournament 2'', it was discovered that when crouching, Kunimitsu not only avoided every high-hitting attack in the game, but PLENTY of mid-hitting attacks in the game because she of all the characters breaks the universal rule of being vulnerable to mid hits. It has since been fixed as of now.
* ''VideoGame/{{MUGEN}}'' - Disjointed hitboxes are also one of potentially many signs of a badly made character. Remember, the quality of the sprite has nothing to do with how the character gives nor receives damage, as those are programming values.
* ''VideoGame/SuperSmashBros'' has a lot of these problems, partially due to the fact that a single attack will have several different hitboxes with sometimes wildly different strengths.
** Ganondorf's Down Special continues for about four seconds, but by the third second it stops doing potential damage. This creates the odd situation where you should be going through someone with your foot but they smack you back. More evident in his recovery (up special) where not only is it unlikely that you will latch onto an opponent, but the punch at the end will most likely never hit.
** Snake's side and up tilts are absolutely ludicrous in this regard. Both of them have hitboxes which strike at least a foot in front of where his feet/hands end. This is especially noticeable with his up tilt, which makes Snake kick straight upwards into the air and yet can hit an opponent seemingly three feet in front of him. This is because in development at some point Snake's model was resized, but they forgot to resize his hitboxes, resulting in all of them being twice as large as the model.
** In ''Melee'', Marth and Roy's grab hitboxes are twice as long as they really should have been. Their standing grabs are actually able to grab Yoshi from farther out than he can grab them, despite them having seemingly standard grabs and Yoshi having an obviously ranged grab via his tongue.
** Quite a few characters can hit people standing ''behind'' them thanks to attacks with hitboxes that extend behind their back or over their shoulder. It's also common to see larger characters such as Bowser or DK be a victim of grabs, when the person grabbing them was nearby, but facing the opposite direction.
** King Dedede's has a long grab range, extending quite a distance from his actual hand.
** Meta Knight's up taunt includes some hurtboxes way above him. If he's on the main platform on ''Brawl'''s Yoshi's Island, and someone attacks while on the upper platform, during his up taunt, it's possible to hurt him.
** The fourth game addresses this by either adding SwordLines to most moves that would otherwise suffer from this or enlarging the fists/legs of the character in the middle of the attack. However, there are still a few cases of attacks missing despite all appearances due to the hitbox not actually being active until a certain point. For instance, Little Mac and Wario have forward-smash attacks that consist of a vicious punch in front of them, but it's entirely possible for them to miss if the opponent is too close, even with the fist going straight through them.
** In the fourth game, Meta Knight's attack range was {{Nerf}}ed to about half of what it was in ''Brawl''. [[GameBreaker While this was a good thing for balance]], the fact that the size of his sword model hasn't changed means that visually, the upper half of his sword is completely non-functional. The aforementioned SwordLines even have the same dissonance, suggesting that the range nerf was probably added relatively late in development.
** Greninja's hurtbox extends above his head, so some attacks that clearly should hit will register.
** Despite the game being played in a 2D plane, the hitboxes still follow the 3D models. It's why sometimes you'll see attacks passing through a character despite seemingly hitting them - because the model is in a (non-dodging) pose that somehow makes the attack not connect with it.
** Bayonetta's spot dodge has her leaning back towards the foreground. The hurtboxes ALSO leaned into the foreground, which means some character's grabs (like Pikachu) would never hit her. The worst part is the hurtboxes didn't return back to normal, so she was flat out invincible. This was quickly fixed in a later patch.
** Jigglypuff is notorious for its Sleep attack hitbox being confined to the area around and between its eyes. Even large characters with ddisjointed hitboxes might be able to avoid, particularly in later games, where characters will gently push away from each other if they occupy the same space.
* Hattori Hanzo's LimitBreak in ''VideoGame/SamuraiShodown III'' had a hitbox that stuck around nearly a second after the actual explosion. Worse, it did not [[{{Combos}} combo]] with the rest of the attack, meaning that a person who blocked the attack could let off the block a moment too early, and end up taking the full brunt of it anyway.
* In ''VideoGame/BlazBlue'', the hitbox for Ragna's [[LimitBreak Carnage Scissors]] is much taller than the graphics would suggest. It is even more noticeable with Hakumen's Yukikaze. The thing hits the entire horizontal plane and even double jumping will not save you unless you have moves that rocket you farther up screen.
* NES version of ''VideoGame/YieArKungFu'' suffered for this quite a bit where a hit was registered a miss and vice versa. The fact that the enemy was mostly made out of background instead of sprite contributed to that.
* ''VideoGame/KillerInstinct'' was known for allowing some truly absurd crossups - essentially, kicking your opponent in the face by jumping over their head and grazing the air a metre behind them with your left knee.
* As you'll find below, ''VideoGame/{{Touhou}}'' is famous for how important your character's hitbox is. This even carries over to the fighting game spinoffs, where sometimes dodging that instant-kill spellcard or that one bullet that would knock you out upon hitting relies solely on your knowledge of hitboxes.
* There are probably a few instances of this in ''VideoGame/StreetFighterII'', but an especially noticeable one comes in Champion's Edition, when Vega's crouching medium punch meets Zangief's sweep kick. Although visually Gief's foot passes under Vega's arm and doesn't touch either of his legs, this exchange results in Vega being tripped and Zangief not being struck at all.
* ''VideoGame/StreetFighterIII'' has a problem with so called "nails"[[note]]named because people think the characters are only hitting the enemy because they forgot to trim their toenails or nails.[[/note]] where attacks would extend just a little farther that they should, as seen in the quotes page.
* ''[[VideoGame/StreetFighterIV Super Street Fighter IV]]'': In a shocking {{nerf}} to fan favorite Makoto, who in Street Fighter 3 was able to pull combos like [[http://www.youtube.com/watch?v=pRwadFHfLhM this]], her EX Grab didn't extend past half her arm's length; they've since fixed this in Arcade Edition. In ''Street Fighter IV'', the developers wanted to do 3D polygon collision instead of hitboxes. However, negative feedback from fans resulting in the game playing this straight.
* ''VideoGame/StreetFighterV'': Part of the reason Nash was a TierInducedScrappy early in the game's life-cycle was the fact that his hurtboxes during his punches and kicks were ludicrously big -- in the neighborhood of 150% bigger than his arm/leg -- making it trivially easy to stuff his attacks.
* ''VideoGame/MarvelVsCapcom3'' has quite a few of these.
** Most notable is [[TheIncredibleHulk Hulk's]] standing H, which can hit an opponent directly behind him, even though he's swinging his fist the opposite way.
** Another example is how VideoGame/ViewtifulJoe's hitbox was updated in ''[[UpdatedRerelease Ultimate Marvel vs Capcom 3]]''. Though Joe is already a small character, his hitbox shrinks whenever he is airborne. This was done to facilitate his evasion of projectiles as he approaches his enemies, as Viewtiful Joe relies heavily on his DoubleJump and [[VideogameDashing Air Dash]] in regards to mobility. With his shrunken hitboxes, Joe can get up close and personal much more easily, at which range his own stubby limbs aren't a both.
* ''VideoGame/DeadOrAlive'': Wake-up kicks can stun an opponent even when they look like they're merely tapping their toenails. Particularly grating when the opponent lands no less than 6 feet away.
* In ''VideoGame/MarvelContestOfChampions'' [[Film/GuardiansOfTheGalaxy Rocket Raccoon]] has the same size hitbox as all other champions, so as not to give him an unfair advantage due to his relative smallness. This is also why he [[PowerFloats always floats in combat]] using his jetpack and only gets down on the ground for one special attack and for his winpose.
[[/folder]]

[[folder:First Person Shooter]]
* There's nothing quite like putting bullet holes into empty air in ''VideoGame/{{MAG}}''.
* In vanilla ''VideoGame/{{Doom}}'', for collision with objects and monsters, everything is essentially treated as having infinite height, allowing monsters to savage players even if they are really high up. This is thankfully averted for projectiles, which can soar over your head harmlessly should you choose to dodge in such a way.
** The sprite for Revenants is noticeably taller than their hitbox. The difference between sprite and hitbox doesn't manifest as aiming difficulties, but it allows Revenants to walk in tunnels that they shouldn't fit into.
** The Spider Mastermind seems to take up space at least four feet farther on each side than it appears. This often leads to it getting hung up on walls and other monsters when used in [[GameMod custom levels]].
** The plasma rifle has the "projectile's hitbox is too large" variety.
** There's also a bug where a bullet can completely fail to hit its target depending on where the shooter and the victim are standing in open space, even at point-blank range. [[http://games.moria.org.uk/doom/research/shooting-through-things Click here for details.]]
** Projectiles that impact with the "ceiling" of sectors which have an open sky immediately disappear. This is rarely triggered without playing in source ports which allow freelook, however.
** Due to the pseudo-3D gameplay and the way in which maps are created, switches can be triggered [[http://doomwiki.org/wiki/Linedefs_can_be_activated_regardless_of_player%27s_Z_position even if you're not physically on the same level as the actual graphic for that switch]]. ''VideoGame/HacX'' [=MAP16=] in particular can be completed in one second because the exit switch is in the same area the player starts the level in, just hidden underground until the player finds and uses four other switches throughout - just turn around and use the empty air behind you, and the map is completed.
* ''VideoGame/{{Unreal|I}}'' brings us both monster variants:
** The Titan, being essentially a twenty-foot reptilian gorilla, isn't very compatible with the simple collision cylinders used in the game, thus ending up with at least a minor form of the "shoot the air next to him" trouble. That said, this is probably a good thing for game balance due to his immense power and durability.
** The pupae and predator enemies are best taken out from afar, since once in melee range, their narrow collision cylinders make them nigh-untouchable.
* The Spy of ''VideoGame/TeamFortress2'': Landing a successful backstab (which is instant death) depends on the view angle of the victim, and not the actual pose of the character, causing dissonance when combined with some animations. This is in addition to lag and the game's rather odd way of calculating melee hits (using the player's bounding box) and, well, you end up with a lot of sidestabs and [[FanNickname facestabs.]] Numerous tweaks and updates have gone toward trying to get it right, though you can't please everyone.
** To the Spy's considerable advantage: a disguise [[http://wiki.teamfortress.com/w/images/e/e1/Disguised_spy_hitbox.png does not change your hitbox]]. A headshot to your fake head will hit you in the torso if the model is short enough.
** To add to this: the Spy can disguise as his own team, so the enemy sniper may not even know the player is a Spy.
** Better still, the Sniper is taller than the Spy. It's very possible that what would have been a headshot on a real Sniper will go straight over your head.
** With the Sniper's bow unlock, the Huntsman, [[http://www.nerfnow.com/comic/345 it's quite possible to aim a few inches to the left or right of an enemy's head and still get a perfect headshot]], as it uses the projectile hitbox (which is the same for every class and just a giant box) rather than the bullet one (which varies by class and conforms to their model and movement). The arrow, rather than sticking the body as it normally would, simply disappears. Getting {{Boom Headshot}}ted from someone that certainly ''looked'' like they missed has led to derisive nicknames for the weapon, including "Huntspam" or "Lucksman".
** Being hit by an enemy with a melee weapon in general is wonky - It will often appear the enemy is several feet from you and hitting you with a really long fist. This is because, rather than using hitboxes, melee attacks use one big map-aligned cube to determine hits. Further compounding the issue is several melee animations, namely all of the Pyro's weapons and the Demoman's two-handed weapons, are disjointed relative to time. What this means is from your perspective, the attack hits while the Pyro/Demoman is still winding up for the strike. The Pyro/Demoman don't see this, however; their first-person animations are synced properly. The Engineer has the opposite problem, which can be demonstrated by aiming at a wall and using melee. It will leave a strike mark in the wall AS HE BRINGS THE WRENCH UP to swing.
** Taunt kills are even more silly. It's possible to temporarily dislocate the hitbox from the onscreen model, making it so that, for example, Sniper's arrow stab shanks someone directly behind him. Even without that, the range for several of them extend far enough to where the attack's animation doesn't have to actually touch the victim to do the damage. Most taunt kills even hit above you, so if your enemy is standing on your head they still get shafted. This isn't even touching on Heavy's ability to shoot his FingerGun a full 90 degrees above/below where his arm is pointing.
** Speaking of taunts, animations like taunts and post-round humiliation stances (and others like spy crabs) do not have matching hitboxes, meaning you need to shoot where their head would be if they weren't taunting, spycrabbing or being humiliated (thankfully, taunting opponents are immobile and humiliation gives you unlimited critical hits, mitigating the issue). This actually becomes a problem in Mann Vs. Machine as robots that hold the bomb long enough start giving out {{Status Buff}}s but taunt to give the playering an opening. It can make killing them as sniper before they move again quite frustrating.
** The [[ActionBomb Sentry Buster]] in Mann Vs. Machine has a model that looks a seamine with legs, [[http://wiki.teamfortress.com/wiki/Sentry_Buster#Trivia but the hitbox of a Demoman with an Ullapool Caber]]. This actually works in the players' ''favor'' because the hit box covers everything the model does plus invisible arms and legs--Snipers even get critical hits for shooting them in the head they don't have!
** The Halloween event map Ghost Fort ([[NonIndicativeName which is actually played on KOTH Lakeside rather than 2Fort]]) features the ghost-wizard Merasmus, who can spin the Wheel of Fate to curse the players every time the point is captured. The curses include "Big Head" and "Tiny Head" curses, which gives them comically deep or squeaky voices respectively. To the dismay of Snipers and relief of everyone else, while the models for the heads may balloon up to the size of their body or shrink to the size of a man's fist, hitboxes are unaffected. This actually makes getting a headshot on a Big Headed enemy much more difficult since the definition of where the head hitbox is in the model is no longer clear.
** Until it was fixed in a patch, the Engineer didn't have a hitbox for his crotch, while the rest of the classes do. Examined [[https://www.youtube.com/watch?v=Si2YGyURTio in this video]] (it also mentions other instances of hitbox dissonance, such as the Scout's messenger bag and the Pyro's fuel tank being hitboxes). The absence of this hitbox is a little less noticeable than other dissonance instances due to the crotch being a relatively small portion of the whole model (which may be why it had been left unpatched since at least 2007).
** Lastly, in a dissonance that effects everyone, all hitboxes are disjointed relative to time. That is, your hitbox exists a fraction of a second in front or behind you. This is a side-effect of the hitbox prediction system used by the engine to compensate for minor latency spikes and make the game run smoother. For most weapons, namely projectiles, the difference is only 1/60th of a second, almost imperceptible to the human players. But every now and then you can get your head blown off by a Sniper a quarter-second after you'd ducked behind a wall.
* In ''VideoGame/CounterStrike: Source'', players' hitboxes actually lag a step behind their models. This can lead to some frustrating missed shots or WTF deaths. This happens in just about any online shooter to some extent, varying depending on lag and netcode.
** For the technically-inclined, an excellent article on how Source engine games (''VideoGame/HalfLife2'', ''VideoGame/CounterStrike'' etc.) usually handle this can be found [[http://developer.valvesoftware.com/wiki/Latency_Compensating_Methods_in_Client/Server_In-game_Protocol_Design_and_Optimization here]]. Making sure that gameplay ''seems'' fair (even at the cost of it actually being fair) is an important priority for developers who want the game to be any fun.
* ''VideoGame/CallOfDuty'' frequently has seemingly wonky hitbox detection, as seen from killcams in online play. The hitboxes are actually very, ''very'' detailed, but even a small amount of lag (as in, normal amounts of lag), can turn a kill into a miss. Headshots are, therefore, best pushed into the realm of luck rather than skill with anything other than a sniper rifle[[note]]except against players using the "Last Chance" perk/deathstreak, where, possibly due to the massively different pose than usual when it's activated, headshots tend to be much more common[[/note]]. Games in the series that try to compensate for lag often end up making this even worse - resulting in, say, a sniper standing right next to a window, aiming down, and killing you along the wall below, when from your perspective all that's even visible is the very tip of his gun's barrel pointing straight forward.
* "Normal" hitboxes that players are used to demonstrate this trope. The premise is simple: players feel cheated when their bullets go through enemies, but badass when they're the ones dodging bullets. So, heroes tend to have smaller hitboxes than their sprites would suggest - this is why Mega Man puts his foot through the floor whenever he lands from a jump.
* ''VideoGame/KillingFloor'' had effectively broken hitboxes on a pair of high level monsters, one had his head hitbox buried in his neck in such a way that it was more or less impossible to hit without attacking from above, another had his head hitbox floating in mid air above his left shoulder. This meant that new players attempting to gain head shots by shooting at ''the head'' found it impossible. Veterans that had learned about this and knew where to aim or how to exploit AI could hit them, but of course when this bug was finally fixed there were cries that the devs were pandering to the scrubs and had ruined the difficulty.
* In ''VideoGame/Left4Dead'' the Hunter's hitbox is actually a ways ahead of him, as various [=YouTube=] tutorials have pointed out. One must take this into account when trying to melee them during their pounces. This has also extended to the Jockey and the Spitter in the sequel. The Jockey can leap and latch onto a survivor from at least 2 feet away due to its ranged hitboxes and the Spitter's acid patch has a slightly larger hitbox, leading to players being damaged from the acid even though their character models aren't physically standing in the acid.
** The sequel as a whole seems to have much less polished collision detection - Melee weapons are always supposed to be a one-hit kill, but can clip through zombies, or even hit them without killing them - The hit sound will still play and in some cases there'll be blood, but the zombie won't die. When it comes to Special Infected, the new additions are pretty bad as well - Chargers sometimes grab you when you're outside of their immediate range, while sometimes they won't, and the Jockey's hitbox is a fairly large distance from the model itself, which makes shoving Jockeys away very hit-and-miss. [[TheComputerIsACheatingBastard The fact that Jockeys have a really bad tendency to pop up out of seemingly nowhere doesn't help, either.]] On top of that, all these bugs can happen in single-player and local games as well.
** The survivors generally have the same sized hit boxes so that no survivor has an advantage over another survivor, but Zoey's hit boxes are slightly smaller than everyone else.
* In ''VideoGame/MetroidPrime2Echoes'', Emperor Ing's [[BishonenLine second form]] takes an absurd amount of damage from the Screw Attack if you land near his feet. Not a direct hit, you must land near him. He'll crumple in under a minute. Also, his chin seems to block many blasts if you shoot him from ground level; try jumping. Data hacking revealed Ing has DummiedOut hitboxes near his knees that block shots but can be Screwed. The Wii rerelease fixed the hitbox.
* When diving to the ground in ''VideoGame/{{Battlefield}} 2'', the animation shows a running character jump forward before landing on the ground. The hitbox, on the other hand, changes to 'prone' instantly, making the diving character very hard to hit, even if you know you shouldn't aim for the airborne body but for the ground below him.
** The hitbox wasn't the only thing that went straight to prone. So did the diving players accuracy. This is why before it was fixed in a patch DolphinDiving was the biggest GameBreaker the series had ever seen.
* ''VideoGame/{{Battlefield 3}}'' has major examples of the physics object hitbox issues. Many of the random items on the floor of the world like boxes or pieces of rubble are only client side, not server side. Which means the rubble, box or crate you are hiding behind on your screen is actually nowhere near you on your opponent, meaning you are standing out in the open from his view.
* ''VideoGame/{{Postal}} 2'' has an JustForFun/{{egregious}} example with Gary Coleman, especially noticeable when he gets into a fight with [=NPCs=] that ALWAYS [[BoomHeadshot aim for the head]] and make puffs of blood appear ABOVE Gary's head. This is presumably done to maintain balance in multiplayer and avoid the issues that ''[[VideoGame/GoldenEye1997 GoldenEye]]'' had with everyone trying to pick Oddjob.
* It's possible to create this with custom skins in some games, including the original ''VideoGame/UnrealTournament'', if the skin is sufficiently larger than the normal character model. Snipers trying for headshots will have a much harder time hitting the character. Then again, this can backfire as less skilled/experienced players can get accidental headshots while attempting (generally more reliable) body shots.
* The zombies in ''VideoGame/NaziZombies'' seem to have hit boxes that are as large the doors they are trying to maneuver through. This has resulted in many a game ended because of one zombie taking up the entirety of what appears to be a double door.
* The player models in ''Franchise/{{Halo}}'' games from ''VideoGame/{{Halo 3}}'' onward (including ''VideoGame/HaloReach'' and ''VideoGame/Halo4'') had this, with a mix between being silly and slightly realistic: Shooting a player's gun will hurt the player, while you can also stick with a gun with a grenade.
* In ''Warrock'', shooting an Assault's backpack will deal damage as blood spurts out of the pack.
* In the original ''Videogame/PlanetSide'', players could cause their hitbox to disconnect from their body by exploiting the game's primitive netcode; by rapidly alternating the left and right strafe keys, players would start [[TeleportSpam warping back and forth]] with their hitbox lagging behind them. The glitch returns albeit ''far'' less potent in the sequel, as players using their weapon's sights move slower, though minor dissonance is noticeable on weapons with less of a speed penalty.
* ''VideoGame/{{Overwatch}}'' has extra large hitboxes for projectile weapons. This has led to situations where characters like [[ArcherArchetype Hanzo]] can effectively get headshots around corners.
** ''[[Creator/BlizzardEntertainment Blizzard]]'''s reasoning for this is to allow characters with projectile weapons a fair chance with dealing with some of the more mobile characters in the game, many of which have abilities which make hitting them with projectile weapons pretty hard.
[[/folder]]

[[folder:Maze Game]]
* ''VideoGame/PacMan'' has a smaller hitbox than it seems. Especially apparent in ''Championship Edition'' series. This is an odd case in which his hitbox is based on his position in the maze rather than his actual sprite. It's because of this that you will, very rarely, see Pac-Man [[GoodBadBugs pass right through a ghost without dying]] at times -- both Pac-Man and the ghosts have a hitbox consisting of exactly one maze tile, aligned to the grid, and if they happen to swap tiles on the ''exact same frame''...
[[/folder]]

[[folder: Miscellaneous Games ]]
* Many games in ''VideoGame/{{Action 52}}'' suffer from this as the games are little more than bare bone [[ObviousBeta alphas]] of actual games.
* ''VideoGame/{{Arkanoid}}'': The last level is the only one where you can lose a life other than by dropping the ball: The FinalBoss is loosing projectiles at you. In the UsefulNotes/AmstradCPC version, said projectiles have a hitbox ''much'' bigger than they appear.
* The ''Robot Ninja Haggleman'' games from ''VideoGame/RetroGameChallenge'' gives enemies a slightly larger hitbox than the size of the enemy. This means that if you approach from the wrong angle, you will get hit without actually touching the enemy. This is particularly bad for Dark Hagglemen, who have an animation where they laugh after deflecting your attack - but which doesn't turn off their hitboxes.
* In ''VideoGame/{{Minecraft}}'', all hitboxes are square regardless of the shape of the creature, leading to some weird situations. Cows, pigs, and sheep all look like they're one block wide and two blocks long, but they have 1x1 hitboxes, allowing them to fall into holes they shouldn't fit through. Conversely, horses appear to have about the same dimensions as cows but they have 2x2 hitboxes, meaning they cannot fit into gates or passages that they should be able to. This becomes a big problem if a horse gets into a boat, as the horse's hitbox is so huge that it is difficult to break the boat without killing the horse first.
* In ''VideoGame/NekoAtsume'', this can be a problem with the special cats, as their costumes and poses mean that they appear in a different place in relation to the toys than normal cats but their hitboxes are still in the normal place. Sometimes you have to touch the toy instead of the cat in order to take actions.
[[/folder]]

[[folder: Massively Multiplayer]]
* ''VideoGame/WorldOfWarcraft'': has some examples of both (though the game indicates each target's hitbox by a circle on the ground). Many bosses have very large hitboxes to make it easier for melee classes to attack them. Kologarn for example has a hitbox that is so large that you can stand near his right arm and use an area-of-effect attack to hit both of his arms and his body (his body and arms have separate hitboxes). Some bosses on the other hand have hitboxes much smaller than their (often huge) model. A persistent problem has been that hunters needed to stay 5 yards from their target to attack effectively, while the melee have to stay in contact with it. This caused problems in fights where everyone has to bunch up. Some bosses were given two different hitboxes for melee and ranged attack, which helped the problem but at the cost of more complex and unintuitive hitboxes. Eventually hunters' minimum range was removed, in part because of this. Specific examples include:
** Sapphiron is an [[{{Dracolich}} undead dragon]] with a hitbox that covers only his feet, with his head and tail extending outside.
** Thaddius: one of his boss abilities is to charge players up with either positive or negative charges. If the two groups stand too close together, you all die, so his hitbox is unnaturally big, or nobody would ever be able to kill him. At some point a [[JokeItem Baby Spice]][[note]]An item which lowers the size of mobs, but has no non-cosmetic effect[[/note]] was exploited by some douchebag, causing a lot of wipes.
** Kel'thuzad can ice block a player, which will chain and ice block anyone else within 10 yards of that player, who will then chain to anyone within range of them. Generally if this happens to more than a couple players at once, it's a wipe. His hitbox is much larger than he is -- just big enough that three melee classes (usually offtanks in case the main tank gets blocked) can stand at the points of a triangle around him and still stay 10 yards apart. On the flip side it means that any other melee classes in the group need to stand back and watch, while also not getting too close to anyone else.
** The proto-drakes in ''Wrath of the Lich King'' often hover in combat, and their large wings mask the hitbox on the ground, frustrating for melee players finding a position to attack.
** This happens in [=PvP=], exacerbated by server lag. You can get Ambushed from twenty feet away, shot by a ranged-only attack between dual-wield melee swings that are supposed to go off simultaneously, be standing ''on top'' of an opponent ''inside their rendered model'' and find you're too far away, etc. Tauren have the largest hitbox of any playable race, which caused issues at the beginning of arenas. Tauren could have their weapon swings pass through pillars intended to provide cover, resulting in a game of maypole where the unlucky recipient couldn't even defend themselves, though this was fixed pretty quickly.
** Lag could result in environmental hazards causing player death. If there is any amount of lag, sometimes you might wind up getting burned by fire you aren't standing in (on your side). Additionally, rule of thumb is that you shouldn't try to be ''next'' to the fire. Video game physics or not, if there is any lag then you might wind up accidentally getting burned by fire that you are clearly not inside.
** At release this was notoriously bad for feral druids in cat form, because the character in that form is a long, low-to-the-ground quadraped, the hitbox was still shaped like a humanoid (tall and narrow), so a kitty had to look like it was nearly inside a mob before it counted as being within hit range. This was improved over time with patches.
** Some attacks home into a certain body part for cosmetic effect, specifically shadow priest spells, being psionic in lore meaning they usually appear at and around the head hitbox. Sometimes on non-humanoid mobs the head hitbox is in some very odd places. Sometimes the hitbox wasn't placed correctly such as in Karazahn where mind flaying skeletal horses before the first boss made you ''hit the wall'' about 20 feet away. Similarly, items that attach to your "back" or "chest" actually just attach to the front and back of your character, which is usually your back or chest. For bear druids however, this means you have [[http://www.youtube.com/watch?v=fIVwk0J2AI8 jetpacks on your rear]].
** Outside of combat, this applies while trying to interact with large sprites - collect items from a monster you killed, or talk to an NPC - when you might have to find a specific (unintuitive) spot to stand in order to be "close enough" to the core of the sprite. Sometimes you have to stand right inside the sprite, or inside its tail, or the like, in order to be close enough to interact with it at all.
** The stone drake Slabhide is particularly problematic on Heroic difficulty due to this. During the fight he unleashes a crystal spray that people have to hide behind fallen stalactites to avoid. However, if people are inside his enormous hitbox the attack won't register the stalactite as blocking it and the attack will still damage them, even though by looking at the screen there was clearly a giant block of stone between the character and the drake.
** The Ancient Smoldering Behemoth, one of five bosses from the daily quest chain in the Molten Front, is easily the largest of the monsters, but has an extremely small hitbox, so that you have to stand underneath him in order to melee him. The problem is that he also uses an area of effect attack centered on himself (which you must avoid for an achievement), making it more difficult to run out and back.
** The fel reaver in the Hellfire Citadel raid has a blitz attack that pushes everyone in front of it against the wall. The problem is, it also considers "Directly behind it", "To the sides of its hitbox" and "underneath it" to be "In front of it", meaning you can get caught even though intuitively it looks like you're nowhere near it.
* ''VideoGame/MonsterHunter''
** Players often shout abuse at the Plesioth. Its hitboxes are ''grossly'' misaligned, which makes dodging its attacks extremely irritating. Its "hipcheck" -- an attack where it slams you with its hip -- is infamous for having a hitbox several meters bigger than the creature's body. Most people, even the most dedicated swordmasters, decide to make a bow ''solely'' to be able to snipe the Plesioth from beyond its wonky hitboxes' range. As of ''[=MH3U=]'', Plesioth's hitboxes have remained largely intact and unchanged. Some of the new attacks have better hitboxes but the dreaded tail whip and hipcheck still have horribly large hitboxes that hit the player even if the player is several feet under the actual model of the attack.
** A similar issue happens whenever a monster attacks by spinning in place to whip its tail around (which just about every wyvern or dragon with a tail does). Even if the monster is so tall that it looks like its tail would just whiff over your head, it'll knock you down. Fortunately, ''World'' has largely corrected this so only the business end of whatever appendage is intended for the attack actually does damage - creating the ''opposite'' effect of being under a monster and even physically pushed around as it spins, but only taking damage when touching the tail, wings, or head, whichever is the basis of the attack.
** Diablos has another problem in that it can hit you with its club tail even if said club is lying severed on the ground. In 2nd Generation games Diablos also could hit the player with its tail whip if they stood in front of its left foot for some strange reason. It would hit before Diablos even turned its body for the tail whip. Again, fixed in ''World'' where a severed tail reduces the hitbox to the stub.
** This has been improved somewhat in ''Monster Hunter Tri'', where you can avoid some tail swipes at distances that would have surely gotten you thwacked in earlier installments.
** In terms of your own attacks, the hitboxes are slightly askew. When fighting against a large monster, it can be difficult to AttackItsWeakpoint. If even a slight bit of your swing hits the hardest armor, your attack bounces off, the monster takes little damage, and you stand there like an idiot for a second while the monster has time to attack. This makes the Barroth a WakeupCallBoss, since its the first monster to be mostly covered in hard plating.
** It also works both ways though, as since most of your melee weapons involve swinging them around, if you're under a monster and your weapon just ''grazes'' their [[AttackItsWeakPoint weakness]], the game will register it as a full-fledged hit. There are some stories going around where people have cut off tails just by poking the tail with a weapon.
** The Greatsword's vertical down-slash attack hitbox was modified for 3rd Generation games so that the hitbox doesn't begin until about 3/5 of the swing down to try and avert the issue of greatsword being unable to destroy weakpoints underneath monsters' bodies but actually caused a much bigger issue... hitting tails on large monsters with high-risen tails. Pink Rathian, Rathalos, Diablos, Brachydios, etc. now have ridiculous trial and error needed to be put into whacking the tail because your blade will go through their tail and hit the foot instead because the Greatsword's hitbox doesn't actually hit at the peak of your swing anymore. In 2nd Gen games and before you hit at the very peak of the swing (approximately 1/2 through the attack animation) allowing tail hitting to be of great use with Greatsword. Have fun hunting tails, Greatsword users.
** Additionally, this goes both ways with some monsters who fire a massive laser beams across the stage. What you're supposed to do is [[ViolationOfCommonSense sprint towards it and hit the dive button, which causes you you to face plant on the ground]], causing the beam to go over you. If you're lucky, the game will register you as dodging it when you are either still diving or are getting up. If you are unlucky, the game may decide you ''didn't'' dodge even when your hunter is on the ground.
** Dalamadur in 4U deserves special mention with the death beams. Think you can dodge them by going to a much lower platform? NOPE! The game will still register you as being hit with the death beam, even when it's a good five meters above you. Bonus points if you are literally ''behind'' an object and the beam ''goes through it''.
* The Hitbox on a Mobile in ''VideoGame/{{Gunbound}}'' is only one pixel wide. This means that you can unleash a MacrossMissileMassacre or BulletHell on an enemy, completely obliterating the ground beneath them, only to have them still be alive, perched on that one pixel your blast did not destroy. This also makes it insanely hard to kill the opponent, as most projectiles don't explode unless they connect with another hitbox, and with the ground gone and the opponent being one pixel wide, it's considerably harder now to kill them.
* The Devs had said this is the reason why [[EldritchAbomination Rularuu]] isn't available to fight in ''VideoGame/CityOfHeroes'', even though a model of him exists in the game's assets. As it stands right now, a character standing on Rularuu's shoulder would need a ''snipe-range'' power to hit him.
* The now discontinued space MMORPG ''Jumpgate'' at one time used a simplistic ovoid shape to determine if ship models were hit by missiles. For many of the designs the difference between hitbox and ship model was minimal, but some ships had their missile vulnerability increased greatly, in particular the Octavian [[http://web.archive.org/web/20120509085206/http://www.jossh.com/flight_academy/blueprints/phoenix.html Phoenix.]] The design's a long and slender fuselage and long downward-angled wings greatly expanded the missile hitbox and increased the ease in hitting it.[[note]]The ship already had the slowest acceleration of the three "fighter" class ships, which combined with its heavy gun firepower made it a favorite target for missile-heavy opponents, even when disregarding the hitbox issue.[[/note]]
* The ship models in ''VideoGame/EVEOnline'' are there purely for show. The hitbox of every ship is a sphere, the radius of which is detemined by the ship's "signature radius" attribute. This means that many large ships, especially ones that are much longer than they are wide, have hitboxes significantly smaller than the model, while small ships tend to have hitboxes larger than the ship. This doesn't matter for purposes of shooting, since you can't manually aim your weapons anyway, but will affect collision detection. For example, if you're flying a cruiser and collide head-on with an Apocalypse-class battleship (which has the longest model of all battleships), your ships wall actually pass completely inside the battleship's prow before the collision detection kicks in and bounces you away.
* This happens every so often with ''VideoGame/WorldOfTanks''. The hitboxes for tanks are generally very forgiving--most tanks have their damage zones fit the model seen while playing the game. There's a few wonky ones where the model doesn't quite line up with the the damage zone, usually by omission--for instance, the Matilda, a British tier 4 medium tank, has a cylindrical piece sticking out of its rear hull that isn't modeled for damage, as well as several boxes on its turret that don't count either. Similarly, some forms of cover will allow tanks to fire through gaps in the models, but not all--most notably, the undersides of train cars are modeled to be hollow between the wheels, to allow players to fire through what is logically open space in the real world, but gaps between adjacent train cars are not.
* This goes both ways in ''VideoGame/StarWarsTheOldRepublic''. Sith Assassins/Jedi Shadows and Operatives/Scoundrels have attacks that require them to be behind the target. The hitboxes can be wonky, which results in you being right behind a target yet the game thinks you're outside of the required hitbox, or when you're clearly to the side yet can still BackStab.
* ''VideoGame/StarTrekOnline'' had a bug early on with its pre-order/vendor-specific Tribble items. They were an item that you could pull out of you pocket and pet to heal a little HP, but a bug would cause them to increase in size each time they were used and they would stick to the player's hip as they grew. They counted as an extension of the player's hitbox and could grow to utterly massive scale, resulting in hitboxes that enabled a player to be shot from anywhere in pvp arenas and unable to fit through any passageways. This was quickly fixed.
[[/folder]]

[[folder:Platform Game]]
* ''VideoGame/MegaMan3'' has a lot of this, because Mega Man's hitbox is a rectangle. Mega Man's hitbox is consistent for all the NES games (not including ''MM 9'', which is an entirely different engine), but it's actually possible to see it, if briefly, every time the Blue Bomber gets hit. The white "damage field" that blinks through Mega Man is exactly the same size of the hitbox. It's slightly taller than Mega Man, and slightly wider.
** Where it gets ridiculous is when Mega Man fires his weapon while standing still. He leans forward, extends his arm, and projectiles emerge from the end, but his hitbox remains the same, and thus the entire outstretched arm has no collision detection at all! He can shove his arm into any obstacle and launch bullets from inside it if he pleases. In games where Sniper Joe's shield has its own hitbox rather than simply a shielded state for the whole sprite during certain animations, Mega Man can tiptoe up to Sniper Joe, reach past the shield, and shoot him directly, without having to wait for Joe to lower his shield.
** The game also has a "wrap-around hitbox" issue, where hitboxes that partially go through the top or bottom of the screen emerge on the other side. This results in strange things like Mega Man being able to collect powerups on the bottom of the screen by jumping at the top, or getting hit by enemies on the bottom by doing the same. It's also possible to trick certain bosses into shooting at the bottom of the screen by jumping close to the top, [[DifficultButAwesome though this is pretty difficult to pull off.]]
** LetsPlay/RoahmMythril mentions hitbox problems in the [[http://www.youtube.com/watch?v=A1l3E_6ndEc Yellow Devil fight]] from his ''VideoGame/MegaMan3'' Let's Play. Basically, the hitboxes of its bouncing pieces are much taller than they should be, and the Devil's fully-formed hitbox seems to exist before its body reforms.
* The Apogee platformer ''VideoGame/PharaohsTomb'' has rectangular hitboxes around everything, which can result in the player character being killed by something he apparently isn't even touching when the corners of their hitboxes overlap. There are also several places where, in order to jump over a wide gap, he has to walk right out onto the edge of a ledge until only the last pixel-column of his hitbox is still on the ledge -- at which point he appears to be standing several pixels out into thin air. Also, you can actually jump to kick the monster into going the opposite direction and even ''walk on top of a monster's hitbox''. It is up to you to stay on top; the monster won't carry you along. The technical reason is they kept with a simple collision system to allow the game to play smoothly on a wide variety of computers, but it's also HandWaved in the manual: it is stated that you need some room to fire your weapon, so you can't kill enemies if you stand too close; this is actually because your hitbox will already touch the enemy at that point.
* In ''VideoGame/StarFoxAssault'', Fox's tail has a hitbox that sometimes appears a bit larger than it is graphically, which makes him pretty easy to hit from the side. Also counts for Krystal, Falco and Wolf.
* In ''VideoGame/IWannaBeTheGuy'':
** The Kid's hitbox does not include the Cape Of The Hero or the Very Small Gun. That's ''extremely'' little difference, but it's required that you take advantage of it to be able to pass certain spike traps.
** It also does not change during the vic viper segment, giving the whole thing quite a BulletHell feel.
** In the sequel, ''VideoGame/IWannaBeTheGuyGaiden'', the newly-added [[GrapplingHookPistol bionic arm]] often latches onto thin air.
* In ''VideoGame/IceClimber'', the hitbox doesn't match the player while jumping which can often cause a player to go through floors while or not hitting enemies while being in the air.
* ''VideoGame/{{Bugdom}}'', a game that came free with the iMac, is another game with box-shaped hitboxes, which becomes rather obvious given the shapes of some enemies. This is most ridiculous when fighting non-flying bees, which both lack collision damage and essentially have invisible platforms hovering a few inches above their heads.
* ''Franchise/SonicTheHedgehog'':
** Tails' hitbox in ''VideoGame/TailsSkyPatrol'' is only one pixel high, but the enemies have larger hitboxes than they should to make up for it.
** One specific enemy from ''VideoGame/SonicTheHedgehog2'', Shellcracker in Metropolis Zone, has an outright counter-intuitive hitbox. When his spiked claw-on-a-chain is extended, hitting him near the base of the chain hurts you. When his claw is retracted, hitting him on exactly the same spot hurts him.
* ''VideoGame/TreasureMaster'' is all about this. First of all, your character's front hitboxes are very good and such, but however, if your back is at the enemy and enemy shoots you for an example, the projectile hits you from space where you could fill another protagonist's sprite. Enemies' hitboxes aren't bad, though.
* ''VideoGame/{{Canabalt}}'' invokes this on purpose for the player's comfort. Buildings extend a bit past their visible right edges, and crates' hitboxes are a mere two pixels tall.
* The boss Anubis Rex in ''VideoGame/PacManWorld'' is filled with this, as a result of the developers running out of time for proper playtesting.
* In ''VideoGame/SuperMarioWorld'':
** The giant Big Bubble enemies have really tiny hitboxes, making it hard to Spin Jump off of them.
** [[https://www.youtube.com/watch?v=0EIZB7h_pgE This actually caused a death glitch]] (demonstrated in the linked-to video by jumping over a key while riding Yoshi and getting smashed against a ceiling in the process) which could very well be an early version of ''VideoGame/SuperMario64''[='=]s infamous [[DisproportionateRetribution Killer Corner]] glitch.
* In ''VideoGame/SuperMarioBros1'':
** Super Mario's hitbox is normally twice as tall as standard Mario's, which makes sense. Crouching eliminates the top half of the hitbox, rendering it the same size as standard Mario's, which also makes sense. Crouching while underwater and then swimming causes Super Mario's hitbox to remain at half-height, causing enemies to pass through his upper half harmlessly, which does not make sense until you realize that you normally stay crouched when you jump this way, but there's no sprite for a crouched swimmer; so what you're actually doing is ''swimming while crouched'', but the lack of sprites causes a visual glitch.
** The collision detection. If Mario is rising, he will take damage from hitting an enemy regardless of whether he is on top of the enemy or below it. On the other hand, if he is falling, he will cause damage to the enemy (assuming it's not TheSpiny) regardless of whether the enemy is on top or he is. This can be confusing to players who are unfamiliar with the mechanics of the engine, and tool-assisted {{Speed Run}}s milk this for all it's worth.
* ''VideoGame/SuperMarioBros3'':
** In the Giant World, the hitboxes for giant clouds are rectangular, but the tile graphics are narrower on top than on the bottom. When standing on the edge of the cloud, it appears that Mario is hovering in midair.
** Bowser has some serious Hitbox Dissonance going on: the bottom half of his body does no harm whatsoever to Mario or Luigi. You can run to the middle of the screen, then stay still, crouching if Super, for most of the battle.
* ''VideoGame/SuperMarioBros2''. The player characters have life energy, but in order to connect the game to the rest of the series, they shrink when they only have one hit point left. But this does not actually reduce the hitbox.
* Some clever things have been done with ''Franchise/{{Metroid}}'' bosses' hitboxes. A good example is Nightmare in ''VideoGame/MetroidFusion''. To get past him in a 1% run, [[http://www.metroid2002.com/fusion/23-nightmare.php Sesshoumaru]] analysed his hitbox carefully, discovering that his front shoulder wasn't "there" at all, while a considerable area above and below his body ''was''. (There's a rough sketch at the link.)
* ''Franchise/{{Castlevania}}''
** In ''VideoGame/CastlevaniaPortraitOfRuin'', the castle has some tunnels half the height of Jonathan and Charlotte which must be negotiated with the Frog Morph spell. But the game has several unlockable characters who don't have that spell -- so some of them have hitboxes only one block high, allowing them to get through. It's bizarre to watch Old Axe Armor walking through a tunnel with half its body apparently inside the ceiling....
** ''VideoGame/CastlevaniaHarmonyOfDespair'' has a much less helpful problem. Richter and the Skeleton that you turn in to when you die stand slightly lower than everyone else. While this normally would be meaningless, a certain attack formation used by Beelzebub will hit Richter and the Skeleton in what is otherwise a blind spot unless you duck, while it'll completely miss everyone else.
* In ''VideoGame/SuperMarioWorld'' hacks, the n00b/newbie boss sprites have a 32 x 32 hitbox. Unfortunately, in many hacks, the graphics used for a boss powered by said sprite, '''doesn't''' have a 32 x 32 hitbox, with some examples in games like ''Drama Mistery'' 1 having bosses about half the size of the screen. Which means you have to figure out which exact part of the 'screen filling' boss is decoration and which is something you can hit. Another example can be seen [[http://www.youtube.com/watch?v=8yMWjQ-FYdM here]], where the Goomba King's hitbox is the crown, not the rest of the sprite.
* In ''VideoGame/ElastoMania'', the rider's body can pass through solid walls so long as his head doesn't collide.
* This is why the [[TheProblemWithLicensedGames licensed game]] for ''Literature/TheWizardOfOz'' is so horrendous to play. Because somehow, the collision detection for the platforms is incredibly messed up, so landing on them anywhere other than dead centre will send your character straight through them. What's more, that's not even getting into the problems with the enemy and character hitboxes, as the ''WebOriginal/AngryVideoGameNerd'' [[http://cinemassacre.com/2008/03/04/wizard-of-oz/ shows in his review.]]
[[/folder]]

[[folder:Puzzle Game]]
* ''VideoGame/TheTalosPrinciple'': The shock balls can interrupt lasers that pass just above them but shouldn't be interrupted according to their visible models.
[[/folder]]

[[folder:Real Time Strategy]]
* ''VideoGame/{{Allegiance}}'', being a team-based strategy/space combat hybrid, is especially susceptible to such problems, since flying ''every'' type of ship needs to be a fair experience for every player. Sometimes, the hitbox for a spacecraft with a complex shape oversimplifies the object's geometry a little ''too'' much. At the extreme, there is one ship that ''looks'' very small, with several thin wings, but ''acts'' as if all the wings were joined by solid surfaces, making what looks like a compact and difficult ship to hit an easy, bulky target in reality. There are also small, but annoying problems with the hit-boxes of a few space stations, which can be a problem since player ships often have to dock at these, and bumping into invisible walls when it looks like you should be flying into a docking bay is never fun. Fortunately, only a very few models suffer from these issues, and only require a little extra care. As the game is being developed by fans, there have been a number of attempts to create new hitbox models and fix these issues; some progress has been made, but the solutions aren't always easy to implement in practice. (Not to mention that in a few cases, some players have [[GoodBadBug gotten used to the hitboxes]], and don't want to see them fixed!)
* In ''VideoGame/DefenseOfTheAncients'', the Keeper of the Light's Illuminate spell uses an effect similar to the Shockwave spell in ''VideoGame/{{Warcraft}} III''. However, the area covered by the spell is a lot wider and somewhat longer than the visual effect, meaning that you can "dodge" the shockwave and still lose an assload of health.
** The Lich's ultimate, Chain Frost, uses bizarre logic in determining how and when it hits. To put it as simple as possible, the projectile deals damage when it reaches ''where the target was'' when the projectile flies to the target, then it bounces to another enemy ''from where you took damage''. So what happens with Chain Frost is that if you see the projectile flying towards you and you move about 6 feet away from that spot in half a second, you get hit once the projectile reaches where you were half a second ago ''even if it didn't directly touch you'', then the projectile teleports to your location and bounces to another enemy close to you, using the same logic. Try wrapping your head around that one.
* In ''VideoGame/LeagueOfLegends'', Morgana's Dark Binding hitbox was infamous for being much wider than the projectile, which made it both easier to land in the open and harder to aim through minions. Leona's [[GrapplingHookGun Zenith Blade]] didn't reach as far as the animation, which was a problem because missing it left her useless for several seconds. Morgana was fixed, Leona was "fixed".
** And then there's the [[EverythingIsAnIpodInTheFuture iBlitzcrank skin]] whose game deciding Rocket Grab has a smaller projectile than the regular Blitzcrank or any of his other skins but the same hitbox, making it much more likely to land than if you didn't [[BribingYourWayToVictory buy the skin]].
[[/folder]]

[[folder:Roguelike]]
* Flies and spiders in ''VideoGame/TheBindingOfIsaac'' have rather large hitboxes, making them far easier to aim at and only slightly harder to avoid. The real pain comes from [[{{Bizarrchitecture}} the walls]] [[MalevolentArchitecture themselves]], which have a bug that can sometimes make bits of the wall jut out slightly and trip you up.
[[/folder]]

[[folder:Rhythm Game]]
* {{Rhythm Game}}s have a variation of this called the "timing window", which refers to how much a player can be off from the exact beat a note falls on when he/she hits that beat (graphically, how much of the note needs to overlap with the "hit zone", assuming a constant speed) for the note to be counted as a "hit". Some games, especially those created by Harmonix (''Amplitude'', ''VideoGame/GuitarHero'', ''VideoGame/RockBand'') only differentiate between "note hit" and "note missed", while other games (most VideoGame/{{Bemani}} games) have several levels of timing windows that award different amounts of points, or differentiate between a "close miss" and a "way off miss" by punishing you more for the latter. The exact width of these timing windows differs widely between games (and sometimes within the games), and you can guarantee that the type and width of these timing windows is a hot topic on forums where these games are compared. The dissonance comes in two forms: firstly, if the game isn't calibrated to the TV, the hitbox will be disjointed. Secondly, in almost all cases, the timing window is, appropriately enough, based on the amount of ''time'' you can be off by, not distance, so if the notes are moving really fast, you can afford to be more visually "off" ("too big") than if they're moving really slow ("too small").
** ''VideoGame/RhythmHeaven'' is a compilation of mini-games that are all hit-or-miss timing windows, but the windows seem to vary for each mini-game. Generally, the simpler the game, the harsher the timing window. Most of the games have ''either'' a near-hit or near-miss animation, but few if any have both. Not to mention the Space Shooter endless game that cuts down the timing window as you go.
** ''[=O2Jam=]'''s timing windows are out of whack. First, the timing windows get faster as the song's BPM goes up. Second, they loosen when you use speed modifiers. Conclusion? ''You get punished if you're more comfortable with lower speed mods than higher speed ones.''
** ''DJ Max Technika'' also suffers from faster songs having smaller timing windows.
*** ''VideoGame/{{DJMAX}} Trilogy'' has the TECH stat, which ''[[GameBreaker expands the timing windows]].''
** The GAMBOL AscendedGlitch in ''VideoGame/BeatmaniaIIDX'' deserves a special mention. Originally, it was one of the easiest charts in the game, but a bug caused it to have much tighter timing windows than any other song in the game, making it easy to clear but extremely hard to score well on it. The song has since been "fixed" to use the standard timing windows with the same chart on Normal difficulty, but retains its Hyper difficulty with the bugged timing windows, as well as having an added Another difficulty chart in the [=PS2=] version of ''IIDX 11: RED'', with the ''exact same chart'' but with ridiculously small timing windows that make it quite hard to clear. Newer installments in the series now have the "GAMBOL Judge Hyper" and "GAMBOL Judge Another" EasterEgg codes, which allow you to use the tightened timing windows on ''any song at all''.
** Fortunately, the latter incarnations of ''VideoGame/GuitarHero'' allow you to manually synchronize audio and visuals with controller input. ''[[VideoGame/RockBand Rock Band 2]]'' (and later) guitars have light and sound sensors that are used to precisely measure the audio and video lag.
** The hit boxes in ''VideoGame/GuitarHero'' and ''VideoGame/RockBand'' are a point of contention among high-level players. In general, the timing window in Rock Band is pretty moderate, but ''the window shrinks'' when notes are placed very close together, which leads to FakeDifficulty on the hardest songs in the game (this is lessened in ''Rock Band 3'', which has a new mechanic for extremely fast and\or imprecise strums and trills). ''Guitar Hero'', on the other hand, is known for timing windows so big that "rhythm" is no longer a necessity. This is generally compensated for by including songs that are, for lack of better words, "walls of skittles".
** There are a few jarring instances in the ''VideoGame/ParappaTheRapper'' games. This is the reason that [[PlanetHeck Stage 6]] of ''VideoGame/UmJammerLammy'' is one of the most [[IncrediblyLamePun hellish]] in the series; even nailing the notes perfectly will drop you down to a "Bad" rating. You ''won't'' get through without freestyling. The first ''Parappa'' game was notoriously difficult due to how strict the timing windows were and it made stage 5 ThatOneLevel due to absurd amount of buttons needed to be pressed back to back with near precision timing. The sequel made the timing windows much more forgiving.
** In [[Videogame/{{Osu}} osu!]], beatmaps have OD and AR values, OD determines how small the timing windows are, and AR determines how much time it is between a beat appears and the moment you have to press it (also changing the approach circle speed). Normally, maps with high OD also have a high AR, so timing feels right. But there are some beatmaps (specially older ones) that have a high OD and low AR, leaving you with no precise enough visual cues to have decent accuracy: If you see the approach circle is exactly over the beat circle, you can still receive a 100 (when the max is 300), since the approach circle takes more time to pass over the pixel-width border of the circle than the time window's length. Also, with maps with high AR and very low OD (not commonly ranked) or easy ranked maps, you can get a 300 even if the approach circle is several pixels off from the beat circle.
** In ''VideoGame/LoveLiveSchoolIdolFestival'', some members have skills that loosen the timing windows for a few seconds, which have a chance to activate every ''x'' seconds, Perfects, Combo, or notes.
* In ''VideoGame/CrossBeats'', the Master chart for the song "魔界村 (平地BGM)" has a series of flick notes which are all in the same direction and are close enough in location that each one has its hitbox overlapping with the next, making it very easy to prematurely hit the next note in the sequence. To add insult to injury, they're spaced ''just'' far apart enough in time such that doing so will break your combo.
* In ''VideoGame/DanceDanceRevolution'', the song "Bag" is 130 BPM but scrolls at half speed. It's also full of triplets, leading to arrows spaced 1/6th of a beat apart in the chart. But at the time the song was introduced, the engine couldn't handle a denominator of 6, so everything got rounded to the nearest 1/16th of a beat. This meant every individual timing window could be off by up to 1/32nd of a beat, which at 65 BPM was 29 milliseconds when the Perfect window is 33 milliseconds. This turned into an AscendedGlitch in newer editions, where Bag has its chart fixed on Expert, but gained a new Challenge chart consisting of the Expert chart with the old, broken triplets.
[[/folder]]

[[folder:Role Playing Game]]
* ''Franchise/TheElderScrolls'':
** This is part of what makes the infamous Cliff Racers of ''[[VideoGame/TheElderScrollsIIIMorrowind Morrowind]]'' so reviled as GodDamnBats. When alive, their hit box is an inexplicably small portion of their body. Fortunately, getting below them and aiming for center of mass is pretty reliable, but they are still hell for archers and spell slingers at a distance. Then when they die, this is reversed. You'll need to dispose of their corpse in order to access any items or other corpses nearby because their dead body "container" selection box is inexplicably massive.
** In ''[[VideoGame/TheElderScrollsVSkyrim Skyrim]]'', the (airborne) Ice Wraiths can be damaged by hitting the apparently empty space beneath them. There's also some occasional examples of arrow hitboxes and target hurtboxes not meeting up like they should, which are frequently pointed out to the player in long, loving detail as your shot gets a slow-mo special killcam, perfectly articulating the arrow's flight through the air, through the enemy's render, and passing harmlessly out the other side, having completely evaded anything that would have caused the CPU to register a hit.
* ''VideoGame/{{Fallout 3}}'' and ''[[VideoGame/FalloutNewVegas New Vegas]]'' suffer from this with the surrounding static models and their collision meshes. There are many occasions when one's line of shooting is very close to what is seen as an obstacle, but when one actually fires, they hit an invisible barrier, thus not hitting the target and subsequently alerting them to your presence and location if you were sneaking. The worst offender is the derelict subway car mesh.
* ''VideoGame/{{Fallout 4}}'' has the same issue as the two prior games. Bethesda improved the shooting mechanics by a large amount but didn't update the environments to compensate - your bullets run into invisible walls all too often.
* Fighting against other hunters in ''VideoGame/PhantasyStarOnline'' is harrowing, as you need to land a blow directly in the center of their bodies in order for it to register, unless you're using a gun.
* The hitboxes in ''VideoGame/PhantasyStarOnline2'' range from extremely precise to completely broken. Dagans and Predicahdas are a few glaring examples of "broken", as their seemingly short-ranged claw swipes can connect with you from a few meters away in any direction, and in the case of the latter, can even connect if they're aiming in the opposite direction of you if you're close enough to their backs.
* ''VideoGame/TalesOfEternia'' has downright ''terrible'' hitboxes on the enemies, especially compared to the rest of the series. One can be right next to an enemy, slashing away a dozen times, and only hit maybe once or twice while the other attacks go right through them, and if 2 or more enemies end up overlapping, the attacks will hit one enemy and not the others. However, the PC hitboxes don't have the same issues for enemy attacks, meaning that the enemies can easily interrupt your attacks, so keeping enemies in hitstun for long like in the other games is downright impossible.
* ''VideoGame/DarkSoulsII'' often has hitboxes for attacks come out [[http://i.imgur.com/0Mdj97G.jpg while the attack should still be winding up]] and/or your hurtbox [[http://i.minus.com/iVXzI0EtCoSSi.gif lagging behind your visible model]]. This is extremely noticeable for any enemy attack that triggers animations involving the player model; you'll appear to dodge it then be teleported to where you'd be if you hadn't.
* The Ceaseless Discharge from the ''VideoGame/DarkSouls'' has a very wide hitbox for its attacks, especially its flail pound, and often clips you even if you're nowhere near the impact point.
* The Blood-starved Beast and the Bloodletting Beast from ''VideoGame/{{Bloodborne}}'' have rather wonky hitboxes on their ground pound attacks - to the point they can sometimes hit you even if you're ''behind'' them. Amygdala also has some odd leg hitboxes, which tends to create problems when it uses its leaping attacks and clips you as you're rolling out of the way.
* ''VideoGame/NeverwinterNights'' uses [[RealtimeWithPause turn-based mechanics with a realtime user interface]], occasionally leading to ''temporal'' hitbox dissonance: An attack that hits where you were standing two seconds ago may very well deal damage to you.
* {{Averted}} to [[NotTheIntendedUse amusing effect]] with ''VideoGame/KingdomHearts2'''s Gummi Ship minigame. Your hitbox is determined from the actual shape of your customizable gummi ship, but the enemies still aim for the center, so if you build a donut-shaped ship, almost anything that isn't an explosion or grapple attack will [[GameBreaker go straight through you, harmlessly.]]
* ''VideoGame/DivinityOriginalSin'':
** Prior to the enhanced edition, the hitboxes for backstabbing were not indicated, and were quite small. This resulted in many players getting frustrated as they are clearly behind a target yet the game still has them regularly attack. Fortunately the Enhanced Edition fixed this.
** Sadly, Enhanced Edition didn't fix a few instances of this happening in other cases. Some AreaOfEffect attacks would give you a full hit when your character was two pixels to the side. Very small enemies are also [[GoddamnedBats annoying to fight]] because their hitboxes are so small the game might mistake an attack click for a move click.
** Another very common issue with Original sin is when you interact with shopkeepers or non-player characters covered in an area covered with items. Because their hitboxes are limited only to their models, it's very common for the game to assume you wanted to click on an item nearby rather than the shopkeeper themselves. Fortunately, in a shop, instead of your character attempting to stuff the item into their pants, the shopkeeper then opens up a dialogue with you asking if you would like to purchase that item.
* The same happens in ''VideoGame/DivinityOriginalSin2''. Be careful in towns where the game might think you meant to steal a bowl of water the NPC was standing next to when you meant to talk with them. Also be very careful if you're walking under something like a roof - sometimes you might accidentally click on something and the game assumes you want to stick an empty cup in your pocket. Fortunately, the game has some more generous combat hitboxes than the previous game, and you can fire at the ground.
[[/folder]]

[[folder:Shoot Em Up]]
* Some BulletHell games (such as ''VideoGame/{{Espgaluda}}'') feature a tutorial at the beginning which, among other things, explicitly shows the ship's/character's hitbox. Usually represented by just a small circle in the cockpit/engine/torso and with a flashing arrow labeled "HIT".
* The 'graze' mechanic in many BulletHell games involves two hitboxes- one very small (sometimes just a few pixels), which is fatal if struck, and a slightly larger one that gives extra points if bullets pass through it. This encourages players to take extra risks by getting closer to the bullets as they weave through the patterns.
** ''VideoGame/{{Raiden}} DX'' has the graze bonus, despite being a non-Bullet Hell shooter with a ship-sized hitbox released in 1994.
** ''VideoGame/RaidenFighters'' brings the hitboxes closer to Bullet Hell-size, with the Slave having the smallest. However, if you're using the Judge Spear version of the Slave (which has the Judge Spear's [[GameBreaker game-breaking]] bomb), your movement speed becomes so fast that grazing becomes dangerous and impractical.
** ''Raiden IV'' also downsizes the hitbox, to accomodate the denser enemy fire, and also has a grazing bonus.
** In ''VideoGame/BorderDown'', the hitbox in the middle of the ship is small and enemy shots can pass through like other shmups. However, the ship will blow up if ''the ship itself'', not the hitbox, runs into anything solid. Almost every other shmup these days will allow the player to put almost half of whatever they're playing as in walls and other obstacles as long as it doesn't hit the hitbox.
** In ''VideoGame/{{Ikaruga}}'', knowing the exact position of your hitbox is vital to getting the [[PacifistRun Dot Eater rank]]. Since you're not allowed to shoot your weapon for this rank, you have to be very precise in your positioning in order to get past walls, blocks, and enemies you're normally suppose to shoot to safely progress.
** ''VideoGame/RadiantSilvergun'' has a mode you can unlock after playing enough hours where the hit boxes of your ship and the enemies become visible.
** ''VideoGame/KnightsInTheNightmare'' uses this version, awarding bonus experience for it.
* ''[=rRootage=]'' and ''[=Parsec47=]'', unusually, explicitly show the hitboxes of not only the player's ship, but also the ''bullets.''
** ''VideoGame/{{Genetos}}'' has a similar feature, but it's optional, because it can be distracting. It's off by default, but you can hit G to toggle it.
* In ''VideoGame/StarwardRogue'', your mech's hitbox is only a small portion of the center. This really helps in surviving all the intense {{bullet hell}} patterns.
* Both your ship and some asteroids in the original ''VideoGame/{{Asteroids}}'' had issues where they could appear to be hit on the side and survive, which makes this OlderThanTheNES.
* ''VideoGame/TransformersConvoyNoNazo'' has this in spades. To begin with, enemy hitboxes are far larger than their graphics might suggest. On top of that, your own character is a large robot to begin with, and the game is extremely biased when it comes to hit detection - your own projectiles have to hit enemies dead center to hit them (and they're often very small to begin with) while enemy projectiles only need to barely graze you to score a hit ([[OneHitPointWonder which is enough to kill you]]).
* ''VideoGame/BangaiO Spirits'' has the [[BatterUp Bat]] weapon, which has a hitbox larger than the range it swings through. This means you can swing at enemies a few feet away from your bat.
* The ''VideoGame/{{Touhou}}'' series does this in a number of ways:
** The playable characters' hitboxes are quite a bit smaller than their sprites. Focusing will show you it, except even that is a bit larger than it actually is -- especially for Reimu, who has a smaller hitbox than everyone else (something that fans joke is a [[HeartIsAnAwesomePower combat application]] of her [[WhatKindOfLamePowerIsHeartAnyway power to eat sweets and never get fat]]).
** The bullets' hit-boxes themselves also tend to be tinier than their sprites (for example, you can safely fit the characters' entire hit-box into the sprite of the bigger bullets, or go through what seems to be a solid wall of rectangular amulets). This makes learning the hit-box of each type of bullet an important part of the learning process. There are, however, certain exceptions:
*** Patchouli's "Metal Fatigue" bullets are larger than normal for that type of bullet, greatly screwing up hardcore players that memorize exactly how large they normally are.
*** Knives have oddly shaped hitboxes that are larger than the sprite. Well, normally larger than the sprite. For some reason, later games have occasionally messed with the sprite to make it more accurate, while leaving the hitbox alone. They're still quite dangerous to players used to bullets having small hitboxes.
*** ''Mountain of Faith'' has Kanako's extremely long oblong bullets during her first Spell Card attack, which appear to have ''rectangular'' hitboxes that make them absurdly big around the corners.
*** In "Imperishable Night", Mokou's "Honest Man's Death" features a laser. The model of this laser forms before its hitbox does, meaning that you have to move into the laser in order not to be killed by it.
** Enemies' [[CollisionDamage collision boxes]] are quite variable, though finding this out tends to be dangerous. While they're normally the same size as the enemies' hitbox, it's been known to get smaller or disappear entirely during patterns that force you to get close.
** The fanmade ''VideoGame/SuperMarioWorld'' knockoff, ''Super Marisa World'', [[http://en.touhouwiki.net/wiki/Super_Marisa_World:_Bosses#Kaguya_Houraisan during the Kaguya battle]].
** Bosses all have the same hitbox regardless of whether this makes sense for the sprite. The sole exception are a few of the bosses early in ''Perfect Cherry Blossom'', who ended up with unusually small hitboxes (which the fandom got backwards and ended up thinking that the one with a normal hitbox was fat).
** Ichirin is so much smaller than Unzan (a cloud youkai) it's joked that [[http://danbooru.donmai.us/posts/518740 she]] serves as [[http://danbooru.donmai.us/posts/913715 his]] hitbox.
* In ''VideoGame/{{Berzerk}}'', [[FloatingLimbs the gap between the humanoid's head and body]] is not part of a hitbox; a horizontal shot that goes through it is harmless.
* ''VideoGame/{{Gradius}}'': The Vic Viper's hitbox is located near the rear of the sprite (where the "engines" of the ship would be, presumably); this means that you can shove the guns of the Vic Viper into parts of bosses hidden behind shields and achieve quick kills that way. With regards to [[DeadlyWalls walls]], if your basic shots can go through an opening, then your ship can go through, regardless of whether its sprite is clear of the walls.
[[/folder]]

[[folder:Sports Games]]
* Several instances in ''VideoGame/ArcStyleBaseball3D'':
** Infielders will somehow tag you out if you pass running by them. ''Behind their back, without turning around''. It really challenges the WillingSuspensionOfDisbelief.
** While pitching a forkball, you can make the ball go through the dirt or home plate, as the ball icon will disappear.
** Fielders can merge with each other and [[GameBreakingBug with the outfield walls]] when diving for the ball.
[[/folder]]

[[folder:Survival Horror]]
* The classic ''Franchise/ResidentEvil'' games on the Playstation has weird hitboxes for zombie dogs; even though they are smaller than the player character, just shooting straight at them is enough to score a hit, even though realistically, you'd have to aim downwards to land a shot. The developers likely made the dog's hitbox larger on purpose for the convenience of the player so that they don't have to worry about making precision aim. Due to the game's 3rd person perspective it did also have an "aim assist" built in. You only needed to have your model facing any enemy's general direction to score a hit, the assist handled the actual gun "aim" in a cone. So it can be taken as the assist is aiming down while you're facing forward.
[[/folder]]

[[folder:Simulation Game]]
* Ships in the first two ''VideoGame/WingCommander'' games simulate 3D objects flying freely through space by using a series of sprites drawn at various angles, with the appropriate sprite angle displayed in relation to the player's ship. The hitboxes are rectangular, no matter what the actual sprite looks like. This is especially noticeable when you are firing at a flat-shaped enemy fighter that is aligned diagonally, and you can hit it at the "empty" corners of the hitbox.
* The ''Videogame/MechWarrior'' series traditionally has this for the sake of game balance on the cockpits of its HumongousMecha, which were designed for a turn-based [[Tabletopgame/BattleTech tabletop boardgame]] where hitbox sizes are irrelevant. Typically, a [[SnipingTheCockpit mech's cockpit can only be sniped]] from the front, on a glass panel directly in front of where the pilot would be sitting, which prevents mechs with large canopies from becoming deathtraps. This presents some particularly silly looking situations like mechs with side windows shrugging off lethal Gauss Rifle slugs because they hit the side window, which counts as a heavily armored torso section.
** Mechs with particularly odd silhouettes typically suffer from hitbox dissonance as the head-torso-arms-legs SubsystemDamage system was designed for humanoid mechs. The Cauldron Born in ''Mechwarrior 4'' gets a double dosage of it, thanks to its asymmetrical aircraft-like body, where the entire left side of the mech can be shielded by the offset cockpit nose, which counts as either a center or right torso depending on where it is hit.
** ''Mechwarrior Living Legends'' had a number of oddities. The Uziel had its cockpit armor completely buried in the torso armor for a few months, making it immune to any non-explosive weapon. Until version 0.7, small vehicles like the Chevalier tank and Harasser hovercraft took absurd amounts of damage from explosive weaponry thanks to SplashDamageAbuse causing a single rocket to damage ''every'' armor section
** ''Mechwarrior Online'' has some particularly terrible hitbox dissonance on its terrain which is especially noticeable on city and industrial areas. On most structures, the hitbox extends at least a meter beyond the physical object, leading to huge amounts of frustration and wasted shots on maps like HPG Manifold, which takes place in a greebled-up industrial area.
* A weird one in ''[[VideoGame/{{X}} X3: Terran Conflict]]''. The auto-aim targets the center coordinate of a ship's model. This works fine most of the time but the Terran Tokyo carrier and Mobile Mining Base-Ship have long, narrow, asymmetrical hulls, such that if you attack from above or below, the geographical center of the ship is floating in empty space. The hitbox isn't ''wrong'' per se, it's just not where the computer thinks it is. A handful of stations have similar issues, making them obnoxiously great at 'tanking' damage from your [[ArtificialStupidity brain-dead]] SpaceFighter pilots.
* This was a particular issue in many early flight simulators, such as ''Air Warrior''. For example, Although the P-38 Lightning in ''Air Warrior'' had a very slender profile, because of its broad wingspan it had an ''enormous'' hit box. This was exacerbated further by its twin-boom design; the hit box covered the ''entire'' aircraft, meaning shots that would have missed it between the booms would instead count as hits.
[[/folder]]

[[folder:Tabletop Games]]
* At one point in ''TabletopGame/{{Heroscape}}'' a model's cloak was not considered to be a hitbox. This had to be changed in later sets, as players were abusing the rules by turning their models' cloaked backs to the opponent and claiming they were now immune to fire.
* In ''TabletopGame/{{Warhammer}}'' and ''TabletopGame/{{Warhammer 40000}}'', a model's base is treated as its hitbox for purposes of melee combat, area effects, and such. The result is that, for example, a Gretchin (shrimpy little goblin creature) and a hulking Ork have the same hitbox, and a hitboxes may suddenly change (as when Terminators were moved from 25mm-diameter bases to 40mm-diameter bases).
** Previously in 4th edition of 40k, for the purposes of shooting the Model was considered to be a cylinder, as tall as it needed to be for the purposes of being able to be shot at or not (so as long as you see part of the base, you saw the entire model). This was changed with the 5th edition, where True Line of Sight took place and you had to physically see the model in question. This fixed some abusable problems, at the cost of introducing others. Since many players would model their commanders and characters on massively scenic bases, which would make them tall as hell, those commanders were now easy targets. Moreover, the 5th edition introduced fliers, vehicles that are mounted on a massive clear pole on their own bases, which makes getting cover for them incredibly hard[[note]]6th edition fixed by removing a flyer's ''need'' for cover; anyone trying to shoot a flyer without dedicated AA weapons gets a huge accuracy penalty[[/note]]. It also caused the modelling community much headaches, as a lot of aesthetic choices on the modeler's part are now against the rules, as it made the miniature physically smaller (and thus harder to actually hit) while others are being mothballed because they gave the model such height it was impractical to field them now.
** A lot of non-imperial vehicles suffer from this issue as well, due to the fact that instead of an all-encompassing "toughness" value for calculating damage, Vehicles have varying Front, Side and Back armor values. This is normally not a problem on boxy Imperial Vehicles (where it's very clear where the rear is) but very hard to pinpoint on something [[http://www.games-workshop.com/resources/catalog/product/600x620/99120104023_WaveSerpentNEW_01.jpg like this]][[note]]The problem with it is that technically all of the engine should be considered the "rear", as that might have been the intention since it's basically shooting out the engines. It also makes sense because the front and side armor on any Wave Serpent-based vehicles are always the same, implying that they are the same piece. However this means you can see the "rear" of the vehicle from the sides, which makes them massively vulnerable. On the other hand if you assume that the only flat side on the rear is the "rear" of the vehicle, it's rear hitbox is hilariously tiny compared to the rest of the thing. Currently there is no perfect way to resolve this, and most people have to agree beforehand what constitutes a "rear" on most eldar vehicles[[/note]].
** Cross-edition models can have this sort of issue. The most notable ones are the Terminators and Wraithlords, who all went up a base size with the newer models. The older models on older bases are still technically legal, but this provides them with a massive advantage against their modern counterparts (especially Terminators, since they now occupy much less space, meaning they are much more easily used in deep striking without mishaps). This also extends to models released in different times; A bloodthirster released in the early days of 40k only came with a 50mm square base, while a newer one (still the same mold) comes with a 60mm round base. Same goes for the Daemon Prince, which initially came on a 40mm round base but now has been "standardized" to the 60mm base every other small Monstrous Creatures use.
* The ''TabletopGame/IronKingdoms'' games use a similar mechanic than pre-5th edition 40k did, ie. the height of the model is independent of the actual physical model and is determined purely by base size. Models with a smaller base will not block line of sight to models with larger bases. This can lead to some weirdness if you have a model particularly short or tall for it's base size; for example the enormous Behemoth warjack will be completely hidden from line of sight if it hides behind another heavy warjack, despite being almost 50% taller, as they both are on the same size base.
* ''TabletopGame/{{Malifaux}}'' uses a similar mechanic to the ''TabletopGame/IronKingdoms'' games (above). Each model has a defined base size (30mm, 40mm, or 50mm in diameter) and a Height stat describing its height in inches. As far as the rules are concerned, every model is thus a cylinder with those dimensions regardless of the actual model's dimensions. While this works from a pure rules perspective, there is often a great discrepancy between a model's stats and its actual physical size. This includes models that can barely fit on their base, but is most commonly seen in models whose height has only the vaguest connection to their Height stat. There are many instances where a model is fully an inch taller than another, but their Height stats are the other way around.
[[/folder]]

[[folder:Third Person Shooter]]
* The N64 ''Film/MissionImpossible'' game suffered from a quite disjointed hitbox, especially compared to ''[[VideoGame/GoldenEye1997 GoldenEye]]''. However, besides the common cases of bullets that should hit the enemy not having an effect, the biggest problem seemed to be with the individual hitboxes indicating the damage zone. The very common result of aiming anywhere besides the head was: the shot person would be shown flinching, but it wouldn't seem to have a damage effect, and a whole clip of a heavy pistol could be emptied into what seemed to be the lower half their center mass (or arms, legs, etc.), and then they would shoot back unfazed as you were reloading. This was even more jarring when you used what would otherwise be a OneHitKO dart gun, and was a major contrast to when you shot them in the head with even small handgun and they ''[[BlownAcrossTheRoom do a backflip]]''. According [[http://www.archive.org/details/MissionImpossible_IL_10908 to this author]], "embarrassing hitbox and bullet detection problems" were a factor in that game.
* ''VideoGame/OrcsMustDie'' has a rather unusual case of the hitbox ''being'' the size of the enemies' models breaking the WillingSuspensionOfDisbelief, especially with the [[BrawnHilda "Ball and Chain"s]]. You can attack their EpicFlail's ball and they'll take as much damage as if you had attacked [[GroinAttack their other part]]. The hitbox dissonance also causes such strange things as enemies frozen in the middle of an attack being encased in a tiny ice cube placed ''between'' itself and its weapon.
[[/folder]]

[[folder:Web Games]]
* ''{{Website/Neopets}}'' released a game that, as part of a plot, was a re-skinned version of an older game. This is notable because the original game sprite was significantly smaller than the re-skinned sprite, but the hitbox remained the same. This was ostensibly a good thing until you realize that the center of the hitbox was located several pixels ''below'' the sprite itself, meaning that you had to fly higher than you thought you would to keep from dying. Bear in mind that this game is designed to constantly have your character descend unless you're consciously rising, so there's significantly more danger from scraping the bottom of the screen than the top to begin with.
[[/folder]]

!!Non-Video Game Examples:

[[folder:Live Action TV]]
* Came up as a plot point in an episode of ''Series/{{CSINY}}''. [[spoiler:An UsefulNotes/{{Xbox}} used in a ''VideoGame/GearsOfWar 3'' tournament had been hacked to give one player a much smaller hitbox, and everyone else a much bigger one.]]
[[/folder]]
[[folder:Web Animation]]
* The hitbox dissonance in ''Dark Souls III'' is parodied in ''Machinima/TheGmodIdiotBox'''s "Dark Souls III: WTF Are Hitboxes Edition" sketch. A mushroom monster pokes a fist into thin air ''yards'' away from the player character, sending them flying into a mountainside.
[[/folder]]

----