<\/p>\n
Incomplete as of 3\/29\/2021<\/strong><\/span><\/p>\n #1 – AutoReturn –<\/span> Triggered by throw1, throw2, or throw3<\/strong> #2 – Boomerang<\/span> – Triggered by throw1, throw2, or throw3<\/strong> #3 – BoomHoverDelay –<\/span> How long a Boomerang hovers in place after reaching target1<\/strong><\/p>\n #4 – CollisionPostActions <\/strong><\/span>– Cause the “Posts Collision” parameters to be examined and performed upon collision.<\/p>\n #5 – CollisionPostActions2<\/strong><\/span> – Same as CollisionPostActions but uses ApplyImpulse2 and AngularVelocity2 instead<\/p>\n #6 – CollisionPostActions3<\/span><\/strong> – Same as CollisionPostActions but uses ApplyImpulse3 and AngularVelocity3 instead<\/p>\n #7 – IgnoreFirstCollision<\/strong><\/span> – bypasses “Posts Collision” parameters. #8 – RangePostActions,<\/strong>off<\/span><\/span> – this must be on<\/span> <\/strong>in order to process “Posts Range” parameters when thrower is “in range” of target<\/p>\n #9 – Receiver<\/span><\/strong> – When NOT ZERO, the thrower will attach to a secondary person. This allows someone other than the thrower to “catch” a thrown Palette. The secondary person must touch Palette and grant ATTACH permission. The body part is the number following Receiver<\/p>\n #10 – RemoveFolder<\/span><\/strong> – If not BLANK then the script will sleep for RemoveFolderDelay seconds then remove the full contents of the RLV RemoveFolder. This name must be fully qualified and be located #11 – RemoveFolderDelay<\/span><\/strong> – Number of seconds after throw before contents of RemoveFolder are removed. Ignored if RemoveFolder is BLANK.<\/p>\n #12 – RezM<\/span><\/strong>e – Use this when you want to rez the inner Palette PERMANENTLY when RezObjectName has a value and (Thrower0123OnRez must be 1,2, or 3 OR Boomerang is on). A rezzable Palette must have either RezMe or TempRezMe on, otherwise the inner rezzable Palette will not rez.<\/p>\n #13 – Ricochet<\/strong><\/span> – Used to control a target1 AND a target2. Works same as Boomerang but there is no auto-attach at end. #14 – ShowInMidFlightAfte<\/span><\/strong>r – if this is not zero then maximum visibility is delayed the amount of seconds entered on the nc. Of course the success of this assumes that it is thrown with visibility off (at MinAlpha). #15 – ThrowOnCollid<\/strong>e<\/span> – this will cause this Palette to execute a throw upon colliding with another object…An example is the 3-hat-carom demo video. The value must be 1, 2, or 3 to tell the thrower which throw (ApplyImpulse and AngularVelocity) to execute<\/p>\n \/*Rezzer section<\/span><\/strong> #16 – Rezzer,on<\/span><\/span><\/strong> – This must be ON and when on causes the RezObjectName to automatically become a candidate for a rezzed throw. This makes this Palette the “rezzer Palette”.<\/p>\n #17 – RezObjectName,HatTemp<\/span><\/span><\/strong> – this is the name of a Palette that must be inside the ‘rezzers’ inventory and will be propelled using its own parameters of how it is to be thrown.<\/p>\n #18 – RezSource,<\/span>HatSource<\/span> <\/strong>– the name of an object that will be used to tell the rezzed object where to rez and what rotation it should have. The Rez Velocity matches the ApplyImpulse value.<\/p>\n #19 – Thrower0123OnRez<\/span><\/strong>,1<\/span> – This tells the rezzer what value to pass to the rezzed Palette so it knows which ApplyImpulse\/AngularVelocity pair to use. It will automatically throw upon rezzing if this parameter has a value.<\/p>\n \/*Targets Section<\/strong><\/span> – this is where you specify target names. They are used to #20 – DirectionalVector,<\/span>Local<\/span> <\/strong>– I have only used “Local<\/strong>” but the other value is “World<\/strong>“. World might be easier to work with if your practice site is the same location as your show-time site. When specifying rotational vectors, its important that you go in to EDIT on the Palette and make sure the reference matches. Local<\/strong> if Local<\/strong> and World<\/strong> if World<\/strong><\/p>\n #21 – ThrowerTarget,<\/span><\/strong>(off\/Both\/Avatar\/Objec<\/span><\/strong>t) – If this is off<\/span> <\/strong>then the next 3 fields are ignored. #22 – ThrowerObjectTargetName1<\/span><\/strong>,HatTarget1<\/span> <\/strong>– name of the target1. Required when ThrowerTarget is Both or Object \/*Motions Section – only one usually<\/span><\/strong> #25 – ApplyImpulse or MoveToTarget<\/span><\/strong><\/p>\n #26 – SetApplyImpulse<\/span><\/strong>,off<\/span> <\/strong>– if this is off<\/span> <\/strong>then the 3 ApplyImpulses<\/strong> are ignored. If on <\/b><\/span>then all may be in play depending on the throw (i.e. throw1, throw2, and throw3)<\/p>\n #27 – ApplyImpulse<\/span><\/strong>,<x,y,z><\/span><\/strong> – If SetApplyImpulse<\/strong> <\/span>is on<\/span> <\/strong>and a throw1 is executed then this becomes the instantaneous impulse. This will decay over time assuming there is some gravity and the Palette will fall to the ground. This is the motion-method I use most often. It reacts to mass(density) and applies 1 newton of force of acceleration equal to 1kg thrust one meter and lasting 1 second, per unit of xyz, velocity in the direction xyz and for a magnitude of (xyz) (effective inertial velocity) . Using it will force the Palette to go physical. It is center-of-mass based so be careful with link-sets. The velocity caps are dependent on the energy, a topic for another discussion but keep in mind 202 meters\/sec as a yardstick for very fast impulses.<\/p>\n #28 – ApplyImpulse2<\/span><\/strong>,<x,y,z><\/span><\/strong> – same as ApplyImpulse<\/strong> only it is used in place of ApplyImpulse when a throw2 action is taken<\/p>\n #29 – ApplyImpulse3<\/strong><\/span>,<x,y,z><\/span><\/strong> – same as ApplyImpulse<\/strong> only it is used in place of ApplyImpulse when a throw3 action is taken<\/p>\n #30 – SetMoveToTarget,<\/span>off<\/span><\/strong> – when off<\/span><\/strong>, then MoveToTargetTau<\/strong> and AtTargetRange<\/strong>, are ignored #31 – SetVelocity<\/span><\/strong>,off<\/span> <\/strong>– when on<\/strong> <\/span>will apply an instantaneous impulse the same as ApplyImpulse<\/strong> only “mass” is not taken into consideration. The direction and magnitude is dependent upon the velocity vector as specified by Velocity<\/p>\n #32 – SetAngularVelocity<\/span><\/strong>,off<\/span><\/strong> – when on<\/span> <\/strong>the appropriate AngularVelocity<\/strong> (rotation) is applied dependent on whether the throw is a throw1, throw2, or throw3<\/p>\n #33 – AngularVelocity,<\/span><x,y,z><\/span><\/strong> – used if a throw1 and SetAngularVelocity<\/strong> is on<\/span><\/strong>. Applies a rotational force ( 1 radian – about 1\/6th of a full-rotation) per second that causes the Palette to rotate in the xyz direction and with a force-magnitude of xyz and usually applied in combination with ApplyImpulse<\/strong> to create a tumble or Frisbee type throw. It will slow down over time but acts as if there is no mass. The Palette will turn physical and angular-velocity stops if and when the Palette turns non-physical<\/p>\n #34 – AngularVelocity2<\/span><\/strong>,<x,y,z><\/span><\/strong> – same as AngularVelocity<\/strong> only this applies only for a throw2<\/strong><\/p>\n #35 – AngularVelocity<\/span>3<\/span><\/strong>,<x,y,z><\/span><\/strong> – same as AngularVelocity<\/strong> only this applies only for a throw3<\/strong><\/p>\n #36 – SetTargetOmega<\/span><\/strong>,off<\/span> <\/strong>– when on<\/span> <\/strong>then TargetOmega<\/strong> will execute a spin on the client using the 1st parameter as a axis-spin direction. This never decays over time so use post-actions to stop spins.<\/p>\n #37 – TargetOmega<\/span><\/strong>,<1.0,0.0,0.0>,6.283185,2.0><\/span><\/strong> – this example spins around the x-axis at 2 x 2PI-radians) per second. Thats\u00a0 2 rotations per second (using 2.0 as gain…and it says the spin-rate is 2-pi (6.283185) radians which is 1 full rotation)<\/p>\n \/*Posts Collision<\/span><\/strong> – This section dictates the disposition of a Palette upon collision<\/strong><\/span>. For these to be effective, there must be CollisionPostActions1<\/strong>, CollisionPostActions2<\/strong>, or CollisionPostActions3<\/strong>. Either one or multiple ones will always cause all the post-actions to occur if on.<\/p>\n #38 – DamageFinishOnCollide<\/strong><\/span>,off,-55,Blood On,1.0,Animate,ArtistePalette_04_B,Spin Fall,10,Crawl,5,KILL_MESH #39 – DamageFinishOnRange<\/strong><\/span>,off<\/strong><\/span>,-55,Blood On,1.0,Animate,ArtistePalette_04_B,Spin Fall,10,Crawl,5,KILL_MESH<\/span><\/strong>
\nOnly applies if:
\ngreater than zero
\nIS Throwable:
\nNOT FollowSpotable
\nand NOT Attachable
\nChanges to NON-PHYS
\nhappens in Receiver script<\/p>\n
\nRicochet must be OFF
\n1st Target is always ThrowerObjectTargetName1
\n2nd Target is always ThrowerObjectTargetName2
\nCollision Post Actions are Ignored
\nReverses any Spin
\nStops Angular Vel.
\nAttaches IF AttachOnRange and Attachable<\/p>\n
\nRezzing a Palette in same position as
\nrezzer can cause a premature collision which we want to ignore
\nNEW for 2021!<\/span><\/strong> Automatically ignores collisions within 1 meter of rezzer so no need for Ingnore unless there
\nIS a collision down the way that you want to ignore.<\/p>\n
\nunder #RLV and RLV must be enabled. The folder must be WORN prior in order to activate it.<\/p>\n
\n1st Target is always ThrowerObjectTargetName1
\n2nd Target is always ThrowerObjectTargetName2
\nIt only responds to 2 targets maximum.
\nRangePost Actions must be enabled since Ricochet expects to use targeting.
\nAttaching is disabled.<\/p>\n
\nIt shows just before Matrix and RemoveFolder<\/p>\n
\nThese are the important parameters you will need in order to make a rezzer. Its why they are grouped together. Rezzers are used to simulate an attached-throw. as in someone holding a Palette and throwing or dropping it.<\/p>\n
\n1) either to guide a throw using SetMoveToTarget,on AND\/OR
\n2) used for controlling the Post Target disposition.<\/p>\n
\nif Both<\/strong>, then ThrowerObjectTargetName1<\/strong> and ThrowerObjectTargetName2<\/strong>
\nmust exist and are used for 2-phase throwing.
\nIf Object then only ThrowerObjectTargetName1<\/strong> is required If Avatar then only ThrowerAvatarTargetName<\/strong> is required
\nRicochet<\/strong> and Boomerang<\/strong> require Both<\/strong><\/p>\n
\n#23 – ThrowerObjectTargetName2<\/span>,HatTarget2<\/span> <\/strong>– name of the target2. Only required when .ThrowerTarget is Both
\n#24 – ThrowerAvatarTargetName<\/span><\/strong>,Lat Lovenkraft<\/span><\/strong> – name of an avatar that is to be target when ThrowerTarget is Avatar<\/p>\n
\nThis section has choices for the motion and propulsion method of the throw. Usually you will choose either<\/p>\n
\nwhen on<\/span> <\/strong>, this Palette behaves like a heat-seeking-missile IF a thrower-target has been specified(not off). Depending on other conditions, the Palette will move towards the target upon a throw and stop when it gets at or near the target. The flightpath will curve upward or downward to meet the target AGAINST the normal gravitational forces that are most likely in play.<\/p>\n
\n<\/span><\/strong>This newly added feature in 2021<\/strong><\/span> is a combination of events. Shoot<\/strong>, affect<\/strong>, animation1<\/strong>, animation2<\/strong>, kill\/die<\/span><\/strong>.
\nIt has delays that apply to the previous parameter.\u00a0 It has no effect if off<\/span><\/strong>.\u00a0 This choice happens when there is a collision<\/strong><\/span>.<\/span><\/span><\/p>\n
\nThis newly added feature in 2021<\/strong><\/span> is a combination of events. Shoot<\/strong>, affect<\/strong>, animation1<\/strong>, animation2<\/strong>, kill\/die<\/span><\/strong>.