Author Topic: Return to Blockland v4  (Read 49122 times)

More like taking whatever oppertunity to insult Ephailtes work he can.

Well no stuff.
But it's not like he personally made requests.
Seriously, hold a cache for an hour, problem solved.

Good, it's been released. I was a beta tester, so It doesn't make much of a difference for me.  :cookieMonster:

Also, try clicking the RTB logo in the OP. Very interesting.

Someone PMs me, I hit shift+tab, and I can't figure out who PMed me.

Nevermind, it was because the message sound for general chat is stupidly set on.

Interface is a bit odd for me, but all in all the features and updates are worth it. Very nice indeed.

Interface is a bit odd for me, but all in all the features and updates are worth it. Very nice indeed.

Surprised you say that. I think the whole Steam-style overlay is pretty clever, not only since its cleaner and nicer to use that way, but because most people here have used Steam and should already be used to the interface.

Unless you are speaking strictly about the setup of the windows... but even then its got a very typical layout for a messenger.

getSubStr(...): error, starting position and desired length must be >= 0: ("</r"
,2, -3)
BackTrace: ->RTBCC_Socket::onLine->XMLParser::bufferData
that is being infinitely spammed into my console as we speek.

Im having the Validating key problem again.

getSubStr(...): error, starting position and desired length must be >= 0: ("</r"
,2, -3)
BackTrace: ->RTBCC_Socket::onLine->XMLParser::bufferData
that is being infinitely spammed into my console as we speek.

That might not be RTB's fault. RTB packages some default commands so it can run it's own functions through it. When an error occurs in the original command, the back trace included the occurrence though any packages and such. That would be like blaming the pipes for giving you contaminated water when it was contaminated by the water supply itself.

Im having the Validating key problem again.

Any details? Could easily not be RTB's fault.
« Last Edit: October 20, 2011, 06:51:46 PM by MegaScientifical »

Any details? Could easily not be RTB's fault.
I'm having the same problem that everyone had. Did I have to download RTB again?

Any details? Could easily not be RTB's fault.

Esp. since v20 just came out. Two new systems, nightmare. :P

this validating dilemma is ridiculous.

I'm also getting it as well, still, so to speak.

this validating dilemma is ridiculous.

I'm also getting it as well, still, so to speak.
Getting it here too.

Server list comes up quickly and fine though.

This might sound superstitious, and plainly stupid. But I feel like I'm the one that is causing the validating problem, ever since I got on, It worked fine, 2 minutes later, everyone had the problem, both times.

That might not be RTB's fault.
the only backtraces are from RTB functions:
RTBCC_Socket::onLine, and
XMLParser::bufferData.
those are not default functions.