I know that Proximity triggers dont work with container spawns, but Im wondering if it is possible to set a spawner outside the container to set the proximity msg and triggeroncarried - then when the triggermob passes the carried check it would then pass an "ok to spawn" sorta thing to the other (in container) spawner - using an external trigger or sequential spawn.
Is this possible?
Dis~
| QUOTE (Discord @ June 19, 2006 12:21 pm) |
I know that Proximity triggers dont work with container spawns, but Im wondering if it is possible to set a spawner outside the container to set the proximity msg and triggeroncarried - then when the triggermob passes the carried check it would then pass an "ok to spawn" sorta thing to the other (in container) spawner - using an external trigger or sequential spawn.
Is this possible?
Dis~ |
yes, this is possible.
Set the container spawner to external-triggering-only by setting ProximityRange to -2. That way it will never spawn or trigger unless the ProximityActivated flag is manually set to true.
Then have the triggered spawner set the ProximityActivated flag on the container spawner by using a spawn entry something like
SET,spawnername,xmlspawner/proximityactivated/true
from xmlspawner2.txt
| QUOTE |
- added the donthurtme.xml example to xmlextras that demonstrates the manual ProximityActivated modifications with forced external triggering (ProximityRange = -2). To test it out, just load it and then damage the orc that spawns. That will trigger the second spawner which is in forced external triggering mode. (thanks to Sou^^ for the example idea).
|
Just an update for anyone who reads this, version 3.11 does now seem to allow external triggering in a container. I have it triggering on a skill check, works perfectly.
Lara
