Sharing variables

[JT Hamelin]

Is it possible for thousands of objects in world to share the same set of variables. So, if I created an item and someone copied it from me, the two items could share the same variables?

[Darkie Minotaur]

Yes and no - well, as far as I understand your question.

Variables as such are restricted to one script - there is now way to define a super global variable that different scripts can access.

Of course you can store values in a way that different scripts/objects can access them.

[Tabris Daxter]

if they are static/ non changing. YES (though technically not a Variable)

OR

if they are stored in a central loocation(website, server prim) and you have some sort of communication to update the "children".

OR

the variables change based on a set pattern at a set interval.

[JT Hamelin]

So basically a serving prim would work? That's what I had in mind, but wasn't sure if it would or not. (I'm new to LSL)

[Darkie Minotaur]

Again: yes  and no - depending on what you want to do. Tabris pointed at different possiblities which are more or less suitable depending on the context.

[JT Hamelin]

I need to keep up with several string variables, constantly count users using the object and be able to choose one single user from the entire crowd of users.

[Void Singer]

then you need a server type set up... the client objects would all send there values, and the server object would accumulate them and send them wherever needed (back to the client objects, reported somewhere else,etc)

[Darkie Minotaur]

I'm not too sure - if crowd < 10 and they are all in one sim, I probably would do without a server. If only we knew

[Void Singer]

well, if we're talking thousands of objects as in the OP then I'm going to assume multiple regions... but it is a valid point.

[JT Hamelin]

Yes, multiple regions indeed.

[Darkie Minotaur]

in that case you would need either e-mail or http and most likelxy a server unit which could be inworld or outworld - which communication and the layout of the information flow depends on the use case - still

[Void Singer]

inworld, lsl http would be your best bet, backed up by email...

server sits in one place, accepts both email request (which will contain an http address for the clients) and http requests (which can be used to update). clients would attempt to send updates via the last known http address and if it fails fall back to sending their own http address via email. the server prim updates from either message type, and if it's email, send an http message with it's new address.

out of SL any server that accepts http requests would work, and preclude the need for client http-in