cheers for that bit of infoBTW, you can set the exploder off in the script too. So, you don't have to name the trigger "explodertrigger".
exec global/ecploder.scr::explode 1 // set off exploder set 1
tnx again tltrude
Moderator: Moderators
cheers for that bit of infoBTW, you can set the exploder off in the script too. So, you don't have to name the trigger "explodertrigger".
exec global/ecploder.scr::explode 1 // set off exploder set 1
Code: Select all
areaportal_controls:
$alliesweaponsroom_portal closeportal
$axisweaponsroom_portal closeportal
$alliesweaponsroom_door closeportal
$axisweaponsroom_door closeportal
Code: Select all
CM_AdjustAreaPortalState : negative reference countyeah,thats what ive been usingYour triggers, with health, can still use "setthread" to run the thread that has "exec global/exploder.scr:: explode 1" and the openportal line.
well,there is a func door nearby but it isnt that close to it.both of the doors are at the end of a corridor ,one of them is a script object and the other is a fun_door and tey are on opposite sides of the corridors walls.That error sounds like you are giving the command to close the portal twice. Remember, a func type door needs no help to open and close its portal. If a script_object door is near a func_door, that might happen.