Hazalea
Hazalea
About
- Username
- Hazalea
- Joined
- Visits
- 11
- Last Active
Comments
-
@[Deleted User] said:
Well I checked myself and as far as I can see they are correct; Legion isn't bugged it was just the FOV.
I clocked his movement speed alongside a house with a stop watch timer.
Average travel time alongside that house in normal movement is 2.45 Seconds.
Average travel time alongside that house in frenzy movement is 2.05 Seconds
15% of 2.45 is about half a second or so; so even calculating for my trigger time with the stop watch it's absolutely faster and seems to be the correct amount faster.
https://www.youtube.com/watch?v=sBD9VV3mnuQ
So, doesn't appear Legion is bugged, he just isn't as good as people wanted to imagine he was.
have you tried testing your movement speed after striking a survivor during frenzy and seeing if your movement speed is slower
-
@MommyDeRose said:
Just don’t make him/her being gay or whatever, their whole personality. That’s what makes characters suck in every book/movie/game ever created that does just that with an LGTB character. Do it like J.K Rowling did dumbeldore, it was part of his character and it made him even better because he was more dynamic but it wasn’t literally who he was completely.
this is the exact opposite of what bhvr wants to do and what anyone would want them to do. saying 'oh yeah dumbledore is gay' after the series was over was really just trying to say 'look see this character is diverse', which a lot of people here are arguing against anyone doing in the first place, lol. also bringing up rowling is really really ironic considering she's really bad about trans rights.
-
yep, just gonna ignore everything that's been posted. classy
-
they didn't read bug reports apparently or want to listen to streamers who have played and experienced it on 4.4.1
-
can't believe i have to register for this
i like legion but they are unplayable right now
the bug was first reported as legion losing their move speed after striking the first survivor during frenzy. did anyone on the team or did you test the bug under _those_ circumstances