Should I list this for sale?

[Tess Juel]

I have a bit of a problem here. I've made this script, called the Linkset Copier, that I use to transfer my builds between Second Life, Second Life Beta and Opensim. I suppose I don't have to explain what it does, the name says it all.

The problem? I know the script would be useful to other honest content creators too and I'd be happy to share it with them. But it can of course also be used by less honest people and that worries me a bit. Most of the functionalities are already easily available with Singularity's XML and Firestorm's OXP export features anyway but not all of them - if they were, I wouldn't have made the script in the first place.

What do you think? Should I list the script for sale or is it better I keep it to myself?

[Tess Juel]

Hi Tess,

That's a good question. I have my own thoughts on the matter but I'd like to know what the Kitely community thinks about this one.

[Christine Nyn]

I have a similar system and I haven't shared it. It could, as you have already said, be abused, especially in the case where a creator has made their wares copiable but no-trans.

[Chris Namaste]

since i cant script 'at all', im always interested in buying scripts from pple who know how to make good ones,

maybe it could be an idea to :
sell it only to people u know or trust (and keep their transaction, name etc)
best not to sell on market 'for all the reasons' sadly

my five cents

[Fayre Scribe]

Gid and I have builds that won't export from SL. Would be great to be able to bring them here. So it might be useful to us depending how it works. (because beyond just putting prims together to make a build, texturing, and making minor script changes, I'm not up on all the technology). However, I can see your concern. Maybe what Chris said, share/sell it to known trustworthy creators and not put it on the MP for anyone on open sim to grab. Question is, who is trustworthy. I suppose if they're already on the MP with a store and a lot of original merchandise, they're probably playing by the rules. (just my 2 cents)

[Chris Namaste]

Yes as Fayre says, i guess that 'knowing each other for years' might count ,even that i barely still can im etc (just speaking for myself now), and i'm sure Tess & Christine know who they can trust, anyway...its really tricky (so sad that it is..)
my one cent

[Tess Juel]

So it might be useful to us depending how it works.

I don't know Christine's script of course but mine can do pretty much everything that is possible to do with the llSetLinkPrimitiveParams() function in lsl, prim name, decsription, type, position, size, ortation, texture repeats etc., etc. There's only one mesh only parameter it could do but won't. (I'm not even going to say what it is; it's rather scary and the fact that it even exists should probably be considered a bug.)

I suppose it's easier to list what it can't do:

• It can't upload anything so all textures, maps and meshes have to be uploaded separately.
• It can't create anything. You have to rez and link the right number of prims to give it something to work on.
• Meshes have to be in the right place in the linkset order.
• It can't usually apply textures, specular maps, normal maps and sculpt maps since they will nearly always have different UUIDs on different grids. All the parameters are set but the textures/maps themselves have to be dragged onto the right place manually afterwards. (This could be fixed by using names rather than UUIDs as identifiers but then you'd have to add them all to the inventory of both the source and target linksets so it wouldn't really simplify things very much.)

So for pure prim/sculpt builds XML or OXP exports are probably still the better option. It's only when mesh is involved a script like this is useful.