Author Topic: RTB Development  (Read 381960 times)

Must've been added recently then. I've seen people spamming on there before.

Nope, flood protection has always been there.

Nope, flood protection has always been there.
Well then it isn't doing its job right.

Thanks for the detailed response, I'll be sure to look into how my flood protection isn't meeting your criteria of acceptability.

I have a request, by default, upon downloading a new add-on from RTB, it should turn on automaticly, I've made the mistake of downloading an add-on, starting a server, and realising the add-on isn't there multiple times

maybe add a toggle option for it too

also, does the main version of RTB only update once the version number hits over 4.9? because if so, and the update timestamp stays as it does now, that save gallery is a long time from now :(
« Last Edit: December 14, 2011, 04:39:21 AM by soba »

X.0 = entirely new feature
0.X = small feature addition
0.0X = patch

It could be v5 tomorrow.

Thanks for clearing that up, I never really understood version numbers like that

Thanks for the detailed response, I'll be sure to look into how my flood protection isn't meeting your criteria of acceptability.
People seem to be able to send the same message every 0.5 seconds without any kind of punishment when Blockbot isn't there.

People seem to be able to send the same message every 0.5 seconds without any kind of punishment when Blockbot isn't there.
I think by "flood protection" he means protection against spamming so fast that the other client crashes (like TomTom did during the beta).

Code: [Select]
Add-Ons/System_ReturnToBlockland/support/networking.cs (319): Unknown command onDisconnect.I suggest that you replace line 319 in file support/networking.cs with this:
Code: [Select]
return isFunction(%this.getName(), onDisconnect) ? Parent::onDisconnect(%this) : "";Same goes for line 205, 222, 287 and 303 respectively.
« Last Edit: December 18, 2011, 03:42:31 PM by mctwist »

And for tcp objects with no name?

Then that guy is doing something seriously wrong. However, it should work nonetheless, except if some other guy overrides the default TCPObject namespace.

And for tcp objects with no name?
Set a temporary random name, as long as its only for the scope of the isFunction call.

Then that guy is doing something seriously wrong.
It is perfectly acceptable to have a nameless TCP object. There are cases where you don't have to use a name.

It is perfectly acceptable to have a nameless TCP object. There are cases where you don't have to use a name.
Unless you don't package the default TCPObject functions, how are you going to retrieve status? I see your point though, as all Torque objects can be nameless.

Is this possible to add?
How about a 'loadbricks()' console command?

Did the saveBricks(); command get removed in RTB 4? Because when I tried saving on my dedicated server BL complained about the function being nonexistant.