Trigger changevalue - Revision history

Outerbeast: Remove /* Issues */

2025-10-07T10:06:27Z

Remove Issues

← Older revision		Revision as of 12:06, 7 October 2025
Line 32:		Line 32:
	* Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per <code>spawnflags</code>.		* Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per <code>spawnflags</code>.
	* When trying to change the value of a [[Custom Keyvalues\|custom key]] for an entity but that custom key doesn't yet exist, it will initialise that key first before writing to it.		* When trying to change the value of a [[Custom Keyvalues\|custom key]] for an entity but that custom key doesn't yet exist, it will initialise that key first before writing to it.

	~~== Issues ==~~
	trigger_changetarget only changes the target of one entity, the first one it can find, if there are several entities of the same name that the changetarget targets - trigger_changevalue can update multiple entities at the same time if they share the same name, so this can be used instead.
	~~<br> This is fixed in 5.26.~~


	{{entity_title}}		{{entity_title}}

Outerbeast: /* Notes */

2025-10-07T10:05:53Z

Notes

← Older revision		Revision as of 12:05, 7 October 2025
Line 31:		Line 31:
	* Trigger_changevalue supports the use of "!activator" and "!caller" in the "Destination Entity" field.		* Trigger_changevalue supports the use of "!activator" and "!caller" in the "Destination Entity" field.
	* Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per <code>spawnflags</code>.		* Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per <code>spawnflags</code>.
			* When trying to change the value of a [[Custom Keyvalues\|custom key]] for an entity but that custom key doesn't yet exist, it will initialise that key first before writing to it.

	== Issues ==		== Issues ==

Outerbeast: /* Notes */

2023-05-28T19:35:46Z

Notes

← Older revision		Revision as of 21:35, 28 May 2023
Line 29:		Line 29:
	== Notes ==		== Notes ==

	Trigger_changevalue supports the use of "!activator" and "!caller" in the "Destination Entity" field.		* Trigger_changevalue supports the use of "!activator" and "!caller" in the "Destination Entity" field.
			* Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per <code>spawnflags</code>.

	~~Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per spawnflags.~~		== Issues ==
			trigger_changetarget only changes the target of one entity, the first one it can find, if there are several entities of the same name that the changetarget targets - trigger_changevalue can update multiple entities at the same time if they share the same name, so this can be used instead.
	~~Unlike~~ trigger_changetarget, trigger_changevalue can update multiple entities at the same time if they share the same name.		<br> This is fixed in 5.26.

Loulimi: /* Notes */ Add note about multiple targets.

2023-05-23T21:04:50Z

Notes: Add note about multiple targets.

← Older revision		Revision as of 23:04, 23 May 2023
Line 29:		Line 29:
	== Notes ==		== Notes ==

	Trigger_changevalue supports the use of "!activator" and "!caller" in the "Destination Entity"-field.Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per spawnflags.		Trigger_changevalue supports the use of "!activator" and "!caller" in the "Destination Entity" field.

			Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per spawnflags.

			Unlike trigger_changetarget, trigger_changevalue can update multiple entities at the same time if they share the same name.

Outerbeast at 17:45, 12 May 2023

2023-05-12T17:45:25Z

← Older revision		Revision as of 19:45, 12 May 2023
Line 3:		Line 3:
	}}		}}

	Trigger_changevalue can perform arithmetic and logic operations on base-keyvalues of entities, as well as replace their private keyvalues. ~~See trigger_copyvalue for~~ a variant of this with more options. Supports custom keyvalues.		Trigger_changevalue can perform arithmetic and logic operations on base-keyvalues of entities, as well as replace their private keyvalues. See [[trigger_copyvalue]] for a variant of this with more options. Supports custom keyvalues.

	== Keyvalues ==		== Keyvalues ==

Outerbeast at 14:23, 11 May 2023

2023-05-11T14:23:03Z

