Page MenuHomeFeedback Tracker

Building is missing collision and you can exploit/hide in structure
Closed, ResolvedPublic

Description

There is an industrial area in Novaya Petrovka where one of the buildings is missing some of the collision box. You can hide inside the stairs and other players will not be able to see you. I stumbled across this while looting the area but I have not seen any players abuse this structure (yet). {F32565}

Details

Legacy ID
3957418910
Severity
None
Resolution
Duplicate
Reproducibility
Always
Steps To Reproduce

The building has stairs on opposite sides. The side that is facing Northwest is the side where the collision doesn't exist. Walk up the stairs and you will go through the surface but will stop before allowing to fully enter the building under the floor. You can also clip along the NW edge of the building and around the southern edge.

Additional Information

I've included a screen shot and map location of the building (blue highlighted area)

Event Timeline

alhaknslash edited Additional Information. (Show Details)
alhaknslash set Category to category:structures.
alhaknslash set Reproducibility to Always.
alhaknslash set Severity to None.
alhaknslash set Resolution to Duplicate.
alhaknslash set Legacy ID to 3957418910.May 8 2016, 11:43 PM
Geez added a comment.Sep 9 2015, 3:09 PM

Hello alhaknslash.
The screenshot probably did not upload. Could you try uploading it again?
Regards,
Geez

Hello Geez,
I just uploaded a screenshot of the area on the map with building circled in red. The blue highlights are the areas where I've noticed no collision along the outside building edge walls and ledges. The stairs on the NW side of the building also allow you to hide through them because there is no collision. Let me know if the screenshot didn't upload for you.

BTW I made this bug report private because I didn't want other players to see you can exploit/hide in this building. Hope that is the right protocol.

Regards,
alhaknslash

Geez added a comment.Sep 10 2015, 10:04 AM

Hello alhaknslash and thank you for the quick response.
This is an issue we are aware of (#0022388) and it has been scheduled for a fix.
Regards,
Geez