Talk:LlSetDamage

I deleted following sentence.

If the object hits another object it will die.

This function seems to have nothing to do with object-to-object collisions. If the sentence is true, detailed conditions should be described, I think. --MasterOf Perl 14:23, 25 May 2009 (UTC)

It needs to be better written. It's why the world isn't riddle with bullets that didn't hit their targets. -- Strife ^{(talk|contribs)} 17:11, 25 May 2009 (UTC)

hmmm i see your point. I have expanded the article. -- Strife ^{(talk|contribs)} 17:39, 25 May 2009 (UTC)

Part of the problem is, I haven't really scripted any guns in... oh 5 years. And things have mostly likely changed. -- Strife ^{(talk|contribs)} 17:58, 25 May 2009 (UTC)

it will however not be physical while it is not damage enabled ... ?

"If the object is not physical, the object will be damage enabled if it becomes physical; it will however not be physical while it is not damage enabled." ... It sounds as if all physical objects have to be set damage enabled via llSetDamage... Anyone can rewrite or explain it so I can understand what these lines mean?--Mako 08:00, 9 May 2010 (UTC)

I'll do some testing after I get some sleep and let ya know. It looks like it might mean something like the relationship between llMoveToTarget and STATUS_PHYSICS. You can have physics without moving to target but you can't move to target without physics enabled. So, if you set a move to target before the physics, the prim does nothing. If you then set physics, the move to target acts until the physics are disabled again. Something along those lines anyhow. -- Fred Gandt ^{(talk|contribs)} 08:37, 9 May 2010 (UTC)

Then we'll have to add more information to the line, for example insert the word "moving" or such anywhere in these line? I'm interested in only the way of "explanation" about each matter and I personally don't care about each specification itself. People, from the alpha geek to the noob for programming, having various background, can read and understand each line in the same way is important :) -- Mako 10:27, 9 May 2010 (UTC)

I think that line is meant to read "it will however not be damage enabled while it is not physical" at least from what I know about Linden Damage mechanics. I can, of course, be completely wrong. -- Faust 10:49, 9 May 2010 (UTC)

I believe Faust has the functionality described properly. Fred's most recent edit removed all mention of a Physics requirement. I'm pretty sure the object must be Physics enabled for it to give the damage and self destruct. The badly worded caveat was meant to convey that if you set it while the object wasn't physics enabled, it would retain the property, the functionality becoming active only when it became physics enabled. -- Strife ^{(talk|contribs)} 02:45, 10 May 2010 (UTC)

Nope. Physics do NOT need to be enabled. -- Fred Gandt ^{(talk|contribs)} 02:55, 10 May 2010 (UTC)