When a prop is moved from one location to another, the prop plugin reports back to nPose a new position. In some cases moving props are wanted and the prop plugin keeps reporting back.

It would be nice to have a quiet mode for props to be used when props are in continual or semi-continual motion.

See nPoseTeam/nPose-V3#23

See: nPoseTeam/nPose-V4#4

With my last commit I changed the scriptname to "nPose Prop Plugin"... That is because I had a issue some time ago with the "Reset all scripts" button in the edit window of the viewer:

I had an object with 2 scripts: one scriptname started with "a" and one scriptname started with "x". In the objects inventory was also about a hundret animations with different names (beginning between "a" and "x". When I then pressed the "Reset all scripts" button I noticed that script "a" came back from the reset a lot earler than script "x". So early that it misses some information send by script "a" via linkmessage in the state_entry() event.
This didn't happen after I renamed script "x" to "ax".
My conclusion was: It is a very good idea to start the name of the scripts that communicate with each other with similar names.

So if we put "nPose " in front of all our scripts the above issue shouldn't happen (often).

(Because of the above issue I also use a small llSleep() inside the state_entry() before I send informations across the object.)

This can be closed ;)

https://jira.secondlife.com/browse/BUG-228939

I guess we will see things like: messages are not recieved by newly rezzed props ...

nPose Prop Plugin V4.00: There is a small chance that the bug will affect this version of the Prop Plugin because the timeout is set to 3.0s (line 16: float PROP_TIMEOUT=3.0;). It is possible that we have to increase this value.

older Prop scripts: depends on the PAUSE between the PROP command and subsequently LINKMSGs. As far as I remember the bug may also have an impact on props rezzed more than 10m away.