Author Topic: ID already logged in for RTB Connect?  (Read 1562 times)

I tried loading up RTB Connect and it says this:



I'm already logged in? I'm only using one Blockland and my internet connection is fine. If anyone could help it would be great.

I've tried numerous times to get on, I have no clue what's going on. I even logged onto another account and it didn't work. If this is happening to anyone else then I'd feel a tad better. It's not my internet connection or anything. :/

You should probably ask ephialtes

Yeah, ive noticed some strange things with RTB recently.
Hitting "Info" on a friends name while hes on a server only tells you that hes playing, and not what server hes on.

RTB is broken as of the last BL update. Just wait for RTB to be updated.

RTB is broken as of the last BL update. Just wait for RTB to be updated.
No it's not
Only the part that will display what server your friends are in and you can't see player lists on server info

No it's not
Only the part that will display what server your friends are in and you can't see player lists on server info
The whole service seems to be having issues. I can actually view server info just fine, but it takes forever to do anything.

The whole service seems to be having issues. I can actually view server info just fine, but it takes forever to do anything.
You can view the info for some servers because those servers aren't updated to r1808 yet.

The whole service seems to be having issues. I can actually view server info just fine, but it takes forever to do anything.

It seems to be something up with the bl master server. I took a look at the process trace and it's hanging on connections to master2.blockland.us which I should have made asynchronous tbh. I'll fix it at some point.

Yeah, ive noticed some strange things with RTB recently.
Hitting "Info" on a friends name while hes on a server only tells you that hes playing, and not what server hes on.

That's not a glitch, that is Scallywag Mode.

That's not a glitch, that is Scallywag Mode.
That is a glitch, caused by badspot taking off the IP: