-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Players can get stuck inside the "Coop Droppers" #2518
Comments
I thought the problem were fixed tho... |
It is fixed if you just fall down. But do to the fact that you can move while falling it is still possible unfortunatly. |
Interesting, thanks for reporting it. |
Does this still happen? |
Tested with the PRL 4.36.1 and i can confirm that this issue still persist. |
Not sure why this has been so hard to fix...why can't they use the same closing logic as the droppers in the spawn room/checkpoints? |
Yeah, that seems to be the most reasonable to do in this case. Not sure why Coop Droppers should have a different closing logic... |
I'm not actually sure if the logic is any different, I haven't checked. It just seems weird that this would repeatedly be a problem even though the normal spawn room/checkpoint droppers have never had the same issue. |
Seems like this might be fixed actually, there seems to be a clip stopping me from moving over far enough to hit the side. This isn't really a proper fix though, it can still happen when noclipping, or probably in some other cases. |
Okay I figured out what's going on here, for some reason the triggers are only considering players to be touching them if the player's origin is inside the trigger, rather than any part of their bounding box. So that causes the dropper to close too early. |
Okay, I'm amazed this has never been found before now...but it looks like triggers don't work right in rotated instances, it effectively treats the hitboxes of detected objects as if they have the same rotation. |
It's not a problem for most objects since their bounding box is centered on their origin, so when rotated it ends up close to if not exactly the same, but since players have their origin at the base of their bounding box it breaks. |
Regardless of exactly what's going on, it seems like the fix in BEE would be to reorient these instances to start in a ceiling orientation, so the triggers don't need to be flipped. |
I figured out what the trigger bug is. It is rotating your bounding box and using that for trigger detection like I originally thought, except your real bounding box also has to be touching the trigger's axis-aligned bounding box for it to activate. For rectangular axis-aligned triggers, that means the detection area is effectively equal to the intersection of your real bounding box and rotated bounding box. That's what was going on with the single checkpoint - with the instance rotated 180 degrees vertically, the intersection of the two bboxes would just be a flat rectangle along the bottom of your player. Things get weirder for triggers that aren't rectangular and axis-aligned, since it becomes possible for you to not be touching any part of the trigger but still have it activate. If you've ever noticed the entry door trigger activating well before you actually touch it, this is why - your rotated bounding box extends forward into the trigger, and since the trigger wraps around the sides of the door as well, your real bounding box intersects its bounding box, so it activates. That also means that this doesn't happen anymore in P1 style, since I updated the door/corridor instances to default to a wall orientation. Not sure how well I explained this, I could make a video showing the bug in more detail if necessary. This is a really interesting bug, and I'm honestly surprised that nobody seems to have found it before now. We'll definitely want to document this on the VDC, and keep it in mind for future BEE items. |
If you respawn at the custom "Player dropper" and move while falling down the dropper you can hit the edge of the inside of the dropper. It may stay open but once you try to jump out it will close and gets you stuck.
The text was updated successfully, but these errors were encountered: