Walk through AB bridge

[icekirby34]

I was in AB and running from LM to stables when i ran towards the bridge. A warrior used battle shout just as i hit the bridge and i was able to walk through it, but not other objects. i walked through about five times then another player came and killed me. after i died when i came back the bridge was solid again. If anyone can recreate this or confirm that would be great

[colincancer]

:noquestions: sorry...

[Canttouchdis]

:noquestions: sorry...

it wasn't a question, it was a request and it doesn't say no requests here

[oricle001]

I've actually had this happen to me in EotS, I dont know what happened but I did something to allow me to walk through the faction flag tower things but nothing else. I hid in them to do sneak attacks o.O

[Charix]

There are parts that are built in to the world map which the server knows about and other things (like the bridge) are collidable objects that the server technically doesn't know about. Certain things can cause your client to ignore collidable objects. For example, being feared/sheeped/etc causes the server to control you and you will ignore collidables. Blink will ignore many as well. Though, honestly, the number of ways to cause your client to ignore collidables based on Blizz bugs is relatively limited. The two most common ways NOT based on Blizz bugs are to get a custom MPQ that has the collide flag removed from the object (Dangerous, since Blizz can see everything that is loaded) or hit the memory location for the collision and zero it out when the collision should occur (Also dangerous, since there are three locations, one for each axis, and they aren't always in the same place, so you can end up accidentally de-colliding the ground and falling to doom. Oh, and Blizz loves to detect memory meddling when they can)

[kemalraik]

Fascinating!

[kayleta]

There are parts that are built in to the world map which the server knows about and other things (like the bridge) are collidable objects that the server technically doesn't know about. Certain things can cause your client to ignore collidable objects. For example, being feared/sheeped/etc causes the server to control you and you will ignore collidables. Blink will ignore many as well. Though, honestly, the number of ways to cause your client to ignore collidables based on Blizz bugs is relatively limited. The two most common ways NOT based on Blizz bugs are to get a custom MPQ that has the collide flag removed from the object (Dangerous, since Blizz can see everything that is loaded) or hit the memory location for the collision and zero it out when the collision should occur (Also dangerous, since there are three locations, one for each axis, and they aren't always in the same place, so you can end up accidentally de-colliding the ground and falling to doom. Oh, and Blizz loves to detect memory meddling when they can)

Interesting, and very informative :P