Howto: Disable a pressure plate trap via a switch

[Bikerdude]

Evening

 

So I am trying to repurpose a Presure_plate_trap from one of my maps (see attached)

 

The issue I want to be able to disable the trap from firing and the pressure place from moving via a switch...

 

Any idea's..?

 

Pressure_plate_trap.pfb.txt

[ERH+]

Script with $trigger_multiple_1.remove(); ?

 

or

scriptEvent void disable(); Disables the mover/trigger

 

scriptEvent void enable(); Enables the mover/trigger Edited May 7, 2016 by ERH+

[SteveL]

You could use a func_remove instead of a script to remove the trigger. It's an extra entity but on the plus side, no scripting and it can be packaged as part of your prefab.

[Bikerdude]

@ERH, so to add this into the map.script file it would look as follows..?

void pressure_plate_trap()
{
     scriptEvent void disable($pp_trigger_multiple_01); Disables the mover/trigger
     scriptEvent void enable($pp_trigger_multiple_01); Enables the mover/trigger 
}

And I assume I will have to target a "atdm:target_callscriptfunction" from the switch..?

 

@Steve, the issue is I want to disable/enable the trap from the switch. I assume the func_remove would permanently remove it from the map? or will the func_remove replace the removed item when targeted from a switch..?

[SteveL]

@Steve, the issue is I want to disable/enable the trap from the switch. I assume the func_remove would permanently remove it from the map? or will the func_remove replace the removed item when targted from a switch..?

Ah, ok. The func_remove would remove it permanently.

 

Gimme a few mins before you try a script. I am sure this can be done without...

[Bikerdude]

Awesome, ta.

[SteveL]

I was thinking that you could use an atdm::target_postscriptevent to call the Enable() and Disable() methods on the trigger. You could, but you'd have to use a complicated setup involving atdm::target_changetargets to toggle between the enabler and the disabler.

Easier just to go for a script like ERH+ suggested

 

(untested) For your map script file:

float pressure_plate_active = 1;
void toggle_pressure_plate_trap()
{
    entity trap_trigger = $trigger_multiple_1;   // PUT THE NAME OF YOUR TRIGGER HERE BETWEEN THE $ AND ;
    if ( pressure_plate_active == 1 )
    {
        trap_trigger.disable();
        pressure_plate_active = 0;
    } else {
        trap_trigger.enable();
        pressure_plate_active = 1;
    }
}

Then create an atdm::target_callscriptfunction and giuve it spawnarg "call" "toggle_pressure_plate_trap", and target it from your switch.

 

Edit: Fixed per Biker's post below

Edited May 7, 2016 by SteveL

[Bikerdude]

Grand thanks Steve, already had the "atdm::target_callscriptfunction" in place so testing now....

 

[update]

 

Got an error on map load, it complains about line " trap_trigger.Disable();" saying unknown value "Disable". So I changed first letter on Disable and Enable to lower case on a wild guess and that fixed it.

[SteveL]

Grand thanks Steve, already had the "atdm::target_callscriptfunction" in place so testing now....

 

[update]

 

Got an error on map load, it complains about line " trap_trigger.Disable();" saying unknown value "Disable". So I changed first letter on Disable and Enable to lower case on a wild guess and that fixed it.

 

Oops, my bad. Those functions are upper case in the c++ code, but lower case for game scripts. Not by accident, it's meant to stop them getting confused. Except that I did get confused and I remembered it the wrong way round. Cool you got it sorted

[Bikerdude]

Dont know if is a script issue or a DR issue, but flipping the switch has no effect. Will look at it again tomoz, Ive commited the latest version of the map if you want to have a look.

[SteveL]

Ack, happy to take a look if needed.

[demagogue]

The lazy way would be to use two pressure plate entities (a functional and inert one) on top of each other and just mutually spawn/remove them with the switch. But if the script functions work then you've already solved it and just have to get it set up right.

[Bikerdude]

Ack, happy to take a look if needed.

I'll drop you a PM

[SteveL]

For anyone finding this thread later, the script above does work ok.

[Bikerdude]

it was a small typo on my part.