← Older revision		Revision as of 16:23, 11 May 2023
Line 11:		Line 11:
	{{Entity_keyvalue\|Static source-value\|m_iszNewValue\|Value to be applied to the destination keyvalue.}}		{{Entity_keyvalue\|Static source-value\|m_iszNewValue\|Value to be applied to the destination keyvalue.}}
	{{Entity_keyvalue\|Operation\|m_iszValueType\|This specifies how destination keyvalue and static source-value correlate. What exactly happens also depends on the types		{{Entity_keyvalue\|Operation\|m_iszValueType\|This specifies how destination keyvalue and static source-value correlate. What exactly happens also depends on the types
	of the two. There are some academic things in here, so I shall explain some of them:Pow: Source value to the power of destination value. To keep things simple, zero to the power of zero magically equals one and taking a negative value to the power of a non-integer will cause the base to be treated as positive.Mod: Short for "Modulo", this calculates the rest of a division. For example, 63 % 13 equals 11, because 63 - 13 = 50,		of the two. There are some academic things in here, so I shall explain some of them:Pow: Source value to the power of destination value. To keep things simple, zero to the power of zero magically equals one and taking a negative value to the power of a non-integer will cause the base to be treated as positive.Mod: Short for "Modulo", this calculates the rest of a division. For example, 63 % 13 equals 11, because 63 - 13 = 50, 50 - 13 = 37, 37 - 13 = 24 and 24 - 13 = 11. Substracting a fifth time would deliver a negative result and is henceforth omitted. The actual computation of this value uses a smarter, fast method; this is just for presentiveness. Usage example: You have a value in seconds, e.g. 285, and want to know how many minutes and seconds that are, so you divide by 60 and get 4.75. Omitting the 0.75 you're left with 4. For the remaining seconds, you'd calculate 285 % 60 = 45, which
	50 - 13 = 37, 37 - 13 = 24 and 24 - 13 = 11. Substracting a fifth time would deliver a negative result and is henceforth omitted. The actual computation of this value uses a smarter, fast method; this is just for presentiveness. Usage example: You have a value in seconds, e.g. 285, and want to know how many minutes and seconds that are, so you divide by 60 and get 4.75. Omitting the 0.75 you're left with 4. For the remaining seconds, you'd calculate 285 % 60 = 45, which
	is the same as 60 * 0.75. Then you'd know that 285 seconds equals 4 minutes plus 45 seconds. Real numbers and negative values are supported.AND, OR, XOR, NAND, NOR, NXOR: These are logic operands which operate bitwise; the leading 'N' indicates bitwise negation after the operation. Example: An entity's spawnflags are stored in an integer which consists of 32 bits. Say you want to set the 7th checkbox of an entity's spawnflags, you need to make sure the 7th bit is set to 1. You hence need the integer number where only the 7th bit is set, which is 2 ^ (7 - 1) = 2 ^ 6 = 64. However, you cannot simply add this		is the same as 60 * 0.75. Then you'd know that 285 seconds equals 4 minutes plus 45 seconds. Real numbers and negative values are supported.AND, OR, XOR, NAND, NOR, NXOR: These are logic operands which operate bitwise; the leading 'N' indicates bitwise negation after the operation. Example: An entity's spawnflags are stored in an integer which consists of 32 bits. Say you want to set the 7th checkbox of an entity's spawnflags, you need to make sure the 7th bit is set to 1. You hence need the integer number where only the 7th bit is set, which is 2 ^ (7 - 1) = 2 ^ 6 = 64. However, you cannot simply add this
	to the existing spawnflags, because if the 7th bit was already set to 1, you'd cause it to be set to 0 and generate a carry which is sent to the 8th bit; the magic of positional notation systems - just as 500 + 500 equals 1000 in decimal,		to the existing spawnflags, because if the 7th bit was already set to 1, you'd cause it to be set to 0 and generate a carry which is sent to the 8th bit; the magic of positional notation systems - just as 500 + 500 equals 1000 in decimal, 100 + 100 equals 1000 in binary. You'd need to perform a bitwise OR. If you'd want only the 7th checkbox to be checked, you'd use replace-operation as usual. XOR means "Exclusive OR", as in "Either that or the other, but not both". AND means that both bits need to be 1 for the resulting bit to remain 1. You can imagine the logic operators perform 32 simultaneous operations on the combined 64 bits of two integers. Append (String concatenation): Appends your source value to the destination keyvalue. The later must be a string; otherwise this cannot work.}}
	100 + 100 equals 1000 in binary. You'd need to perform a bitwise OR. If you'd want only the 7th checkbox to be checked, you'd use replace-operation as usual. XOR means "Exclusive OR", as in "Either that or the other, but not both". AND means that both bits need to be 1 for the resulting bit to remain 1. You can imagine the logic operators perform		{{Entity_keyvalue\|Trigonometric funcs. I/O\|m_trigonometricBehaviour\|When using trigonometric or arc-functions as per the "Operation"-keyvalue, this is used to determine what your input/desired output measure is. You'll usually want to stick to degrees.}}
	32 simultaneous operations on the combined 64 bits of two integers.Append (String concatenation): Appends your source value to the destination keyvalue. The later must be a string; otherwise this cannot work."Trigonometric funcs. I/O~~", m_trigonometricBehaviour :~~		{{Entity_keyvalue\|Append spaces (for strings)\|m_iAppendSpaces\|When the destination keyvalue is a string, this specifies how many spaces to append after the operations. You'll usually want to use this with either the "Replace"- or "Append"-operation. This was implemented because Valve Hammer Editor omits any trailing spaces in keyvalues (but not leading ones).}}
	When using trigonometric or arc-functions as per the "Operation"-keyvalue, this is used to determine what your input/desired output measure is. You'll usually want to stick to degrees.}}
	{{Entity_keyvalue\|Append spaces (for strings)\|m_iAppendSpaces\|When the destination keyvalue is a string, this specifies how many spaces to append after the operations. You'll usually want
	to use this with either the "Replace"- or "Append"-operation. This was implemented because Valve Hammer Editor omits any trailing spaces in keyvalues (but not leading ones).}}
	{{Entity_keyvalue\|Trigger after operation\|message\|Set entity/entities to be triggered after the trigger_changevalue has set the new keyvalue, by targetname as usual.		{{Entity_keyvalue\|Trigger after operation\|message\|Set entity/entities to be triggered after the trigger_changevalue has set the new keyvalue, by targetname as usual.
	This is very useful when you need a chain of operations to happen in a specific order and without any delay in between.}}		This is very useful when you need a chain of operations to happen in a specific order and without any delay in between.}}

Outerbeast: losing grip on sanity

2023-05-11T14:20:03Z

losing grip on sanity

← Older revision		Revision as of 16:20, 11 May 2023
Line 10:		Line 10:
	{{Entity_keyvalue\|Destination Keyvalue\|m_iszValueName\|Name of the key which's value is to be changed.}}		{{Entity_keyvalue\|Destination Keyvalue\|m_iszValueName\|Name of the key which's value is to be changed.}}
	{{Entity_keyvalue\|Static source-value\|m_iszNewValue\|Value to be applied to the destination keyvalue.}}		{{Entity_keyvalue\|Static source-value\|m_iszNewValue\|Value to be applied to the destination keyvalue.}}
	{{Entity_keyvalue\|Operation\|m_iszValueType\|This specifies how destination keyvalue and static source-value correlate. What exactly happens also depends on the types of the two. ~~Check~~ the ~~notes section~~ to get a ~~detail explanation~~ for ~~usage~~ of ~~each choice~~.}}		{{Entity_keyvalue\|Operation\|m_iszValueType\|This specifies how destination keyvalue and static source-value correlate. What exactly happens also depends on the types
			of the two. There are some academic things in here, so I shall explain some of them:Pow: Source value to the power of destination value. To keep things simple, zero to the power of zero magically equals one and taking a negative value to the power of a non-integer will cause the base to be treated as positive.Mod: Short for "Modulo", this calculates the rest of a division. For example, 63 % 13 equals 11, because 63 - 13 = 50,
			50 - 13 = 37, 37 - 13 = 24 and 24 - 13 = 11. Substracting a fifth time would deliver a negative result and is henceforth omitted. The actual computation of this value uses a smarter, fast method; this is just for presentiveness. Usage example: You have a value in seconds, e.g. 285, and want to know how many minutes and seconds that are, so you divide by 60 and get 4.75. Omitting the 0.75 you're left with 4. For the remaining seconds, you'd calculate 285 % 60 = 45, which
			is the same as 60 * 0.75. Then you'd know that 285 seconds equals 4 minutes plus 45 seconds. Real numbers and negative values are supported.AND, OR, XOR, NAND, NOR, NXOR: These are logic operands which operate bitwise; the leading 'N' indicates bitwise negation after the operation. Example: An entity's spawnflags are stored in an integer which consists of 32 bits. Say you want to set the 7th checkbox of an entity's spawnflags, you need to make sure the 7th bit is set to 1. You hence need the integer number where only the 7th bit is set, which is 2 ^ (7 - 1) = 2 ^ 6 = 64. However, you cannot simply add this
			to the existing spawnflags, because if the 7th bit was already set to 1, you'd cause it to be set to 0 and generate a carry which is sent to the 8th bit; the magic of positional notation systems - just as 500 + 500 equals 1000 in decimal,
			100 + 100 equals 1000 in binary. You'd need to perform a bitwise OR. If you'd want only the 7th checkbox to be checked, you'd use replace-operation as usual. XOR means "Exclusive OR", as in "Either that or the other, but not both". AND means that both bits need to be 1 for the resulting bit to remain 1. You can imagine the logic operators perform
			32 simultaneous operations on the combined 64 bits of two integers.Append (String concatenation): Appends your source value to the destination keyvalue. The later must be a string; otherwise this cannot work."Trigonometric funcs. I/O", m_trigonometricBehaviour :
			When using trigonometric or arc-functions as per the "Operation"-keyvalue, this is used to determine what your input/desired output measure is. You'll usually want to stick to degrees.}}
	{{Entity_keyvalue\|Append spaces (for strings)\|m_iAppendSpaces\|When the destination keyvalue is a string, this specifies how many spaces to append after the operations. You'll usually want		{{Entity_keyvalue\|Append spaces (for strings)\|m_iAppendSpaces\|When the destination keyvalue is a string, this specifies how many spaces to append after the operations. You'll usually want
	to use this with either the "Replace"- or "Append"-operation. This was implemented because Valve Hammer Editor omits any trailing spaces in keyvalues (but not leading ones).}}		to use this with either the "Replace"- or "Append"-operation. This was implemented because Valve Hammer Editor omits any trailing spaces in keyvalues (but not leading ones).}}

Outerbeast: /* Keyvalues */

2023-05-11T14:18:11Z

Keyvalues

← Older revision		Revision as of 16:18, 11 May 2023
Line 10:		Line 10:
	{{Entity_keyvalue\|Destination Keyvalue\|m_iszValueName\|Name of the key which's value is to be changed.}}		{{Entity_keyvalue\|Destination Keyvalue\|m_iszValueName\|Name of the key which's value is to be changed.}}
	{{Entity_keyvalue\|Static source-value\|m_iszNewValue\|Value to be applied to the destination keyvalue.}}		{{Entity_keyvalue\|Static source-value\|m_iszNewValue\|Value to be applied to the destination keyvalue.}}
	{{Entity_keyvalue\|Operation\|m_iszValueType\|This specifies how destination keyvalue and static source-value correlate. What exactly happens also depends on the types		{{Entity_keyvalue\|Operation\|m_iszValueType\|This specifies how destination keyvalue and static source-value correlate. What exactly happens also depends on the types of the two. Check the notes section to get a detail explanation for usage of each choice.}}
	of the two. There are some academic things in here, so I shall explain some of them:Pow: Source value to the power of destination value. To keep things simple, zero to the power of zero magically equals one and taking a negative value to the power of a non-integer will cause the base to be treated as positive.Mod: Short for "Modulo", this calculates the ~~rest of a division. For example, 63 % 13 equals 11, because 63 - 13 = 50,~~
	50 - 13 = 37, 37 - 13 = 24 and 24 - 13 = 11. Substracting a fifth time would deliver a negative result and is henceforth omitted. The actual computation of this value uses a smarter, fast method; this is just for presentiveness. Usage example: You have a value in seconds, e.g. 285, and want to ~~know how many minutes and seconds that are, so you divide by 60 and~~ get ~~4.75. Omitting the 0.75 you're left with 4. For the remaining seconds, you'd calculate 285 % 60 = 45, which~~
	is the same as 60 * 0.75. Then you'd know that 285 seconds equals 4 minutes plus 45 seconds. Real numbers and negative values are supported.AND, OR, XOR, NAND, NOR, NXOR: These are logic operands which operate bitwise; the leading 'N' indicates bitwise negation after the operation. Example: An entity's spawnflags are stored in an integer which consists of 32 bits. Say you want to set the 7th checkbox of an entity's spawnflags, you need to make sure the 7th bit is set to 1. You hence need the integer number where only the 7th bit is set, which is 2 ^ (7 - 1) = 2 ^ 6 = 64. However, you cannot simply add this
	to the existing spawnflags, because if the 7th bit was already set to 1, you'd cause it to be set to 0 and generate a carry which is sent to the 8th bit; the magic of positional notation systems - just as 500 + 500 equals 1000 in decimal,
	~~100 + 100 equals 1000 in binary. You'd need to perform~~ a bitwise OR. If you'd want only the 7th checkbox to be checked, you'd use replace-operation as usual. XOR means "Exclusive OR", as in "Either that or the other, but not both". AND means that both bits need to be 1 for ~~the resulting bit to remain 1. You can imagine the logic operators perform~~
	~~32 simultaneous operations on the combined 64 bits~~ of two integers.Append (String concatenation): Appends your source value to the destination keyvalue. The later must be a string; otherwise this cannot work."Trigonometric funcs. I/O", m_trigonometricBehaviour :
	~~When using trigonometric or arc-functions as per the "Operation"-keyvalue, this is used to determine what your input/desired output measure is. You'll usually want to stick to degrees~~.}}
	{{Entity_keyvalue\|Append spaces (for strings)\|m_iAppendSpaces\|When the destination keyvalue is a string, this specifies how many spaces to append after the operations. You'll usually want		{{Entity_keyvalue\|Append spaces (for strings)\|m_iAppendSpaces\|When the destination keyvalue is a string, this specifies how many spaces to append after the operations. You'll usually want
	to use this with either the "Replace"- or "Append"-operation. This was implemented because Valve Hammer Editor omits any trailing spaces in keyvalues (but not leading ones).}}		to use this with either the "Replace"- or "Append"-operation. This was implemented because Valve Hammer Editor omits any trailing spaces in keyvalues (but not leading ones).}}

GeckonCZ: Import of converted entguide pages from Sven Manor.

2019-01-27T22:29:32Z

Import of converted entguide pages from Sven Manor.

New page

{{Entity_Infobox
| title=
}}

Trigger_changevalue can perform arithmetic and logic operations on base-keyvalues of entities, as well as replace their private keyvalues. See trigger_copyvalue for a variant of this with more options. Supports custom keyvalues.

== Keyvalues ==

{{Entity_keyvalue|Destination Entity|target|Name of the entity which's keyvalue is to changed. This can refer to more than one.}}
{{Entity_keyvalue|Destination Keyvalue|m_iszValueName|Name of the key which's value is to be changed.}}
{{Entity_keyvalue|Static source-value|m_iszNewValue|Value to be applied to the destination keyvalue.}}
{{Entity_keyvalue|Operation|m_iszValueType|This specifies how destination keyvalue and static source-value correlate. What exactly happens also depends on the types
of the two. There are some academic things in here, so I shall explain some of them:Pow: Source value to the power of destination value. To keep things simple, zero to the power of zero magically equals one and taking a negative value to the power of a non-integer will cause the base to be treated as positive.Mod: Short for "Modulo", this calculates the rest of a division. For example, 63 % 13 equals 11, because 63 - 13 = 50,
50 - 13 = 37, 37 - 13 = 24 and 24 - 13 = 11. Substracting a fifth time would deliver a negative result and is henceforth omitted. The actual computation of this value uses a smarter, fast method; this is just for presentiveness. Usage example: You have a value in seconds, e.g. 285, and want to know how many minutes and seconds that are, so you divide by 60 and get 4.75. Omitting the 0.75 you're left with 4. For the remaining seconds, you'd calculate 285 % 60 = 45, which
is the same as 60 * 0.75. Then you'd know that 285 seconds equals 4 minutes plus 45 seconds. Real numbers and negative values are supported.AND, OR, XOR, NAND, NOR, NXOR: These are logic operands which operate bitwise; the leading 'N' indicates bitwise negation after the operation. Example: An entity's spawnflags are stored in an integer which consists of 32 bits. Say you want to set the 7th checkbox of an entity's spawnflags, you need to make sure the 7th bit is set to 1. You hence need the integer number where only the 7th bit is set, which is 2 ^ (7 - 1) = 2 ^ 6 = 64. However, you cannot simply add this
to the existing spawnflags, because if the 7th bit was already set to 1, you'd cause it to be set to 0 and generate a carry which is sent to the 8th bit; the magic of positional notation systems - just as 500 + 500 equals 1000 in decimal,
100 + 100 equals 1000 in binary. You'd need to perform a bitwise OR. If you'd want only the 7th checkbox to be checked, you'd use replace-operation as usual. XOR means "Exclusive OR", as in "Either that or the other, but not both". AND means that both bits need to be 1 for the resulting bit to remain 1. You can imagine the logic operators perform
32 simultaneous operations on the combined 64 bits of two integers.Append (String concatenation): Appends your source value to the destination keyvalue. The later must be a string; otherwise this cannot work."Trigonometric funcs. I/O", m_trigonometricBehaviour :
When using trigonometric or arc-functions as per the "Operation"-keyvalue, this is used to determine what your input/desired output measure is. You'll usually want to stick to degrees.}}
{{Entity_keyvalue|Append spaces (for strings)|m_iAppendSpaces|When the destination keyvalue is a string, this specifies how many spaces to append after the operations. You'll usually want
to use this with either the "Replace"- or "Append"-operation. This was implemented because Valve Hammer Editor omits any trailing spaces in keyvalues (but not leading ones).}}
{{Entity_keyvalue|Trigger after operation|message|Set entity/entities to be triggered after the trigger_changevalue has set the new keyvalue, by targetname as usual.
This is very useful when you need a chain of operations to happen in a specific order and without any delay in between.}}

== Flags ==

{{Entity_flag|1|Don't use X|When using vectors/arrays, this will ignore the first array. E.g., when setting render-color, specifying this flag would ignore the 'Red'-value.}}
{{Entity_flag|2|Don't use Y|When using vectors/arrays, this will ignore the second array. E.g., when setting angles, specifying this flag would ignore the 'Yaw'-value.}}
{{Entity_flag|4|Don't use Z|When using vectors/arrays, this will ignore the third array. E.g., when setting velocity, specifying this flag would ignore the vertical velocity.}}
{{Entity_flag|32|Invert target value|The destination keyvalue will be multiplied with minus one before proceeding.}}
{{Entity_flag|64|Invert source value|The source-value will be multiplied with minus one before proceeding; this change is only temporary and this keyvalue is rather useless, as you can always prepend a minus-sign to the static source-value.}}

== Notes ==

Trigger_changevalue supports the use of "!activator" and "!caller" in the "Destination Entity"-field.Trying to write a vector to a float or integer will cause the vector's length to be written. This is in respect to any ignored dimensions as per spawnflags.

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]