JCampbell32

Void Singer, Sorry if I didn't follow things correctly. I saw the recent activity, felt it was similar to overloading, and found the answers here posted by others unintimidating. The people here seemed genuine rather than some out there who are just waiting to "pounce" on the unknowing and fill themselves with pride at the expense of others. Selfishly I may have taken advantage of the courteous atmosphere and current responses here. I don't know how to move the thread, in the future I will start my own. Hopefully the wolves don't rush in to fast to tell me to search through 40 other threads somewhere else before kind hearted souls lend a helping hand. I should however appologize to skybreeze though for hijacking the thread. Sorry about that, I did not quite think of that. Thank you, Jay

Rolig Loon, Jenni Darkwatch et all, Thank you very much for your help. I think it would be a bit much for me to explain this to the 30 plus students in my course, not including the other classes. It could get ugly, messy and confusing implementing that. Most of us are doing good just to edit the default script! I do understand your answer though and sincerely thank you for the Help!!! I've given it some thought along with the great input here. I think the easiest remedy is to have each fellow classmate keep their code under the touch_start event. In this manner we could elimiate the "chatter" and "overloading" that has been happening. If I am correct, nothing will happen until an object is touched. Once again, thank you very very much! You have been very nice and polite. I really appreciate it! Respectfully, Jay

Jenni Darkwatch, You seem to be very knowledgeable with scripting, I appologize if this is not the right place to ask, but here's my problem: We are using SL for school. We all have to place our assignments in one area for the instructor to look at and interact with. With 30 students creating prims that listen for interaction and say "Hello" you can imagine what is happening. One goes off, they all go off! It creates a huge lag, then crashes. This is new to me, and to my classmates and professor. My question is, is there a quick line of code that we can add to or edit that would listen only for avatars and not to adjacent or other scripts in prims? Something quick and easy I could submitt to the professor as an option that we all include in our assignments to stop setting the "Sandbox" ablaze with 30 objects all saying "Hello" and crashing the site and never stop chattering? Surely there must be something to limit a script interaction to just going off when an avatar talks, rather than every object out there, something easy for us newbies that admit to not having a clue as to what we're doing but trying! Jay