darthsLair on 13/2/2015 at 08:28
I am following a Fidcal tutorial on frobbing in inventory:
(
http://www.ttlg.com/forums/showthread.php?t=83128&p=1033796&viewfull=1#post1033796) http://www.ttlg.com/forums/showthread.php?t=83128&p=1033796&viewfull=1#post1033796
Following this tutorial, I am attempting to use a disguise to get past a couple of ai that know me. Once I get a successful change of behavior, then the disguise won't matter.
I am using a lamp set on minimum to test the ability and reliability of a turnon with a cd to a conversation to set the M-AlertCapZero on some key ai's. The funny thing is, that it won't work the first two times, but it will the 3rd,4th, and 5th time. It then repeats with about the same results. It is not reliable using a conversation according to my experiments.
I am using some M-FrontGateGuards elsewhere, and find it more reliable. I always thought that M-AlertCapZero was more reliable, but now I am beginning to wonder about setting M-FrontGateGuard to them instead of Just M-AlertCapZero.
I have read everthing I can on M-AlertCapZero and the various response settings.
Can anyone suggest a proof positve way of setting Alert Cap to Zero,that will work everytime?
Thanks for any help.
R Soul on 13/2/2015 at 15:15
You don't need Inv Action
and Tool Action. Just one is needed, and I think it should be Inv Action. And you don't need FocusSctipt. The flags are explained (
http://dromed.whoopdedo.org/dromed/property/frobinfo) here.
You don't need stdButton on an inv object. TrigInvFrob is sufficient. You also don't need to use a conversation any more. You can install NVScript and use NVMetaTrap, or public scripts and use TrapMetaProp.
e.g. Put the NVMetaTrap script on each AI (when the property shows up, remove the other scripts and leave Don't Inherit unchecked). Add Editor > Design Note: NVMetaTrapMeta="M-Front Gate Guard"; NVMetaTrapCount=1
(unless you've renamed it in the hierarchy the name
does have spaces in it)
Give the lamp a CD link to each AI.
NVMetaTrapCount=1 means that if some event removes the metaprop (e.g. an alarm goes off and the AI become hostile again), frobbing the lamp again will not put the metaprop back on the AI. This is useful if some other event, e.g. an alarm, makes the AI hostile again.
The difference between M-AlertCapZero and M-Front Gate Guard? The second one allows the AI to be fully alert, just as they normally are if they see you, but it prevents them reacting. M-AlertCapZero stops alertness completely.
Your setup won't work if the conv actor is too far away. AI go into 'efficient' mode to save processing power and they stop doing things. There's an M-NeverEfficient metaprop if you really
need a conv actor. And I'm not sure what would happen if you added M-AlertCapZero to an AI who was already on high alert.
darthsLair on 13/2/2015 at 15:30
Thankyou Robin, I will use this metatrap. :thumb:
Edit: I am not sure how to rig up the disguise(shirt) using this NVMetaTrap script.
I placed NVMetaTrap script in scripts on each guard. What I do not understand, is since NVMetaTrapCount=1, doesn't this mean they are alerted one time, and also that they are already alerted with =1?
The shirt is the control device, but how do I add the NVMetaTrap editor design note to the ai using the shirt to activate it?
Thanks for any help Robin. Edit: nevermind, I figured it out. Thanks again!
