Dr Eyeball – User talk

From Bohemia Interactive Community
Jump to navigation Jump to search
(deleting triggers)
No edit summary
Line 15: Line 15:
:Nah - I was just teasing raedor... ;)
:Nah - I was just teasing raedor... ;)
:He hadn't expected that somebody would've deleted a trigger underneath him, and this was causing an error. But the command itself is harmless. --[[User:Kronzky|Kronzky]] 06:32, 2 October 2008 (CEST)
:He hadn't expected that somebody would've deleted a trigger underneath him, and this was causing an error. But the command itself is harmless. --[[User:Kronzky|Kronzky]] 06:32, 2 October 2008 (CEST)
::I see. Then we don't use it as the trigger is still "there" after deleting, and it is still returned in the [[triggers]] array (we just like set the condition to false and move it to [0,0]).
::Okay, so you can delete this one day, DrEyeball ;) --[[User:Raedor|raedor]] 10:14, 2 October 2008 (CEST)

Revision as of 10:14, 2 October 2008

Triggers + deleteVehicle

Did you ever test this? As far as I know deleteVehicle does not have any effect on triggers. --raedor 20:17, 1 October 2008 (CEST)

  • Definitely works! Even recently caused a script error in your trigger color selection (editor rev. 734), because somebody was deleting triggers inside the mission :D --Kronzky 20:47, 1 October 2008 (CEST)
  • I have used it a few times - in my real-time Merlin editor, for IED's, objectives, etc in both SP & MP. It definitely disables the trigger and I have never seen a problem with it yet.

I guess the confusing part is if you display a trigger in a format statement, it shows something like "276361: <NO SHAPE>", then even after you delete it, it still shows the same value although it has been disabled.

I'm not sure what would happen if you attempt to manipulate it after that. Does it still exist as a disabled trigger in some usable form, or is it truly deleted.

Kronzky, your reply could be misinterpreted when saying "it works" and "caused a script error" in the same statement. I'm pretty sure you're saying it works but someone has used it incorrectly? Dr Eyeball 04:35, 2 October 2008 (CEST)

Nah - I was just teasing raedor... ;)
He hadn't expected that somebody would've deleted a trigger underneath him, and this was causing an error. But the command itself is harmless. --Kronzky 06:32, 2 October 2008 (CEST)
I see. Then we don't use it as the trigger is still "there" after deleting, and it is still returned in the triggers array (we just like set the condition to false and move it to [0,0]).
Okay, so you can delete this one day, DrEyeball ;) --raedor 10:14, 2 October 2008 (CEST)