By registering with us, you'll be able to discuss, share and private message with other members of our community.
Sign up now!do u need an account?Thanks for the report, investigating now.
I might, I failed to reproduce it on my normal account.do u need an account?
I might, I failed to reproduce it on my normal account.
Fixed for the next build. If this issue continues after the next update for anybody, please report it again. It's an issue with the way we're detecting the current InterfaceMode. They broke the detection we used before, so I rewrote it to use a different varpbit. Apparently that varpbit wasn't the correct one and although it worked on my account, it didn't work on all of them. Currently there are 8 varpbits that seem to correspond to legacy/modern, although I'm sure only one of them is the specific check for it. As I narrow the list down further it'll become more accurate although from all my testing the one used in the next build *should* work for everyone.
It should be fixed at this point.same problem
Yeah, I confirmed it worked on the account slash gave me.build v1.1.18?
believe me it is not working on 5 other accountsYeah, I confirmed it worked on the account slash gave me.
Have slash send me another account that's not working then.believe me it is not working on 5 other accounts
To resolve it I'll need an account that's still experiencing the issue@Cloud Not resolved. Still occurs. As for the messages above I was probably asleep at that time and I wasn't given any list of accounts to give to cloud xD
To resolve it I'll need an account that's still experiencing the issue
I'll send you the details on skypeTo resolve it I'll need an account that's still experiencing the issue
We use essential cookies to make this site work, and optional cookies to enhance your experience.