Quote:
Originally Posted by xXziroXx
That would be me that posted it a few months ago, never got a working answer. And the array works, obviously, since it can be read. So I doubt thats the issue here.
|
I have a hunch, but I am at work so I cannot confirm or deny this right now, but checkit.
The array obviously is not working, a truth which contridicts your statement. Why would you be posting?
I am not sure what part of your npc you are pulling your code from but bear with me. You are assigning that attribute clientsided, yes? Your clientside variable may very well be able to store that array, that attr variable on your clientside is nothing more then a variable. HOWEVER, when another player pulls it from you, they are only getting the first index, since attr cannot handle anything else between clients. If my memory serves me correctly, attributes have to be strings. If this be the case, the optimal solution you have available to you is converting it to a string before sending it, such as putting the @ in front as I had earlier seen in this thread.