clemon
clemon
About
- Username
- clemon
- Joined
- Visits
- 3
- Last Active
Comments
-
Look from the realistic POV this thing is not gonna get changed even though it should. BHVR has already spoken and they don't recognize it as a bug. Okay fair enough you acknowledged this in the post but I sincerely doubt that calling it an issue instead of a bug is gonna change anything; BHVR is not gonna play with semantics - at the end of the day it's us the community asking the company to do something in our favor (all of us for a change, not just 1 side) unfortunately we already got an answer and it's a no sadly.
I don't want to say here that the whole post is pointless but this is kinda doing the same thing again isn't it. History has taught us that going for the big one (fixing this issue) didn't work so maybe this time we should go for something smaller? Like asking BHVR to at least acknowledge it is an issue for every player involved and then see where we can go from there. Maybe we can get ingame info about the whole issue so the new players aren't caught off guard by it? I mean it's ultimately a band aid fix and even that is stretching it but at least it would be something compared to the total disregard of the issue from the previous attempt.
Now I hope that I'm wrong and this time it's gonna be successful because it's the biggest collab in the game's history that's affected by that issue. If not then well here's my idea for attempt 3 in the future.