Text - Revision history

Asie at 13:58, 4 January 2026

2026-01-04T13:58:10Z

← Older revision		Revision as of 13:58, 4 January 2026
Line 29:		Line 29:
	Side effects from this roundabout encoding are apparent in a couple of places:		Side effects from this roundabout encoding are apparent in a couple of places:

	*Overwriting text (using [[Put\|#put]] or [[Become\|#become]]) will sometimes result in [[~~STK~~]]~~-colored elements~~. This is because those commands always interpret the color byte as a color: if you #put a gem onto a blue text "Z" (ASCII code 0x5A), you will get a green-on-dark-purple gem (color code 0x5A).		*Overwriting text (using [[Put\|#put]] or [[Become\|#become]]) will sometimes result in elements with [[Color\|non-standard colors]]. This is because those commands always interpret the color byte as a color: if you #put a gem onto a blue text "Z" (ASCII code 0x5A), you will get a green-on-dark-purple gem (color code 0x5A).
	*Unlike most elements, it is impossible to get arbitrary text colors from [[Toolkit\|toolkits]] or [[External editor\|external editors]]. This is not a matter of ZZT's internal editor being restrictive, but rather a limit imposed by the file format and the in-memory representation.		*Unlike most elements, it is impossible to get arbitrary text colors from [[Toolkit\|toolkits]] or [[External editor\|external editors]]. This is not a matter of ZZT's internal editor being restrictive, but rather a limit imposed by the file format and the in-memory representation.

Asie at 09:13, 24 December 2025

2025-12-24T09:13:58Z

← Older revision		Revision as of 09:13, 24 December 2025
Line 25:		Line 25:

	==Usage of terrain color byte==		==Usage of terrain color byte==
	Text is stored differently than any other element. Internally, ZZT repurposes the element's color byte to store character data instead: this allows the full range of characters to be encoded without having to allocate extra space (in the form of [[stats]]) for each tile. Since the color byte is occupied with other data, the actual color info is encoded by having different element IDs for each color. The result is that text is technically not just one element, but several.		Text is stored differently than any other element. Internally, ZZT repurposes the element's color byte to store character data instead: this allows the full range of characters to be encoded without having to allocate extra space (in the form of [[Stat\|stats]]) for each tile. Since the color byte is occupied with other data, the actual color info is encoded by having different element IDs for each color. The result is that text is technically not just one element, but several.

	Side effects from this roundabout encoding are apparent in a couple of places:		Side effects from this roundabout encoding are apparent in a couple of places:

The Green Herring: byte

2021-02-13T19:20:34Z

byte

← Older revision		Revision as of 19:20, 13 February 2021
Line 5:		Line 5:
	\|zzt-oop name=N/A		\|zzt-oop name=N/A
	\|id=Multiple, used to encode background color:		\|id=Multiple, used to encode background color:
	* ~~0x2F~~: Blue		* {{Byte\|47}}: Blue
	* ~~0x30~~: Green		* {{Byte\|48}}: Green
	* ~~0x31~~: Cyan		* {{Byte\|49}}: Cyan
	* ~~0x32~~: Red		* {{Byte\|50}}: Red
	* ~~0x33~~: Purple		* {{Byte\|51}}: Purple
	* ~~0x34~~: Brown		* {{Byte\|52}}: Brown
	* ~~0x35~~: Black		* {{Byte\|53}}: Black
	\|color=White foreground; element ID determines background		\|color=White foreground; element ID determines background
	\|char=Any (determined by tile's color byte)		\|char=Any (determined by tile's color byte)
Line 39:		Line 39:
	Some known unassigned IDs and their text colors:		Some known unassigned IDs and their text colors:

	*~~0x36~~: {{ColorSwatch\|blinking\|fg=white\|bg=black}}		*{{Byte\|54}}: {{ColorSwatch\|blinking\|fg=white\|bg=black}}
	*~~0x37~~: {{ColorSwatch\|blinking\|fg=white\|bg=dark blue}}		*{{Byte\|55}}: {{ColorSwatch\|blinking\|fg=white\|bg=dark blue}}
	*~~0x38~~: {{ColorSwatch\|blinking\|fg=white\|bg=dark green}}		*{{Byte\|56}}: {{ColorSwatch\|blinking\|fg=white\|bg=dark green}}
	*~~0x39~~: {{ColorSwatch\|blinking\|fg=white\|bg=dark cyan}}		*{{Byte\|57}}: {{ColorSwatch\|blinking\|fg=white\|bg=dark cyan}}
	*~~0x3A~~: {{ColorSwatch\|blinking\|fg=white\|bg=dark red}}		*{{Byte\|58}}: {{ColorSwatch\|blinking\|fg=white\|bg=dark red}}
	*~~0x3B~~: {{ColorSwatch\|blinking\|fg=white\|bg=dark purple}}		*{{Byte\|59}}: {{ColorSwatch\|blinking\|fg=white\|bg=dark purple}}
	*~~0x3C~~: {{ColorSwatch\|blinking\|fg=white\|bg=dark brown}}		*{{Byte\|60}}: {{ColorSwatch\|blinking\|fg=white\|bg=dark brown}}
	*~~0x3D~~: {{ColorSwatch\|blinking\|fg=white\|bg=light gray}}		*{{Byte\|61}}: {{ColorSwatch\|blinking\|fg=white\|bg=light gray}}
	*~~0x45~~: {{ColorSwatch\|fg=white\|bg=light gray}}		*{{Byte\|69}}: {{ColorSwatch\|fg=white\|bg=light gray}}

	It is impossible to choose the text foreground color because ZZT hard-codes it to be white. This means there are only 16 possible color combinations: the 7 text colors built into ZZT, and the 9 produced by the unassigned IDs above.		It is impossible to choose the text foreground color because ZZT hard-codes it to be white. This means there are only 16 possible color combinations: the 7 text colors built into ZZT, and the 9 produced by the unassigned IDs above.

Quantum: Add navbox

2021-01-18T06:12:53Z

Add navbox

← Older revision		Revision as of 06:12, 18 January 2021
Line 50:		Line 50:

	It is impossible to choose the text foreground color because ZZT hard-codes it to be white. This means there are only 16 possible color combinations: the 7 text colors built into ZZT, and the 9 produced by the unassigned IDs above.		It is impossible to choose the text foreground color because ZZT hard-codes it to be white. This means there are only 16 possible color combinations: the 7 text colors built into ZZT, and the 9 produced by the unassigned IDs above.

			{{ElementsNavbox}}
	[[Category:Elements]]		[[Category:Elements]]

Quantum: Fix sentence fragment

2021-01-17T19:14:57Z

Fix sentence fragment

← Older revision		Revision as of 19:14, 17 January 2021
Line 20:		Line 20:
	'''Text''' is a terrain type that can have any of the 256 characters. Its intended use is for putting text labels on a board's terrain.		'''Text''' is a terrain type that can have any of the 256 characters. Its intended use is for putting text labels on a board's terrain.

	Text is the only element that can display any character without the overhead of using a [[stat]], which makes them useful for ZZT art. However, artistic usage is somewhat hampered by the fact that text can only use a fixed set of color combinations: if you want to write a sentence on the screen in a custom color (e.g., black on light gray), the only way to do it is to		Text is the only element that can display any character without the overhead of using a [[stat]], which makes them useful for ZZT art. However, artistic usage is somewhat hampered by the fact that text can only use a fixed set of color combinations: if you want to write a sentence on the screen in a custom color (e.g., black on light gray), the only way to do it is to use [[object\|objects]].

	Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type.		Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type.

Quantum: /* Unassigned element IDs */ Use color swatches

2021-01-17T07:24:07Z

Unassigned element IDs: Use color swatches

← Older revision		Revision as of 07:24, 17 January 2021
Line 39:		Line 39:
	Some known unassigned IDs and their text colors:		Some known unassigned IDs and their text colors:

	*0x36: ~~Blinking~~ white on black		*0x36: {{ColorSwatch\|blinking\|fg=white\|bg=black}}
	*0x37: ~~Blinking~~ white on blue		*0x37: {{ColorSwatch\|blinking\|fg=white\|bg=dark blue}}
	*0x38: ~~Blinking~~ white on green		*0x38: {{ColorSwatch\|blinking\|fg=white\|bg=dark green}}
	*0x39: ~~Blinking~~ white on cyan		*0x39: {{ColorSwatch\|blinking\|fg=white\|bg=dark cyan}}
	*0x3A: ~~Blinking~~ white on red		*0x3A: {{ColorSwatch\|blinking\|fg=white\|bg=dark red}}
	*0x3B: ~~Blinking~~ white on purple		*0x3B: {{ColorSwatch\|blinking\|fg=white\|bg=dark purple}}
	*0x3C: ~~Blinking~~ white on brown		*0x3C: {{ColorSwatch\|blinking\|fg=white\|bg=dark brown}}
	*0x3D: ~~Blinking~~ white on light gray		*0x3D: {{ColorSwatch\|blinking\|fg=white\|bg=light gray}}
	*0x45: ~~White on~~ light gray		*0x45: {{ColorSwatch\|fg=white\|bg=light gray}}

	It is impossible to choose the text foreground color because ZZT hard-codes it to be white. This means there are only 16 possible color combinations: the 7 text colors built into ZZT, and the 9 produced by the unassigned IDs above.		It is impossible to choose the text foreground color because ZZT hard-codes it to be white. This means there are only 16 possible color combinations: the 7 text colors built into ZZT, and the 9 produced by the unassigned IDs above.
	[[Category:Elements]]		[[Category:Elements]]

Quantum: Remove extra space

2020-06-10T06:55:56Z

Remove extra space

← Older revision		Revision as of 06:55, 10 June 2020
Line 18:		Line 18:
	\|uses zzt-oop color=N/A		\|uses zzt-oop color=N/A
	}}		}}

	'''Text''' is a terrain type that can have any of the 256 characters. Its intended use is for putting text labels on a board's terrain.		'''Text''' is a terrain type that can have any of the 256 characters. Its intended use is for putting text labels on a board's terrain.

Quantum: Add element ID for white on light gray text, prefix hex values in infobox

2020-06-01T07:40:39Z

Add element ID for white on light gray text, prefix hex values in infobox

← Older revision		Revision as of 07:40, 1 June 2020
Line 5:		Line 5:
	\|zzt-oop name=N/A		\|zzt-oop name=N/A
	\|id=Multiple, used to encode background color:		\|id=Multiple, used to encode background color:
	* 2F: Blue		* 0x2F: Blue
	* 30: Green		* 0x30: Green
	* 31: Cyan		* 0x31: Cyan
	* 32: Red		* 0x32: Red
	* 33: Purple		* 0x33: Purple
	* 34: Brown		* 0x34: Brown
	* 35: Black		* 0x35: Black
	\|color=White foreground; element ID determines background		\|color=White foreground; element ID determines background
	\|char=Any (determined by tile's color byte)		\|char=Any (determined by tile's color byte)
Line 25:		Line 25:
	Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type.		Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type.

	== Usage of terrain color byte ==		==Usage of terrain color byte==
	Text is stored differently than any other element. Internally, ZZT repurposes the element's color byte to store character data instead: this allows the full range of characters to be encoded without having to allocate extra space (in the form of [[stats]]) for each tile. Since the color byte is occupied with other data, the actual color info is encoded by having different element IDs for each color. The result is that text is technically not just one element, but several.		Text is stored differently than any other element. Internally, ZZT repurposes the element's color byte to store character data instead: this allows the full range of characters to be encoded without having to allocate extra space (in the form of [[stats]]) for each tile. Since the color byte is occupied with other data, the actual color info is encoded by having different element IDs for each color. The result is that text is technically not just one element, but several.

Line 31:		Line 31:

	*Overwriting text (using [[Put\|#put]] or [[Become\|#become]]) will sometimes result in [[STK]]-colored elements. This is because those commands always interpret the color byte as a color: if you #put a gem onto a blue text "Z" (ASCII code 0x5A), you will get a green-on-dark-purple gem (color code 0x5A).		*Overwriting text (using [[Put\|#put]] or [[Become\|#become]]) will sometimes result in [[STK]]-colored elements. This is because those commands always interpret the color byte as a color: if you #put a gem onto a blue text "Z" (ASCII code 0x5A), you will get a green-on-dark-purple gem (color code 0x5A).
	*Unlike most elements, it is impossible to get arbitrary text colors from [[Toolkit\|toolkits]] or [[External editor\|external editors]]. This is not a matter of ZZT's internal editor being restrictive, but rather a limit imposed by the file format and the in-memory representation.		*Unlike most elements, it is impossible to get arbitrary text colors from [[Toolkit\|toolkits]] or [[External editor\|external editors]]. This is not a matter of ZZT's internal editor being restrictive, but rather a limit imposed by the file format and the in-memory representation.

	Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type. This may also be a side effect of text having a unique encoding.		Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type. This may also be a side effect of text having a unique encoding.

	== Unassigned element IDs ==		==Unassigned element IDs==
	ZZT only officially supports the seven text colors which have assigned element IDs. However, it is possible to get a few additional colors by using IDs beyond the assigned range, as ZZT interprets all element IDs greater than 0x2E as text. The problem is that all these IDs are buggy because they cause ZZT to read past the end of its table of elements. Touching tiles with these IDs will crash ZZT, and many unassigned IDs will crash ZZT immediately, on the first [[tick]].		ZZT only officially supports the seven text colors which have assigned element IDs. However, it is possible to get a few additional colors by using IDs beyond the assigned range, as ZZT interprets all element IDs greater than 0x2E as text. The problem is that all these IDs are buggy because they cause ZZT to read past the end of its table of elements. Touching tiles with these IDs will crash ZZT, and many unassigned IDs will crash ZZT immediately, on the first [[tick]].

	Some known unassigned IDs and their text colors:		Some known unassigned IDs and their text colors:

	* 0x36: Blinking white on black		*0x36: Blinking white on black
	* 0x37: Blinking white on blue		*0x37: Blinking white on blue
	* 0x38: Blinking white on green		*0x38: Blinking white on green
	* 0x39: Blinking white on cyan		*0x39: Blinking white on cyan
	* 0x3A: Blinking white on red		*0x3A: Blinking white on red
	* 0x3B: Blinking white on purple		*0x3B: Blinking white on purple
	* 0x3C: Blinking white on brown		*0x3C: Blinking white on brown
	* 0x3D: Blinking white on light gray		*0x3D: Blinking white on light gray
			*0x45: White on light gray

			It is impossible to choose the text foreground color because ZZT hard-codes it to be white. This means there are only 16 possible color combinations: the 7 text colors built into ZZT, and the 9 produced by the unassigned IDs above.
	[[Category:Elements]]		[[Category:Elements]]

Quantum: Fleshed out the article quite a bit

2020-06-01T06:00:33Z

Fleshed out the article quite a bit

← Older revision		Revision as of 06:00, 1 June 2020
Line 21:		Line 21:
	'''Text''' is a terrain type that can have any of the 256 characters. Its intended use is for putting text labels on a board's terrain.		'''Text''' is a terrain type that can have any of the 256 characters. Its intended use is for putting text labels on a board's terrain.

	Text is a ~~unique element~~ in ~~several ways:~~		Text is the only element that can display any character without the overhead of using a [[stat]], which makes them useful for ZZT art. However, artistic usage is somewhat hampered by the fact that text can only use a fixed set of color combinations: if you want to write a sentence on the screen in a custom color (e.g., black on light gray), the only way to do it is to

	* Its display character is ~~determined~~ by color: Internally, ZZT ~~stores~~ character data ~~where color bytes would normally go, presumably~~ to ~~reduce~~ the ~~number~~ of stats ~~that a long run of text would otherwise require~~.		Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type.
	* It has more than one ID: Because the color byte is occupied, ~~ZZT encodes~~ the ~~text's background~~ color by having ~~multiple~~ different IDs.
	* ~~Its foreground~~ color ~~cannot be changed~~.		== Usage of terrain color byte ==
	* ~~It cannot be referenced~~ in ZZT-OOP: e.g., there is no way to change all text tiles to another element type.		Text is stored differently than any other element. Internally, ZZT repurposes the element's color byte to store character data instead: this allows the full range of characters to be encoded without having to allocate extra space (in the form of [[stats]]) for each tile. Since the color byte is occupied with other data, the actual color info is encoded by having different element IDs for each color. The result is that text is technically not just one element, but several.

			Side effects from this roundabout encoding are apparent in a couple of places:

			*Overwriting text (using [[Put\|#put]] or [[Become\|#become]]) will sometimes result in [[STK]]-colored elements. This is because those commands always interpret the color byte as a color: if you #put a gem onto a blue text "Z" (ASCII code 0x5A), you will get a green-on-dark-purple gem (color code 0x5A).
			*Unlike most elements, it is impossible to get arbitrary text colors from [[Toolkit\|toolkits]] or [[External editor\|external editors]]. This is not a matter of ZZT's internal editor being restrictive, but rather a limit imposed by the file format and the in-memory representation.

			Text is also the only element supported by the built-in editor that has no ZZT-OOP name: e.g., there is no way to change all text tiles to another element type. This may also be a side effect of text having a unique encoding.

			== Unassigned element IDs ==
			ZZT only officially supports the seven text colors which have assigned element IDs. However, it is possible to get a few additional colors by using IDs beyond the assigned range, as ZZT interprets all element IDs greater than 0x2E as text. The problem is that all these IDs are buggy because they cause ZZT to read past the end of its table of elements. Touching tiles with these IDs will crash ZZT, and many unassigned IDs will crash ZZT immediately, on the first [[tick]].

			Some known unassigned IDs and their text colors:

			* 0x36: Blinking white on black
			* 0x37: Blinking white on blue
			* 0x38: Blinking white on green
			* 0x39: Blinking white on cyan
			* 0x3A: Blinking white on red
			* 0x3B: Blinking white on purple
			* 0x3C: Blinking white on brown
			* 0x3D: Blinking white on light gray

	[[Category:Elements]]		[[Category:Elements]]

Quantum: Update infobox template params for picture/caption

2020-06-01T03:00:31Z

Update infobox template params for picture/caption

← Older revision		Revision as of 03:00, 1 June 2020
Line 1:		Line 1:
	{{Element		{{Element
	\|name=Text		\|name=Text
	\|picture=[[File:text-example.png~~\|center~~]] Text can display any character, but color choices are limited.		\|picture=[[File:text-example.png]]
			\|caption=Text can display any character, but color choices are limited
	\|zzt-oop name=N/A		\|zzt-oop name=N/A
	\|id=Multiple, used to encode background color:		\|id=Multiple, used to encode background color: