Return to Blockland v3

[Loz]

I don't think he was trying to...

[Ad Bot]

[Destiny/Zack0Wack0]

And there would be the proof Ephi is not a god at scripting, but he is better than most people here.

Haha, Kheyre that looked so desperate, and made yourself look like a complete tard.

[Eryehk]

Haha, Kheyre that looked so desperate, and made yourself look like a complete tard.

Not trying to make him look like a terrible scripter, just pointing out that he is human after all, and makes mistakes.

[Destiny/Zack0Wack0]

... are you an idiot.

The table was not HIS mistake, it wasn't involved with HIS programming, it was just a malfunction with the table.

[Marcem]

Not trying to make him look like a terrible scripter, just pointing out that he is human after all, and makes mistakes.

Superhuman.*

[Truce]

RTBC_IRCClient.cs
Line 411
Line 425

Both are currently:

Code: [Select]

RTBIC_addLine("\c6Connect Failed - Retrying ("@%this.retryCount@"/5)");
Both should be:

Code: [Select]

RTBIC_addLine("\c6Connect Failed - Retrying ("@%this.retryCount@"/"@$RTB::CIRCClient::RetryCount@")");
Obviously, not worth an update just for this bug, since it's so small.
But I'm pointing it out for whenever you do update it again so people don't see:
"Connect Failed - Retrying (14/5)"

[Ephialtes]

It could never get to that point anyway given that there is a check above it:

Code: [Select]

406    %this.retryCount++;
407    if(%this.retryCount > $RTB::CIRCClient::RetryCount)
408       RTBIC_addLine("\c2Could not connect.");
409    else
410    {
411       RTBIC_addLine("\c6Connect Failed - Retrying ("@%this.retryCount@"/5)");
412       %this.retrySchedule = %this.schedule(1000,"connect",%this.site@":"@%this.port);
413    }

[Truce]

If someone changed the $RTB::CIRCClient::RetryCount variable, then it could.

[Ephialtes]

If someone changed the $RTB::CIRCClient::RetryCount variable, then it could.

Find me someone who would actually bother to do that haha. If it doesn't connect the first time, chances are it never will. I just threw in the retry stuff to give people some hope.

The general rule of RTB (and probably Blockland) is that when you get it, generally it works. When you change stuff and it breaks, its your fault.

[Truce]

Find me someone who would actually bother to do that haha.

Haha, true. If I do I'll let you know ;)

[Randy]

I have a couple of suggestions:

Allow negative values (or at least -1) in the Server Control Preferences.
Make it possible to enter multiple words for items in lists (eg. "list\tNone\t0\tMost Frequent\t1\tAll\t2").

[Ephialtes]

Oh, I thought event lists were space delimited too - I'll switch them over to tabs for the next update and to maintain backwards compatibility if it doesn't find tabs it'll assume its space delimited.

[Randy]

Events use spaces like the current rtb system and tabs to separate different parameters, but it'd be good to be able to add spaces.

[Edit] Another suggestion: Adding paintColor would be cool.

[Ephialtes]

Yeah i'll try to get all the default parameter types that Blockland uses into the server control thing. The ones I need to add are float and paintColor so far. I can't remember if there are more.

[Tezuni]

Heres a suggestion:

There is a glitch when you are in RTB IRC and you have a name selected, and you are still scrolling through the name list.  When someone leaves, or joins IRC, you automatically focus on the selected person in the list again.  So that means if you were looking at other people either further up or down the list, you have to scroll up or down to where you were again.  It gets annoying, and as more people get RTB it will be a race just to select the person's name before you get scrolled away again.