Saxtus

It was mentioned in the old APB:R forum, but it got trashed along with all the discussions we had pre-2019.

Too much free time?

Just make sure to not burnout yourself or the team.

They say that if you want to do something right, do it yourself, but I am afraid Matt is hurting himself. Why no one else has enough knowledge across all the game's systems?

I didn't know that people can make APB look THAT ugly. Little Orbit how do you allow this to happen to your game?

Hmm, but how GTA online gets away with it? You can't choose height, but wearing shoes with heels, lifts you up significantly...

I believe that the only patches that are expected would be if: Need to enable/disable an event Something game breaking has been detected and fixed

Matt Scott, because of the extremely rare appearances he is our own celebrity!

In this beta the Logitech G Hub was able to correctly switch profiles automatically so I guess this is fixed. However again I was unable to make OBS to capture only the APB window while fullscreen. Please fix! Also there is something wrong with sound source when you drive a car and using surround speakers: Half of the engine sounds come from behind, like another car chasing you. This was not the case with APB v1.

2FA codes are time sensitive. As long as you enter the correct code within the time period, even if you entered wrong code before, it should work. I am not saying that measures against brute force shouldn't be taken by LO, just 2FA doesn't work that way. https://security.stackexchange.com/a/185917/66167 I am against SMS 2FA or 2FA that use proprietary apps in general. SMS 2FA codes comes with other problems, like trouble with routing, making your code either arrive with big delay or never, essentially locking you out. Not to mention the SIM swapping threat (although this is mainly a targeted attack) In my opinion Google Authentication compatible 2FA codes are the best in this case.

That is exactly what I meant. I read that they fixed token time sync issues. Have they fixed the issue with requiring a new token when you switch characters too?

That isn't an issue at all if you use Google Authenticator compatible apps that allow backups.

If the breach is from LO side, then it is not our responsibility. Worst case scenario, they will restore from previous state or compensate. I am talking about LO helping us shield our side.

Google Authenticator is enough protection but nobody sane will use it with all the problems mentioned in this thread. Please fix it LO. We want to use it. Don't punish those who want to use it because of bad implementation from your side! Don't ask us for it every time we switch character! Don't have your clocks out of sync, making it impossible sometimes to enter our tokens!

So LO still not ready for Google Authenticator. Anyway I 've changed my password and I couldn't login. I realized that one of the following characters in the password is a big no-no for LO: $&@ If you lock out yourself like me, try resetting to another password.