Set - Revision history

Asie at 12:54, 24 December 2025

2025-12-24T12:54:44Z

← Older revision		Revision as of 12:54, 24 December 2025
Line 29:		Line 29:
	* Care must be exercised when editing flags with an external editor. If a flag name is not in all uppercase (e.g. <code>pants</code> instead of <code>PANTS</code>), then it will not be able to be referenced by any ZZT-OOP command.		* Care must be exercised when editing flags with an external editor. If a flag name is not in all uppercase (e.g. <code>pants</code> instead of <code>PANTS</code>), then it will not be able to be referenced by any ZZT-OOP command.

	== ~~Myth~~ ==		== Myths ==
	* At least two influential programming documents, ''[https://museumofzzt.com/file/z/zzttool.zip?file=ZZTTRICK.DOC Interesting Tricks and Techniques for ZZT and Super ZZT Object Programming]'' (ZZTTRICK.DOC) and ''[https://museumofzzt.com/file/z/zztptt.zip ZZT Programming Tricks and Techniques]'' (ZZTPTT.ZZT), claim that a flag can be set more than once ("double flags"), as any #set command with a flag that is already set will create another copy of the flag, and thus any instance where a flag may be set twice should have a #clear command to clear it first. This is incorrect, because as stated above, [https://github.com/asiekierka/reconstruction-of-zzt/blob/253a97774e24ed486a13b0ffa88e5a686b485ca2/SRC/OOP.PAS#L303-L324 the flag-setting procedure] checks for the existence of the specified flag and will not set it if it already exists, making an initial clearing procedure unnecessary.		* At least two influential programming documents, ''[https://museumofzzt.com/file/z/zzttool.zip?file=ZZTTRICK.DOC Interesting Tricks and Techniques for ZZT and Super ZZT Object Programming]'' (ZZTTRICK.DOC) and ''[https://museumofzzt.com/file/z/zztptt.zip ZZT Programming Tricks and Techniques]'' (ZZTPTT.ZZT), claim that a flag can be set more than once ("double flags"), as any #set command with a flag that is already set will create another copy of the flag, and thus any instance where a flag may be set twice should have a #clear command to clear it first. This is incorrect, because as stated above, [https://github.com/asiekierka/reconstruction-of-zzt/blob/253a97774e24ed486a13b0ffa88e5a686b485ca2/SRC/OOP.PAS#L303-L324 the flag-setting procedure] checks for the existence of the specified flag and will not set it if it already exists, making an initial clearing procedure unnecessary.

	{{ZZT-OOP navbox}}		{{ZZT-OOP navbox}}

RT-55J: /* Quirks */

2023-10-14T17:04:05Z

Quirks

← Older revision		Revision as of 17:04, 14 October 2023
Line 27:		Line 27:
	* Due to how the interpreter works, flags set with ZZT-OOP are limited to letters (a-z), numbers (0-9), colons (:) and underscores (_). The first character is not allowed to be a number. Other symbols will cut the string off: for example, <code>#set brick-wall</code> will assign the flag "BRICK".		* Due to how the interpreter works, flags set with ZZT-OOP are limited to letters (a-z), numbers (0-9), colons (:) and underscores (_). The first character is not allowed to be a number. Other symbols will cut the string off: for example, <code>#set brick-wall</code> will assign the flag "BRICK".
	* ZZT will technically allow setting flags with the same names as built-ins ([[contact]], [[blocked]], etc.), but attempting to read them with <code>[[if\|#if]]</code> statements will always query the state of the built-in flag.		* ZZT will technically allow setting flags with the same names as built-ins ([[contact]], [[blocked]], etc.), but attempting to read them with <code>[[if\|#if]]</code> statements will always query the state of the built-in flag.
			* Care must be exercised when editing flags with an external editor. If a flag name is not in all uppercase (e.g. <code>pants</code> instead of <code>PANTS</code>), then it will not be able to be referenced by any ZZT-OOP command.

	== Myth ==		== Myth ==

Asie at 17:10, 29 September 2022

2022-09-29T17:10:10Z

← Older revision		Revision as of 17:10, 29 September 2022
Line 19:		Line 19:

	In [[Super ZZT]] the flag limit has been increased to 16. Additionally, a flag prefixed with the letter "Z" can serve as the name for the [[Stones of Power]] counter. (Note that Super ZZT expects the initial "Z" to be uppercase, so keep that in mind if you choose to use an external editor to have the name of the Stones counter be mixed-case.)		In [[Super ZZT]] the flag limit has been increased to 16. Additionally, a flag prefixed with the letter "Z" can serve as the name for the [[Stones of Power]] counter. (Note that Super ZZT expects the initial "Z" to be uppercase, so keep that in mind if you choose to use an external editor to have the name of the Stones counter be mixed-case.)

			== Syntax ==
			<code>#set <flag></code>
			<code>#clear <flag></code>

	== Quirks ==		== Quirks ==

The Green Herring: Busting a well-known myth

2021-12-19T04:27:43Z

Busting a well-known myth

← Older revision		Revision as of 04:27, 19 December 2021
Line 23:		Line 23:
	* Due to how the interpreter works, flags set with ZZT-OOP are limited to letters (a-z), numbers (0-9), colons (:) and underscores (_). The first character is not allowed to be a number. Other symbols will cut the string off: for example, <code>#set brick-wall</code> will assign the flag "BRICK".		* Due to how the interpreter works, flags set with ZZT-OOP are limited to letters (a-z), numbers (0-9), colons (:) and underscores (_). The first character is not allowed to be a number. Other symbols will cut the string off: for example, <code>#set brick-wall</code> will assign the flag "BRICK".
	* ZZT will technically allow setting flags with the same names as built-ins ([[contact]], [[blocked]], etc.), but attempting to read them with <code>[[if\|#if]]</code> statements will always query the state of the built-in flag.		* ZZT will technically allow setting flags with the same names as built-ins ([[contact]], [[blocked]], etc.), but attempting to read them with <code>[[if\|#if]]</code> statements will always query the state of the built-in flag.

			== Myth ==
			* At least two influential programming documents, ''[https://museumofzzt.com/file/z/zzttool.zip?file=ZZTTRICK.DOC Interesting Tricks and Techniques for ZZT and Super ZZT Object Programming]'' (ZZTTRICK.DOC) and ''[https://museumofzzt.com/file/z/zztptt.zip ZZT Programming Tricks and Techniques]'' (ZZTPTT.ZZT), claim that a flag can be set more than once ("double flags"), as any #set command with a flag that is already set will create another copy of the flag, and thus any instance where a flag may be set twice should have a #clear command to clear it first. This is incorrect, because as stated above, [https://github.com/asiekierka/reconstruction-of-zzt/blob/253a97774e24ed486a13b0ffa88e5a686b485ca2/SRC/OOP.PAS#L303-L324 the flag-setting procedure] checks for the existence of the specified flag and will not set it if it already exists, making an initial clearing procedure unnecessary.

	{{ZZT-OOP navbox}}		{{ZZT-OOP navbox}}

Rbts: valid zzt flag: ::::::::::::::::::::

2021-02-13T00:46:11Z

valid zzt flag: ::::::::::::::::::::

← Older revision		Revision as of 00:46, 13 February 2021
Line 19:		Line 19:

	In [[Super ZZT]] the flag limit has been increased to 16. Additionally, a flag prefixed with the letter "Z" can serve as the name for the [[Stones of Power]] counter. (Note that Super ZZT expects the initial "Z" to be uppercase, so keep that in mind if you choose to use an external editor to have the name of the Stones counter be mixed-case.)		In [[Super ZZT]] the flag limit has been increased to 16. Additionally, a flag prefixed with the letter "Z" can serve as the name for the [[Stones of Power]] counter. (Note that Super ZZT expects the initial "Z" to be uppercase, so keep that in mind if you choose to use an external editor to have the name of the Stones counter be mixed-case.)

			== Quirks ==
			* Due to how the interpreter works, flags set with ZZT-OOP are limited to letters (a-z), numbers (0-9), colons (:) and underscores (_). The first character is not allowed to be a number. Other symbols will cut the string off: for example, <code>#set brick-wall</code> will assign the flag "BRICK".
			* ZZT will technically allow setting flags with the same names as built-ins ([[contact]], [[blocked]], etc.), but attempting to read them with <code>[[if\|#if]]</code> statements will always query the state of the built-in flag.

	{{ZZT-OOP navbox}}		{{ZZT-OOP navbox}}

RT-55J at 16:39, 12 February 2021

2021-02-12T16:39:20Z

← Older revision		Revision as of 16:39, 12 February 2021
Line 3:		Line 3:
	When using <code>#set flag</code>, ZZT checks to see if the flag has already been set. If it has been set already, then it does not set the flag again. If the flag has not been already set, then the flag is set in the first open flag slot. If no flag slot is open, then the last flag is overwritten.		When using <code>#set flag</code>, ZZT checks to see if the flag has already been set. If it has been set already, then it does not set the flag again. If the flag has not been already set, then the flag is set in the first open flag slot. If no flag slot is open, then the last flag is overwritten.

	The <code>#clear flag</code> command removes the flag from the flag list, replacing it with an empty string. Given how small the flag limit is, ~~but~~ sure to '''#clear''' flags when you are done with them. (If the flag list has been modified in an ~~eternal~~ editor to have multiple flags with the same name, then the last flag with the name will be removed.)		The <code>#clear flag</code> command removes the flag from the flag list, replacing it with an empty string. Given how small the flag limit is, be sure to '''#clear''' flags when you are done with them. (If the flag list has been modified in an external editor to have multiple flags with the same name, then the last flag with the name will be removed.)

	The presence of a flag can be detected using the [[if\|#if]] command.		The presence of a flag can be detected using the [[if\|#if]] command. For example:

	For example:

	<pre>#set flag		<pre>#set flag
Line 16:		Line 14:
	The object in this scenario will move east, but will not move west.		The object in this scenario will move east, but will not move west.

	Using the <code>?</code> cheat prompt, the player can type <code>+flag</code> or <code>-flag</code> to set and clear flags.		Using the <code>?</code> cheat prompt, the player can type <code>+flag</code> or <code>-flag</code> to set and clear flags manually. Several games have the player use this feature intentionally (eg to open an inventory menu) and not as a cheat.

	== ''Super ZZT'' ==		== ''Super ZZT'' ==

KKairos: added example. put in mid-explanation to avoid giving impression the example pertained to using cheat prompt.

2021-02-12T06:39:44Z

added example. put in mid-explanation to avoid giving impression the example pertained to using cheat prompt.

← Older revision		Revision as of 06:39, 12 February 2021
Line 6:		Line 6:

	The presence of a flag can be detected using the [[if\|#if]] command.		The presence of a flag can be detected using the [[if\|#if]] command.

			For example:

			<pre>#set flag
			#if flag /e
			#if not flag /w
			</pre>

			The object in this scenario will move east, but will not move west.

	Using the <code>?</code> cheat prompt, the player can type <code>+flag</code> or <code>-flag</code> to set and clear flags.		Using the <code>?</code> cheat prompt, the player can type <code>+flag</code> or <code>-flag</code> to set and clear flags.

RT-55J: still needs a code example and probably some cleanup

2021-02-12T06:31:33Z

still needs a code example and probably some cleanup

New page

The [[ZZT-OOP]] commands '''#set''' and '''#clear''' are used to set and clear flags from the world's flag list. Flags are strings limited to 20 characters in length, and only 10 flags can be set at a time. Internally, flags are converted into uppercase when set.

When using <code>#set flag</code>, ZZT checks to see if the flag has already been set. If it has been set already, then it does not set the flag again. If the flag has not been already set, then the flag is set in the first open flag slot. If no flag slot is open, then the last flag is overwritten.

The <code>#clear flag</code> command removes the flag from the flag list, replacing it with an empty string. Given how small the flag limit is, but sure to '''#clear''' flags when you are done with them. (If the flag list has been modified in an eternal editor to have multiple flags with the same name, then the last flag with the name will be removed.)

The presence of a flag can be detected using the [[if|#if]] command.

Using the <code>?</code> cheat prompt, the player can type <code>+flag</code> or <code>-flag</code> to set and clear flags.

== ''Super ZZT'' ==

In [[Super ZZT]] the flag limit has been increased to 16. Additionally, a flag prefixed with the letter "Z" can serve as the name for the [[Stones of Power]] counter. (Note that Super ZZT expects the initial "Z" to be uppercase, so keep that in mind if you choose to use an external editor to have the name of the Stones counter be mixed-case.)

{{ZZT-OOP navbox}}