Author Topic: RTB Development  (Read 394983 times)

I guess compressed they take up a pretty much trivial amount of space and it's probably not worth really studying it then. I wouldn't be surprised if you could hold all the saves ever made by everyone on a flash drive if you stripped out the pictures. If you run a beta that will also let you establish a pretty good baseline as to how people will use the service anyway, and you'd be free to adjust the cap then without bothering people much.

Storing only unique saves is a really cool idea.

My plan is to store saves based on the content of the save file instead of what it's called, so in actual fact if everyone had the default saves on their RTB account it'd only take up as much space for me as one copy. A lot of people share and save popular builds so this enables me to make people's quotas only count towards unique save files, while also making sure I'm not wasting space storing the same file hundreds of times. There's a lot of logistics to work out there but those are my intentions at the moment.
You could possibly create a way to determine the difference between two save files and output data on all the additions,  subtractions, and edits. This would cut down on minor changes in stored saves if all you store is the original save the person loaded and the data of the changes they made, and you could even throw in a Wikipedia-style version history for save files, which could have several uses besides being a nice novelty.

I like the idea of saves management.  But could it be done with Private sharing too?

Registered an RTB pref as an int ranging from 5 to 100. Upon trying to set it to 20, pressing the 2 causes it to put in a 5 because 2 is below the minimum value.

Registered an RTB pref as an int ranging from 5 to 100. Upon trying to set it to 20, pressing the 2 causes it to put in a 5 because 2 is below the minimum value.

That's stuffty, I'll fix it.

Registered an RTB pref as an int ranging from 5 to 100. Upon trying to set it to 20, pressing the 2 causes it to put in a 5 because 2 is below the minimum value.
That has been a problem for as long as I can remember :u

You could possibly create a way to determine the difference between two save files and output data on all the additions,  subtractions, and edits. This would cut down on minor changes in stored saves if all you store is the original save the person loaded and the data of the changes they made, and you could even throw in a Wikipedia-style version history for save files, which could have several uses besides being a nice novelty.
If I'm understanding you correctly, this is going to result in every safe file being diff'd with the uploaded one. Text difference calculation is pretty slow as it is.

Alternatively, if you meant that they Good Guy Greg were to select a save file that his is based on (and when the save download is served it compiles the differences with the parent save), then that would indeed save a decent amount of space. While you're at it, you could make it so they can select a certain colorset that is used and then it only stores the brick part of the save. But like Ephi said, the space used probably won't be that bad.

Storing a save file should begin and end at the click of a 'save' button. Any sort of "selecting colorsets/choosing save files it's based on" process is just unnecessary work. As it stands it's very easy to extract the colorset from a save automatically, save that as a separate file and have any subsequent save files using it reference that single file. Users should really not have to put any effort into storing a file on RTB.

I think saving the difference in save files is probably going a little too far. Given the great compression ratio I've already achieved with little to no effort I think it wouldn't be necessary to go that far since it'd be considerably more work for savings that could be gained with much less effort.

Would it be possible to add a general list of online RTB users? I find that the only reason I ever have the General Discussion window open is because people sign into it by default, and the list of it in the side-bar is easy to scan through if I want to contact someone or look up their information. It's usually a good list, but people can leave the chat room, and also I don't particularly want to see people roleplaying with the /me command, myself.

Also, could you add some way to tell whether a person can be messaged without being their friend before typing up a message and sending it?

Some sort of user search functionality will be added eventually. I'll add a filter to hide offline people so that should satisfy your first requirement.

As for knowing if someone accepts messages before you send them, the only word I can think of that accurately describes how all that stuff works is "ghetto". I plan to re-write it to work a little better but as a stop-gap solution it could request those details upon opening the chat window or something dodgy. Given that it's just a case of poor usability at the moment it probably won't be addressed for a while.


...


So... Does
3 kicks in a minute -> ban for a week,
5 in 10 minutes -> ban for 24 hours
sound like a good system?

Got about a year's jump on you, Wedge :)

You're only helping me to prove you posess a time machine.

Registered an RTB pref as an int ranging from 5 to 100. Upon trying to set it to 20, pressing the 2 causes it to put in a 5 because 2 is below the minimum value.
I reported this with Trac during RTBv4 Beta. :I

You're only helping me to prove you posess a time machine.

Wedge is ephialtes six days younger the real ephialtes

I steal your cookeh's Ephialtes =3  :cookie:  :cookie:  :cookie: