bc of this fix power struggle my fav perk to run is now basically ######### dead, bhvr in what world can you keep getting away with this
this is a ######### travesty
It definitely still works, I've used it myself. In that clip that you've put there, you are too far away when the pallet is dropped so the killer is out of stun range.
How can you drop a pallet with power struggle and not have it stun the killer?
I'm sorry but I have to completely disagree with that. A trusted member on this forums said it doesn't work either. It just throws the pallet down.
Because a pallet stun occurs when the pallet is roughly 50% of the way dropped, the stun does not start on the initial drop.
In the video linked there, by the time the pallet was in the 50% position - the killer was well away. If you notice when the pick up happens, the survivor is already at the end of the stun range.
I'm sorry, you cannot convince me this is fair at all. Power struggle will never be used again if this goes on.
Edit: And this is coming from a killer main.
and yet I play with it daily and have got 3 stuns with it today
The position of where the pallet stuns the killer has not changed btw, it's been in the 50% position for years.
If that's the case, you shouldn't be able to drop pallets if it's not going to guarantee a stun (with PS)
Before the reverse pallet stun change, this never happened - if power struggle went off, the stun was guaranteed because in order to be in range of the pallet to drop it, the killer had to be in stun range.
I get that it's likely an unintended side effect of the pallet change, but maybe the perk needs changing then?
If you can pull that off, please send clips of you getting stuns and I will stop completely.
I was most definitely not, it literally pushed him forward. I fail to see how a pallet PUSHING HIM FORWARD is out of range
that has literally never been how pallet stuns have worked, and it is funny how this after reverse pallet stuns are fixed, this is the only time ive seen this problem not once but thrice, dont you make up such bullshit reasons with the "50%" he got pushed forward by it that is still in the stun range, there is literally noway to pull a survivor with power struggle out of a pallet especially in the position that ghostface was, it sure as ######### has a stun window that reaches beyond that.
Out of stun range, but still in pallet model collision range, meaning the pallet pushed him forward while it was dropping. This sounds like a problem with the design of pallets in that case. If it can push the killer forward, but not stun the killer, there is an inherent design flaw that needs to be fixed. but somehow wasn't really an issue until the reverse pallet "fix". There's also the issue that there's plenty of cases outside of server lag that "50%" of the pallet still gets a stun.
so im just gonna add more pallet stuns that are clearly in a much further range than that ghostface was, and if you wanna dispute that. This is the same ping and same condition spamming spacebar at the right time to abuse the pallet stun window bc how huge it is. Bc I truly do not believe that you know just how big that stun window is
oh yeah pallets don't work like that, especially considering the first video and the comments about them working as intended.
The ghostface literally MOVES forward from getting his butt smacked by the pallet. If that isn't an indication that the stun simply didn't register at all, i don't know what is. As others have commented, the pallet hitbox is generally quite generous with what range it lets you stun a killer. The fact that at such a short range the ghostface did not get stunned at all is undeniably a design flaw.
The pallet being 50% of the way down (roughly) is how pallet stuns have worked for many years - that's not new. It's why you get a lot of survivors complaining they get hit through a pallet. there was a time when the stun happened at the start of the animation, but as I said, that was many years ago.
Regardless of "how" they worked, the way the pallet stun in the clip happened (or lack thereof, technically) is clearly not functioning properly. The pallet hitbox actively pushed ghostface forward, and yet the hurtbox did not activate. Compare this to the clips posted above, where clearly, the pallet hitbox isn't even hitting the killer, nor pushing them forward, yet the hurtbox is still activating and stunning the killer. There is an issue with the perk, or an issue with the pallet changes, it should never be that inconsistent.
You have no point, since the perk description clearly says "you can drop a pallet to stun the killer and escape their grasp".
It says "YOU can drop the pallet" as in you are able to drop the pallet. Not that you have an arbitrary random chance to drop it.
And it says "drop TO stun" not "drop and perhaps it CAN stun".
dont ignore the fact it was most definitely still in range as I showed you with even dumber pallet stuns with the same ping, the 50% ######### just has no merit here
So Mandy, wanna issue a apology about your inability to understand how you failed to see what was wrong here? since bhvr fixed it today
"Fixed an issue that caused the Power Struggle perk not to reliably stun the killer since the same side pallet stuns were removed."
how can that even be possible to use a perk that is supposed to let you still the killer and then not have it stun the killer. The killer shouldn't be able to be fat enough from the pallet for it not to work. Defeats the purpose of the perk.
Pallet hitboxes are pretty generous, and there was also that vacuum.
That clip looked like it should of connected.
I know the PS case is fixed now, but I'm just here for the drama.. jk
I never understood why same side stuns had to be patched out in the first place.
I mean if the killer is within the hitbox, he/she should be stunned. If there was some weird edge case, you should be looking into why they clipped together in the first place.
Changing the overall rule, then deploying some more code to treat an edge case (power struggle) is the sure way to spaghetti code.
In some cases where it was not working correctly it's been fixed, hence the wording on the patch notes (the added "reliably") because many players have managed to do it many times with no issues, it was edge cases that weren't working.