Every-time-argument - Revision history

Goober5000 at 03:46, 10 August 2007

2007-08-10T03:46:03Z

← Older revision		Revision as of 03:46, 10 August 2007
Line 10:		Line 10:
	Rest: Actions to take when the boolean expression becomes true.		Rest: Actions to take when the boolean expression becomes true.
	===Comments===		===Comments===
	<tt>[[Every-time]]</tt> and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will be evaluated in every single frame, they add a measurably larger performance overhead than a regular [[when]] or [[when-argument]] sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.		<tt>[[Every-time]]</tt> and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will be evaluated in every single frame, they add a measurably larger performance overhead than a regular <tt>[[when]]</tt> or <tt>[[when-argument]]</tt> sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.

	When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.		When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.

	[[Category:SCP SEXPs]]		[[Category:SCP SEXPs]]

Goober5000: we follow English grammar here

2007-08-10T03:42:43Z

we follow English grammar here

← Older revision		Revision as of 03:42, 10 August 2007
Line 10:		Line 10:
	Rest: Actions to take when the boolean expression becomes true.		Rest: Actions to take when the boolean expression becomes true.
	===Comments===		===Comments===
	<tt>[[~~every~~-time]]</tt> and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will be evaluated in every single frame, they add a measurably larger performance overhead than a regular [[when]] or [[when-argument]] sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.		<tt>[[Every-time]]</tt> and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will be evaluated in every single frame, they add a measurably larger performance overhead than a regular [[when]] or [[when-argument]] sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.

	When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.		When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.

	[[Category:SCP SEXPs]]		[[Category:SCP SEXPs]]

Goober5000 at 03:42, 10 August 2007

2007-08-10T03:42:05Z

← Older revision		Revision as of 03:42, 10 August 2007
Line 10:		Line 10:
	Rest: Actions to take when the boolean expression becomes true.		Rest: Actions to take when the boolean expression becomes true.
	===Comments===		===Comments===
	[[every-time]] and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will ~~execute~~ in every single frame, they add a measurably larger performance overhead than a regular [[when]] or [[when-argument]] sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.		<tt>[[every-time]]</tt> and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will be evaluated in every single frame, they add a measurably larger performance overhead than a regular [[when]] or [[when-argument]] sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.

	When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.		When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.

	[[Category:SCP SEXPs]]		[[Category:SCP SEXPs]]

Shade: 2 links added

2007-08-08T12:33:31Z

2 links added

← Older revision		Revision as of 12:33, 8 August 2007
Line 10:		Line 10:
	Rest: Actions to take when the boolean expression becomes true.		Rest: Actions to take when the boolean expression becomes true.
	===Comments===		===Comments===
	[[every-time]] and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will execute in every single frame, they add a measurably larger performance overhead than a regular ~~<tt>~~when~~</tt>~~ or ~~<tt>~~when-argument~~</tt>~~ sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.		[[every-time]] and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will execute in every single frame, they add a measurably larger performance overhead than a regular [[when]] or [[when-argument]] sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.

	When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.		When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.

	[[Category:SCP SEXPs]]		[[Category:SCP SEXPs]]

Shade: link added

2007-08-08T12:29:40Z

link added

← Older revision		Revision as of 12:29, 8 August 2007
Line 10:		Line 10:
	Rest: Actions to take when the boolean expression becomes true.		Rest: Actions to take when the boolean expression becomes true.
	===Comments===		===Comments===
	~~<tt>Every~~-time~~</tt>~~ and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will execute in every single frame, they add a measurably larger performance overhead than a regular <tt>when</tt> or <tt>when-argument</tt> sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.		[[every-time]] and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will execute in every single frame, they add a measurably larger performance overhead than a regular <tt>when</tt> or <tt>when-argument</tt> sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.

	When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.		When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.

	[[Category:SCP SEXPs]]		[[Category:SCP SEXPs]]

Goober5000: added a developer warning and removed questionable advice

2007-08-08T02:17:31Z

added a developer warning and removed questionable advice

← Older revision		Revision as of 02:17, 8 August 2007
Line 10:		Line 10:
	Rest: Actions to take when the boolean expression becomes true.		Rest: Actions to take when the boolean expression becomes true.
	===Comments===		===Comments===
	When using this, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between ~~triggerings~~ when using <tt>every-time</tt>~~, though this~~ can be ~~hacked~~ using ~~a combination of variables~~ and ~~the [[Mission-time\|mission-time]] SEXP to measure the desired delay - See the [[Stealthing Ships To Force Target Loss]] page in [[:Category:FRED_Examples\|FRED_Examples]] for how this can be done~~.		<tt>Every-time</tt> and <tt>every-time-argument</tt> should be used extremely rarely, if ever, and only with careful and cautious planning. Since these sexps will execute in every single frame, they add a measurably larger performance overhead than a regular <tt>when</tt> or <tt>when-argument</tt> sexp. Worse, since framerate can vary greatly between computers and even between playthroughs, improper use of these sexps can lead to wildly unpredictable (and even incorrect) results, as was famously demonstrated in the first few versions of [[The Procyon Insurgency]]. As described in the help texts, these sexps should ''only'' be used for volatile conditions that may become true more than once.

			When using this sexp, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between firings when using <tt>every-time</tt>. It can be done, but only using advanced (and often complicated) methods.

	[[Category:SCP SEXPs]]		[[Category:SCP SEXPs]]

Shade: New page: every-time-argument Every-time-argument (Conditional operator) This is a version of "when-argument" that will always evaluate its arguments. It's useful in situations where you ...

2007-07-31T09:47:06Z

New page: every-time-argument Every-time-argument (Conditional operator) This is a version of "when-argument" that will always evaluate its arguments. It's useful in situations where you ...

New page

every-time-argument
Every-time-argument (Conditional operator)
This is a version of "when-argument" that will always evaluate its arguments. It's useful in situations where you need to
repeatedly check things that may become true more than once. Since this sexp will execute every time it's evaluated,
you may need to use it as an argument to "when" (not "when-argument") if you want to impose restrictions on how it's called.

Takes 3 or more arguments...
1: The arguments to evaluate (see any-of, all-of, random-of, etc.).
2: Boolean expression that must be true for actions to take place.
Rest: Actions to take when the boolean expression becomes true.
===Comments===
When using this, be careful that the conditions for it to trigger will not cause it to accidentally trigger indefinitely. Also, unlike a standard repeating event, there is no simple way to set a delay between triggerings when using <tt>every-time</tt>, though this can be hacked using a combination of variables and the [[Mission-time|mission-time]] SEXP to measure the desired delay - See the [[Stealthing Ships To Force Target Loss]] page in [[:Category:FRED_Examples|FRED_Examples]] for how this can be done.

[[Category:SCP SEXPs]]