Second Inventory Software - Save Inventory to Hard Drive

Kitty,

the software will only allow you to make a copy if

a) you have full permissions for the object including all prims, contents and assets in that object

or

b) you are identified as the original creator for the object including all prims, contents and assets in that object


So yes it does allow copying of M/NC/T or M/C/NT prims but *only* if you are the *creator* of those prims.

It would be very easy for someone to remove these checks and use this software for copying anything, which is presumedly why the author is not releasing the source code for this tool.

Matthew

Mmmm, it is quite easy for the software to check the creator and permissions of a texture from its UUID before attempting to save the texture!

That said, it is extremely easy to steal a texture given its UUID using an unmodified LL client...

Matthew

Thanks for this thread. I have wanted to know the question to this for awhile. I am still new to SL and I have bought so many things already. I guess I will just have to hope for the best.

BT

Well, It is the 21st. Has the restore function been activated?

Irony

hahaha. Nice one.

Do you have a copy to try something?

There are two ways to see who created a linkset: one is shallow and easily fooled, the other is accurate. If they're using the accurate way there's no problem, if they're using the shallow way then you have a copying tool.

Hence me asking someone who owns it to try something.

That's doesn't help the cause... since the scripts and the textures are the easiest things to backup and restore on SL without using any exotic application: scripts are plain text (copy and past and you finished); textures: it's supposed you own them on your HD already, but if you don't > Save As.... et voila'. So, again, why the hell i would have to use a "copybot"?

PS: there's no copybot able to backup a script, even it's stupid to do (since it is a normal text file) so the reason would be only to steal someone else work; the script resides on the server, so only LL can make actually a "backup" utility... but again there's no senso to do backup a text file!

Ease of use - given two scenarios:

i) select each prim in a large link set in turn, open contents, open first script, copy contents, open new local file, paste contents, save local file, open second script in prim, copy contents, open new local file paste contents, save local file, repeat for each script in prim, then repeat for each prim in object...

ii) select object in inventory, click save.

I know which I'd find easiest. Your approach is fine for single prim, single script objects but not really convenient for any complicated scripting project.

Also with both textures and scripts it isn't just having the texture/script it is also ensuring it is on/in the right prim, and with textures is sized and positioned correctly. Once this software has the restore function, being able to not only upload the textures but reapply them correctly would be extremely useful.



A copybot *can* backup a script if you have modify rights (i.e. the ability to read the script source) - if the LL SL Client can access the script source code to display it, then so can any copybot! You can't backup a script to which you do not have the access rights but this software doesn't claim to do that.

Matthew

U telling me that you have objects that are using a set of so many script, one inside each prim, that would be so stressing to copy & paste em manually into a txt file? ...so you motivate a third party copybot to avoid that (supposed) hard job... soz i dunno what's english term (and my english suks) but we say something like: climbing on a mirror.



No i do gadgets with multiscripts on different primitives, but we are talking about a limited number (i don't think you gonna have a 240 prims object with 240 script inside it... to not talk about the performance). And if you would need to do that, i can deploy a script that will self duplicate itself inside each prim of a linkset and will move the scripts away from each of these prims saving em in a single inventory contents. But we're not eninstein and we're not talking about teoric mats formulas, we faces real problems, so:

a) you can actually copy manually the script;
b) you can automatize the copy inworld;
c) that "copybot" doesn't claim to copy any script...

So i ask again: how do you motivate the (eventually) usefull of this "program"?



Read above.. anyway if you loose a texture asset, the parameters on the prims are "saved" (position etc.) you loose just the texture coz the key doesn't exists anymore, so you need to re-apply it again. Assuming that a) you lost the main object; b) second life lost your asset.



Yes, opening each script from each object/prim and save em to a txt file, but to revert em? U must do it manually, otherwise you need to automatize the creation of a new script, copy the content of your local txt file into it, move it to the object (in the right "backuped" object) etc. etc.. or upload all the scripts (and it would costs to you 10 linden per upload) and do the same.
All that stuff because you won't to do a simple copy/paste operation that would be 100000% faster (and free) in 99.9% of the cases. Sry i've a programmer mind, i do stuff when it is usefull and it does really help, i do not work in a laboratory making experiments just for the glory (loosing my time)... i did that in the past, i do not have time anymore.
Does this copybot has a market? Yes, maybe for 1 user per millions.

Or better still ....... as each script is written add them to a local (hd) text file with a commented id as a header and save the txt file then you only need one file to upload L$10 period.