A bounding box (collision) decision doesn’t correlate to “polish”.
Our server software uses axis-aligned bounding boxes. This means that the boxes are always “square” in the case of an entity that can freely move position. As they are axis-aligned, these boxes cannot be rotated.
Thus, we have to choose a bounding box that makes sense from all angles. It can be shrunk slightly, but the minimum bounding box must account for the seat positions to ensure you do not clip your passenger through the wall(s).
Nomatter which way you are facing, if you have two small hitboxes to the front and back of you, they create a smaller left-right hitbox, while also making sure the players do not clip into walls! And they do not have to rotate
correct me if I’m wrong, but the ender dragon in vanilla has multiple hitboxes and idt there are any problems there. This def feels possible within the limitations of mc, but devs would know better than I would.
i believe those hitboxes are actually hurtboxes, by that i mean boxes that dont calculate collision. that’s probably why boxes show up for entities even when they are riding something, it’s their hurtbox. (this time I mean a box to detect damage (boxes are weird))
it really wouldn’t be too hard to implement multiple hitboxes into minecraft but of course, the hive would have to do it themselves which would either make the client laggier (running calculations on client end) or making the mount less responsive/laggier (sending input for server to compute, then moving it).
I’m all for this suggestion so idrk why I’m saying this but yeah, it probably wouldn’t be as simple as that (although, there are plenty of actual, colliding hitboxes around minecraft, infact i’d say most hit boxes aren’t cubes)
Yeah I kinda agree with you here. It feels like Hive has gotten super laggy recently, although that may just be my iPad slowing down (I’ve only had it for a year and it already has problems -_- ) The broomstick would definitely be a special case, but I’m sure they could fix the problem. There’s just not a big enough reason for them to do it, other than being annoying
Bump. I’m sure this bump is well within the guidelines of bumping. Jokes aside, this issue still really really bugs me I really wish Hive would fix it. Yes, I look like an annoying little brat, but 10 dollars is a lot of money, and it makes me sad the mount isn’t quite right
Tbf, I suppose they could even just shrink the hitbox so the “brush” bit (the black part at the back end of it) isn’t included and keep it a cube just with that amount of length cut off to make it ~2 blocks thinner. That would be the most simple thing the hive could do imo.
Yo guys remember this topic??? Still a problem it just annoys me so much. This mount has such great visibility and yet it CANNOT fit through a small gap. Sadness.
While I personally do not experience this problem (as I do not actually have the mount lol), it makes sense to me that this is an issue. Just overall, even though it’s a lot of work, the Hive should add custom hitboxes to every mount, especially smaller ones like this.