How long will Clown remain kill-switched for?
Genuine question , do we have an estimate? I just accumulated 2mil bp to prestige him and get his perks on my other killers and I can't even seem to be able to spend blood points on him, not even play him
Comments
-
so I cant play my "main" for a couple of weeks ? and not even spend BP ... jesus
0 -
Yeah, the soonest they could turn him back on would be whenever the bug fix patch is since it’s something that has to be fixed on the client side. So hopefully not more than a week or two.
0 -
Yeah, it's borderline ridiculous that this inconvenience is to last more than 24/48 hours. People paid for that character, and his perks, as well as for this game
2 -
I'd much rather we have something gamebreaking killswitched than in the game so people can continue to use the gamebreaking exploit. Bugs happen, it's best that these bugs cannot be used while they are fixed.
2 -
I am fine with that, what I am not fine with is not being able to buy perks for a character that is broken in matches, not in the bloodweb.
What I am not fine with is not having an ETA of roughly expected fix.
What I am not fine with is not having some kind of compensation such as BP, shards or whatever.
0 -
Oh I agree you should be able to level up a killswitched character, but if the option was no killswitch or no levelling (which it shouldn't be but often for some reason is) I'd still prefer it to be killswitched.
0 -
I agree, I am just salty because I grinded 2 mil bp to prestige clown to unlock his perks and now I can't because some *insert witty insult here* wanted to exploit a bug
2 -
They should reward every player who played Clown in the past week with some BP, shards or even a Clown skin for free (could be one of the cheapest skins in the store, nothing major)
0 -
No ETA given, but it really all depends on:
1) how hard the bug is to sort out
2) if they do a 6.1.3 bug fix patch and
3) if they decide to just wait until the next chapter
At this point 6.1.1 is probably already out the door and off for console verification.
They are probably putting the finishing touches on 6.1.2; if the bug is easy to fix they might be able to squeeze it in just in time. If not then it could be a long time, as they don't usually do 3 or more bug fix patches (but it has happened).
My money is on it being fixed in the next chapter patch but that's just an educated guess and I could very well be wrong.
0
