Post

@classicsoniccode.bsky.social

So, the 2013 remake of Sonic 2 made a change to the way the claw attack's hitbox works.

btw the chain link's hitboxes are also the reason why you always get hit when trying to jump on it. For some reason they're 32×32, the way the sub-objects are created is messy which is why they reuse the claw's hitbox size (they seem to have forgotten to change the size for the chain's boxes).

Liliam 🏳️‍⚧️

@liliambean.bsky.social

Honestly they might have forgotten to clear the collision flags.

Plutiedev

@plutiedev.com

It's weirder than that: it first creates an object for the claw, then creates each chain link *by copying the claw into a new object and modifying it* (which is why they inherit its hitbox size). Dunno, chain hurting you makes sense (it's moving at high speed)… just not with that range.

17/10/26, 4:44 am0 reposts0 likes

Under the Surface of Classic Sonic

@classicsoniccode.bsky.social

Not quite true. It actually spawns all the pieces in a loop in one go. Each piece is given the same subtype value of 0x26, which is passed into a function sets up their sprites and collision. The piece type is checked to set the correct sprite during initialization, but not the collision.

Plutiedev

@plutiedev.com

I guess I was thinking on that beq.s loc_38198 under ObjA0_Init. It seems that code runs for both the claw and the chain and the code below adjusts the sprite and offset for the chain links, could have easily changed the collision size there too.