Author Topic: RTB Development  (Read 378245 times)

Small update, v2 of the RTB API is almost complete. The architecture is done and it just needs all the code plugged into it, which is already written anyway from v1.

On the topic of RTB v4 - I have finally decided to include a feature to let you search the names used by a Blockland ID as part of the friend invite system. You'll be able to view the recorded history of names belonging to an ID using this tool. As usual, there will be an opt-out privacy option that you can enable which will prevent you being listed.

I'll write a big post on the friends list side of RTB v4 and invite you guys to suggest things you want for it, but wait until you know what's in it first!



I want a gallery/builds downloads section in the mod manager for a future update. Would be cool, getting builds would be so much easier.


Quick question, how many of you guys actually used the download feature in the server information browser? I'm just doing it now and I've added the player list, and the list of add-ons the server has (along with whether you have that add-on installed, and whether it contains content like sounds/shapes etc.) but I have no idea if people actually downloaded from there.

Quick question, how many of you guys actually used the download feature in the server information browser? I'm just doing it now and I've added the player list, and the list of add-ons the server has (along with whether you have that add-on installed, and whether it contains content like sounds/shapes etc.) but I have no idea if people actually downloaded from there.

I did... sometimes...

Quick question, how many of you guys actually used the download feature in the server information browser? I'm just doing it now and I've added the player list, and the list of add-ons the server has (along with whether you have that add-on installed, and whether it contains content like sounds/shapes etc.) but I have no idea if people actually downloaded from there.
I use it most of the time, it is so much faster than waiting for the downloads from the server and they are most likely good not going to break my computer :3

Quick question, how many of you guys actually used the download feature in the server information browser? I'm just doing it now and I've added the player list, and the list of add-ons the server has (along with whether you have that add-on installed, and whether it contains content like sounds/shapes etc.) but I have no idea if people actually downloaded from there.
I did on occasions. Would be nice to keep though.

I used it pretty often, actually, but really for Prints and stuff like that it was best.

Also, in a minor fit of downs I totally neglected to post here instead of messaging Ephi via MSN. Could have even been a major fit of downs. My bad.

Anyway: Suggestions regarding the RTB GUI Transfer system.
  • A clientCmd for performing functions on certain GUI controls, such as resizing, adding lines to lists, setting buttons active status or text, or toggling visibility. ie;
Code: [Select]
clientCmdRTBCT_Do(%control,%function,%arg1,%arg2,%arg3,%arg4,%arg5)
clientCmdRTBCT_Do("TextList","addRow",1,"Option One","");
  • Some other controls are needed: GuiTextListCtrl, GuiPopupMenuCtrl, and possibly GuiMenuBar would be useful on occasion.

It would also be nice to perhaps be able to register a clientside mod to be shown on the info GUI, and possibly mark these mods (move them to the top of the list & display a warning when joining without said mod). Of course we can do the latter ourselves, but it makes sense to do so.

Yeah GUI Manipulation is something I'm still drawing up but eventually I'd like to have a neat little API for servers to use to control pretty much all the important aspects of the client GUI. It's more a case of making sure it can't be abused than coming up with how to do it.

It would also be nice to perhaps be able to register a clientside mod to be shown on the info GUI, and possibly mark these mods (move them to the top of the list & display a warning when joining without said mod). Of course we can do the latter ourselves, but it makes sense to do so.
I agree.  I was just thinking about this recently. Maybe it could be marked as "crucial" (client guis required to play an rpg?) and if a client with RTB tries to join they are warned that they need a mod to play the server to a full extent.

This is a possibility because I know it would help people out with regards to distributing their server gui better, however it would still be subjected to the RTB Reviewing for each update - and TCPObject-self-updating would not pass review. I'll build this capability into the 3.1 server information but specifying required/recommended add-ons to join servers would probably have to be done in a later update.

The downloads to ratings ratio is crazy. Look at the Duplicator: 2,892 downloads, and 31 ratings.

You mean people aren't rating things enough? I need to figure out a way to encourage ratings but not in a way that makes people spam them thoughtlessly.