@c0bra_4@Crypto_Cartel90@tarkov Honestly, we'll see, but I am fairly sure that the vast majority of PvE players that play at least few hours per week won't need extra rubles considering how much you can make in few raids
Unless BSG decide to reduce the drop rate to press the ruble need even more
@c0bra_4@tarkov Nah you're not crazy, it's really, really easy to gain millions in PVE in few raids. That's why I'm not that sure about that decision except for testing purposes to later on deploy it on PVP-based servers
@c0bra_4@tarkov Yeahhh, I don't know about that one.
I wouldn't be surprised if it's more of a test-based decision to see how the playerbase reacts to later possibly deploy it on PVP rather than anything else.
PVE is really simple to gather millions in few raids, so Idk about that one
@emmbld Hello Emmanuel! Je me permet de demander ça ici vu que je ne peux pas te dm.
J'essaie de faire rejoindre un ami qui n'est pas en mesure de rejoindre, très probablement à cause de son domaine d'adresse email. Il est sous un alias Protonmail, est-ce qu'elles sont acceptées? Merci!
@ThePsychoPine They're aware, they're normally an alert in the client that explains this, but well, weekend
Drew mentioned what they currently know here: https://t.co/ihMKMhVDCO
Tickers are up in all regions. Here’s what we know:
1. Remakes have increased in the last three days.
2. This is driven by an increase in people failing to hit loading screen from champ select.
3. This issue appears an order of magnitude more on 8gb and 16gb RAM machines vs 32gb RAM machines.
4. We believe what’s going on is that, when you finish a game, that process is taking up to 10 minutes to properly terminate. If you try to start a new game (that is, move from champ select to loading screen), the old process blocks the new process and throws an error. A lot of people have hit that in the last three days.
5. The ticker advising people to restart is aimed at ensuring that the old game process fully closes, which would resolve what we presently believe to be the root cause of the issue.
6. We have a team continuing to test and validate a fix, but don’t have a timeline for deploy yet.
7. We’ll be actively monitoring Clash in OCE to see how it goes. Fingers crossed, as we never want to cancel Clash.
8. PS team has guidance to refund LP and lift penalties associated with these issues, so please write to them if affected.
Thanks for all the logs and all the clips, they’ve helped a lot. Have a good weekend.