Repulsor Cannon's bug
Product: Star Wars Battlefront II Platform:Sony Playstation 4 What is your issue related to? General Summarize your bug I found the following Repulsor Cannon bugs in the almost game mode. 1. Even ...
Forum Discussion
Hello @XP-8TIM!
I've moved your new thread into this one, to get more attention from the developers! I saw that you already posted here some time ago, so it's good to bump this thread.
As for the bug, yes the repulsor cannon is absolutely broken now. I hope they got a fix for it coming soon.
Thanks! And yes, I really hope they fix it!
That issue you pointed out about a second trigger to the repulsor cannon hitting the previously targetted enemy no matter if your attack should miss completely seems exactly like the issue Palpatine had when they messed his chain lightning badly because it could hit the AT-AT driver on Endor. You'd use chain lightning in an enemy and it wouldn't hit, but the next time you used it, it would travel to the previously targetted enemy no matter where he was in the map. I made a video showing this behavior back then:
I also saw this happening with his normal attack after they fixed chain lightning, I'll test this in Arcade this weekend too to see if it's still present, but I believe it has been fixed already.So with 3 different mechanics all suffering from the same issue, I think this is a material worth sharing with the team.
- I didn't know about that. Well then, even more reason for them to fix it.
I tested the 3 things: Chain Lightning, Palpatine's 1 and 2 handed attacks, and the Repulsor Cannon. Palpatine is free of this BUG on both the chain lightning and his lightning attack, great news.
But the Repulsor Cannon is indeed suffering this very BUG like shown in OP's video. I reproduced it in Arcade Splitscreen and the results are the same. It seems that there are distances which the repulsor cannon should hit, but instead it "marks" the target (just like in the video I posted before about Chain Lightning), and whenever you use it again (no matter if in the same skill usage or in the next one) aiming anywhere, it'll hit the "marked" enemy.
But I also found that at least at some distances it works as intended, hitting and not marking.
