Wiki of ZZT - User contributions [en]

Color

2021-04-30T02:03:29Z

Rbts: "dark brown" -> "brown". Added alternative way to get blinking white on brown via bears.

[[ZZT-OOP]] has seven named colors: blue, green, cyan, red, purple, yellow and white. These correspond to the seven bright colors in the default 16-color CGA palette. With the exception of [[door|doors]], named colors apply to an element's foreground color, and are paired with a black background. A handful of additional colors can be obtained through ZZT-OOP by using the [[change]] and [[put]] commands on built-in entities with hard-coded colors.

Below are examples of how to obtain [[gem|gems]] of various colors using ZZT-OOP.

== Dark colors on black ==

=== Brown on black ===

<code>
<nowiki>#</nowiki>put e [[torch]]

<nowiki>#</nowiki>change torch gem
</code>

''Alternatively:''

<code>
<nowiki>#</nowiki>put e [[bear]]

<nowiki>#</nowiki>change bear gem
</code>

=== Dark cyan on black ===

<code>
<nowiki>#</nowiki>put e [[ammo]]

<nowiki>#</nowiki>change ammo gem
</code>

=== Dark purple on black ===

<code>
<nowiki>#</nowiki>put e [[energizer]]

<nowiki>#</nowiki>change energizer gem
</code>

=== Gray on black ===

<code>
<nowiki>#</nowiki>put e [[shark]]

<nowiki>#</nowiki>change shark gem
</code>

== Black on dark colors ==

=== Black on dark green ===
<code>
<nowiki>#</nowiki>put e [[forest]]

<nowiki>#</nowiki>change forest gem
</code>

=== Black on gray ===
<code>
<nowiki>#</nowiki>put e [[empty]]

<nowiki>#</nowiki>put e gem
</code>

== White on dark colors ==

=== White on gray ===

<code>
<nowiki>#</nowiki>put e [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark blue ===

<code>
<nowiki>#</nowiki>put e blue [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark green ===

<code>
<nowiki>#</nowiki>put e green [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark red ===

<code>
<nowiki>#</nowiki>put e red [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark purple ===

<code>
<nowiki>#</nowiki>put e purple [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on brown ===

<code>
<nowiki>#</nowiki>put e yellow [[door]]

<nowiki>#</nowiki>change door gem
</code>

== Blinking white on black and dark colors ==

=== Blinking white on black ===

<code>
<nowiki>#</nowiki>put e forest

<nowiki>#</nowiki>change forest door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on dark cyan ===

<code>
<nowiki>#</nowiki>put e ammo

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>put e gem
</code>

''Note'': The ammo won't automatically be overwritten by the newly-created door. You can delete it with <code>#change ammo empty</code>, or put the object next to an obstacle such that the ammo gets crushed when the door is created.

=== Blinking white on dark purple ===

<code>
<nowiki>#</nowiki>put e energizer

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on brown ===

<code>
<nowiki>#</nowiki>put e torch

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

''Alternatively:''

<code>
<nowiki>#</nowiki>put e bear

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

''Note'': The bear needs to be crushed by an obstacle when the door is created.

=== Blinking white on gray ===

<code>
<nowiki>#</nowiki>put e shark

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

== References ==
[https://museumofzzt.com/file/m/Mwencv14.zip?file=%24MWENC_B.ZZT&board=7#19,10 Mystical Winds Encyclopedia v1.4: $MWENC_B.ZZT: 7. MW More In-Game Colors]

Talk:Stat order

2021-04-25T20:58:59Z

Rbts: strikethrough 'add a gif' bullet point

Todo:
* Stat bugs related to deleting entries in the list
* <s>Maybe a GIF of objects demonstrating gaps in movement, versus no gaps depending on the stat order</s>
* Origin of the term ''stat'' in this context (KevEdit?)

[[User:Rbts|Rbts]] ([[User talk:Rbts|talk]]) 20:21, 25 April 2021 (UTC)

Stat order

2021-04-25T20:57:16Z

Rbts: Add gif

The '''stat order''' or '''stat list''' refers to a ZZT [[board]]'s internal array of "active" entities. Stats provide additional state for map elements, and the list serves as a way for the engine to identify which elements require updates on a per-frame basis. Up to 150 stats can exist on a ZZT board, with the [[player]]'s stat occupying the first index.

The stat order is not exposed to the user in the [[built-in editor]]. Nonetheless, the order of stats can affect how quickly entities respond to certain events. Given two [[object|objects]] running at Cycle 1, the object first appearing in the list can send a message to the second object and have the latter react to it on the same frame. On the other hand, if the second object sends a message to the first, it will not react until the following frame.

[[File:Stat_order_move_gaps.gif|thumb|Top row: objects attempt to step forward, but are blocked by the objects in front of them which appear later in the stat order. Bottom row: all objects move on the same frame.|alt=|left]]

File:Stat order move gaps.gif

2021-04-25T20:53:23Z

Rbts: Animated .gif showing gaps in movement caused by the order of objects in the stat list. Top row: objects attempt to step forward, but are blocked by the objects in front of them. Bottom row: all objects move on the same frame. Uploaded by the author.

== Summary ==
Animated .gif showing gaps in movement caused by the order of objects in the stat list. Top row: objects attempt to step forward, but are blocked by the objects in front of them. Bottom row: all objects move on the same frame. Uploaded by the author.
== Licensing ==
{{CC-BY-SA-4.0}}

Talk:Stat order

2021-04-25T20:22:17Z

Rbts: Created page with "Todo: * Stat bugs related to deleting entries in the list * Maybe a GIF of objects demonstrating gaps in movement, versus no gaps depending on the stat order * Origin of the t..."

Todo:
* Stat bugs related to deleting entries in the list
* Maybe a GIF of objects demonstrating gaps in movement, versus no gaps depending on the stat order
* Origin of the term ''stat'' in this context (KevEdit?)

[[User:Rbts|Rbts]] ([[User talk:Rbts|talk]]) 20:21, 25 April 2021 (UTC)

Stat order

2021-04-25T20:15:49Z

Rbts: stub

Board

2021-04-25T20:06:23Z

Rbts: 151 stats -> 150

'''Boards''' are ZZT's playable map regions. Boards are 60x25 in size, and can contain up to 150 [[stat list|entities with stats]]. They are also used for the [[title screen]].

= Configuration =

* '''Title''': What the board is called in the editor's ''Switch Boards'' menu.
* '''Can Fire''' (0-255): How many [[bullet|bullets]] fired by the [[player]] are permitted at any one time.
* '''Board is dark''': If yes, requires the player to light a [[torch]] to see.
* '''Board ↑↓←→''': Allows linking this board to others by their [[edge|edges]]. These links are not automatically reciprocated in the [[built-in editor]].
* '''Re-enter when zapped''': When the player takes built-in damage, place them where they first entered the board.
* '''Time limit''' (0-32767): When active, the board will display a timer that counts down in seconds. When the time runs out, the player takes damage. This is typically used with ''Re-enter when zapped''.

= Storage and Persistence =

Boards maintain their state as the player travels from area to area, but there is only one board context active at a time. They are stored in a compressed form using a run-length encoding scheme, and decompressed into the active board context as needed. When the [[player]] travels to a new board, the old board's content is compressed and stored again.

Boards are limited to 20000 bytes in size, and exceeding this amount can lead to ZZT crashing.

= Perimeter =

The current active board has an additional hidden perimeter of [[edge|board edge tiles]]. These tiles are part of the system that allows the player to move across boards via edge links. They also serve as a barrier to prevent entities from stepping out of bounds. If a user [[cheat|zaps]] the edge of a board, they will create a hole in the perimeter which can allow entities to leave the board, typically resulting in memory corruption. Entities with tweaked [[step value|step values]] can also phase through the barrier.

= See also =

* [[ZZT file format]]

Color

2021-04-25T01:37:07Z

Rbts: high-intensity -> bright

[[ZZT-OOP]] has seven named colors: blue, green, cyan, red, purple, yellow and white. These correspond to the seven bright colors in the default 16-color CGA palette. With the exception of [[door|doors]], named colors apply to an element's foreground color, and are paired with a black background. A handful of additional colors can be obtained through ZZT-OOP by using the [[change]] and [[put]] commands on built-in entities with hard-coded colors.

Below are examples of how to obtain [[gem|gems]] of various colors using ZZT-OOP.

== Dark colors on black ==

=== Dark brown on black ===

<code>
<nowiki>#</nowiki>put e [[torch]]

<nowiki>#</nowiki>change torch gem
</code>

''Alternatively:''

<code>
<nowiki>#</nowiki>put e [[bear]]

<nowiki>#</nowiki>change bear gem
</code>

=== Dark cyan on black ===

<code>
<nowiki>#</nowiki>put e [[ammo]]

<nowiki>#</nowiki>change ammo gem
</code>

=== Dark purple on black ===

<code>
<nowiki>#</nowiki>put e [[energizer]]

<nowiki>#</nowiki>change energizer gem
</code>

=== Gray on black ===

<code>
<nowiki>#</nowiki>put e [[shark]]

<nowiki>#</nowiki>change shark gem
</code>

== Black on dark colors ==

=== Black on dark green ===
<code>
<nowiki>#</nowiki>put e [[forest]]

<nowiki>#</nowiki>change forest gem
</code>

=== Black on gray ===
<code>
<nowiki>#</nowiki>put e [[empty]]

<nowiki>#</nowiki>put e gem
</code>

== White on dark colors ==

=== White on gray ===

<code>
<nowiki>#</nowiki>put e [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark blue ===

<code>
<nowiki>#</nowiki>put e blue [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark green ===

<code>
<nowiki>#</nowiki>put e green [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark red ===

<code>
<nowiki>#</nowiki>put e red [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark purple ===

<code>
<nowiki>#</nowiki>put e purple [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on brown ===

<code>
<nowiki>#</nowiki>put e yellow [[door]]

<nowiki>#</nowiki>change door gem
</code>

== Blinking white on black and dark colors ==

=== Blinking white on black ===

<code>
<nowiki>#</nowiki>put e forest

<nowiki>#</nowiki>change forest door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on dark cyan ===

<code>
<nowiki>#</nowiki>put e ammo

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>put e gem
</code>

''Note'': The ammo won't automatically be overwritten by the newly-created door. You can delete it with <code>#change ammo empty</code>, or put the object next to an obstacle such that the ammo gets crushed when the door is created.

=== Blinking white on dark purple ===

<code>
<nowiki>#</nowiki>put e energizer

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on brown ===

<code>
<nowiki>#</nowiki>put e torch

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on gray ===

<code>
<nowiki>#</nowiki>put e shark

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

== References ==
[https://museumofzzt.com/file/m/Mwencv14.zip?file=%24MWENC_B.ZZT&board=7#19,10 Mystical Winds Encyclopedia v1.4: $MWENC_B.ZZT: 7. MW More In-Game Colors]

Color

2021-04-25T01:35:59Z

Rbts: Created page with "ZZT-OOP has seven named colors: blue, green, cyan, red, purple, yellow and white. These correspond to the seven high-intensity colors in the default 16-color CGA palette...."

[[ZZT-OOP]] has seven named colors: blue, green, cyan, red, purple, yellow and white. These correspond to the seven high-intensity colors in the default 16-color CGA palette. With the exception of [[door|doors]], named colors apply to an element's foreground color, and are paired with a black background. A handful of additional colors can be obtained through ZZT-OOP by using the [[change]] and [[put]] commands on built-in entities with hard-coded colors.

Below are examples of how to obtain [[gem|gems]] of various colors using ZZT-OOP.

== Dark colors on black ==

=== Dark brown on black ===

<code>
<nowiki>#</nowiki>put e [[torch]]

<nowiki>#</nowiki>change torch gem
</code>

''Alternatively:''

<code>
<nowiki>#</nowiki>put e [[bear]]

<nowiki>#</nowiki>change bear gem
</code>

=== Dark cyan on black ===

<code>
<nowiki>#</nowiki>put e [[ammo]]

<nowiki>#</nowiki>change ammo gem
</code>

=== Dark purple on black ===

<code>
<nowiki>#</nowiki>put e [[energizer]]

<nowiki>#</nowiki>change energizer gem
</code>

=== Gray on black ===

<code>
<nowiki>#</nowiki>put e [[shark]]

<nowiki>#</nowiki>change shark gem
</code>

== Black on dark colors ==

=== Black on dark green ===
<code>
<nowiki>#</nowiki>put e [[forest]]

<nowiki>#</nowiki>change forest gem
</code>

=== Black on gray ===
<code>
<nowiki>#</nowiki>put e [[empty]]

<nowiki>#</nowiki>put e gem
</code>

== White on dark colors ==

=== White on gray ===

<code>
<nowiki>#</nowiki>put e [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark blue ===

<code>
<nowiki>#</nowiki>put e blue [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark green ===

<code>
<nowiki>#</nowiki>put e green [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark red ===

<code>
<nowiki>#</nowiki>put e red [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on dark purple ===

<code>
<nowiki>#</nowiki>put e purple [[door]]

<nowiki>#</nowiki>change door gem
</code>

=== White on brown ===

<code>
<nowiki>#</nowiki>put e yellow [[door]]

<nowiki>#</nowiki>change door gem
</code>

== Blinking white on black and dark colors ==

=== Blinking white on black ===

<code>
<nowiki>#</nowiki>put e forest

<nowiki>#</nowiki>change forest door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on dark cyan ===

<code>
<nowiki>#</nowiki>put e ammo

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>put e gem
</code>

''Note'': The ammo won't automatically be overwritten by the newly-created door. You can delete it with <code>#change ammo empty</code>, or put the object next to an obstacle such that the ammo gets crushed when the door is created.

=== Blinking white on dark purple ===

<code>
<nowiki>#</nowiki>put e energizer

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on brown ===

<code>
<nowiki>#</nowiki>put e torch

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

=== Blinking white on gray ===

<code>
<nowiki>#</nowiki>put e shark

<nowiki>#</nowiki>put e door

<nowiki>#</nowiki>change door gem
</code>

== References ==
[https://museumofzzt.com/file/m/Mwencv14.zip?file=%24MWENC_B.ZZT&board=7#19,10 Mystical Winds Encyclopedia v1.4: $MWENC_B.ZZT: 7. MW More In-Game Colors]

Title screen

2021-04-23T20:33:37Z

Rbts: Created page with "The ZZT '''Title Screen''' is the game state which appears after the configuration screen. It displays the first board of the currently-loaded world, and provides..."

The ZZT '''Title Screen''' is the game state which appears after the [[configuration screen]]. It displays the first [[board]] of the currently-loaded [[world]], and provides options to select and play a world, restore from a [[saved game]], display info about ZZT, list [[high scores]], adjust the [[game speed]], and access the [[built-in editor]].

While in Title Screen mode, the [[player]] is replaced by a [[monitor]].

== Quirks ==
* The user can access the ZZT [[cheats|cheat]] menu on the Title Screen by pressing the pipe key ("|").
* If the first character in the ZZT [[ZZT.CFG|config file]] is "'''*'''", then the editor is disabled.
* When the user ends a game session and returns to the title screen, their [[counters]] and [[flags]] will persist. Starting a new game or loading another world will reset them.

Board

2021-04-22T22:21:59Z

Rbts: board edge perimeter

'''Boards''' are ZZT's playable map regions. Boards are 60x25 in size, and can contain up to 151 [[stat list|entities with stats]]. They are also used for the [[title screen]].

= Configuration =

* '''Title''': What the board is called in the editor's ''Switch Boards'' menu.
* '''Can Fire''' (0-255): How many [[bullet|bullets]] fired by the [[player]] are permitted at any one time.
* '''Board is dark''': If yes, requires the player to light a [[torch]] to see.
* '''Board ↑↓←→''': Allows linking this board to others by their [[edge|edges]]. These links are not automatically reciprocated in the [[built-in editor]].
* '''Re-enter when zapped''': When the player takes built-in damage, place them where they first entered the board.
* '''Time limit''' (0-32767): When active, the board will display a timer that counts down in seconds. When the time runs out, the player takes damage. This is typically used with ''Re-enter when zapped''.

= Storage and Persistence =

Boards maintain their state as the player travels from area to area, but there is only one board context active at a time. They are stored in a compressed form using a run-length encoding scheme, and decompressed into the active board context as needed. When the [[player]] travels to a new board, the old board's content is compressed and stored again.

Boards are limited to 20000 bytes in size, and exceeding this amount can lead to ZZT crashing.

= Perimeter =

The current active board has an additional hidden perimeter of [[edge|board edge tiles]]. These tiles are part of the system that allows the player to move across boards via edge links. They also serve as a barrier to prevent entities from stepping out of bounds. If a user [[cheat|zaps]] the edge of a board, they will create a hole in the perimeter which can allow entities to leave the board, typically resulting in memory corruption. Entities with tweaked [[step value|step values]] can also phase through the barrier.

= See also =

* [[ZZT file format]]

Board

2021-04-22T18:12:39Z

Rbts: Created page with "'''Boards''' are ZZT's playable map regions. Every board in ZZT is 60x25 in size, and can contain up to 151 entities with stats. They are also used for the tit..."

'''Boards''' are ZZT's playable map regions. Every board in ZZT is 60x25 in size, and can contain up to 151 [[stat list|entities with stats]]. They are also used for the [[title screen]].

= Configuration =

* '''Title''': What the board is called in the editor's ''Switch Boards'' menu.
* '''Can Fire''' (0-255): How many [[bullet|bullets]] fired by the [[player]] are permitted at any one time.
* '''Board is dark''': If yes, requires the player to light a [[torch]] to see.
* '''Board ↑↓←→''': Allows linking this board to others by their [[edge|edges]]. These links are not automatically reciprocated in the [[built-in editor]].
* '''Re-enter when zapped''': When the player takes built-in damage, place them where they first entered the board.
* '''Time limit''' (0-32767): When active, the board will display a timer that counts down in seconds. When the time runs out, the player takes damage. This is typically used with ''Re-enter when zapped''.

= Storage and Persistence =

Boards maintain their state as the player travels from area to area, but there is only one board context active at a time. They are stored in a compressed form using a run-length encoding scheme, and decompressed into the active board context as needed. When the [[player]] travels to a new board, the old board's content is compressed and stored again.

Boards are limited to 20000 bytes in size, and exceeding this amount can lead to ZZT crashing.

== See also ==

* [[ZZT file format]]

Monitor

2021-04-21T21:58:22Z

Rbts: Created page with "{{Element |name=Monitor |zzt-oop name=monitor |id={{Byte|3}} |color={{ColorSwatch|fg=gray|bg=black}} |char={{CharSwatch|32}} |stats=yes |cycle=1 |destructible=no |effect on mo..."

{{Element
|name=Monitor
|zzt-oop name=monitor
|id={{Byte|3}}
|color={{ColorSwatch|fg=gray|bg=black}}
|char={{CharSwatch|32}}
|stats=yes
|cycle=1
|destructible=no
|effect on movement=wall
|uses zzt-oop color=no
}}

'''Monitors''' stand in for the [[player]] on [[title screen|title screens]]. They watch for keyboard input.

== Quirks ==

There is no option to create new monitors in ZZT's [[built-in editor]], but they can be placed with [[external editor|external editors]]. Objects can create new monitors at run-time with [[ZZT-OOP]] (ie '''#put [dir] monitor'''). Placing a monitor in-game will not enable title screen features, though.

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

Pusher

2021-04-20T18:49:53Z

Rbts: Created page with "{{Element |name=Pusher |zzt-oop name=pusher |category=creature |id={{Byte|40}} |char={{CharSwatch|16}}, {{CharSwatch|17}}, {{CharSwatch|30}}, {{CharSwatch|31}} |stats=yes |cyc..."

{{Element
|name=Pusher
|zzt-oop name=pusher
|category=creature
|id={{Byte|40}}
|char={{CharSwatch|16}}, {{CharSwatch|17}}, {{CharSwatch|30}}, {{CharSwatch|31}}
|stats=yes
|cycle=4
|destructible=no
|effect on movement=wall
|uses zzt-oop color=yes
}}

'''Pushers''' are built-in ZZT creatures. They move in one direction, displacing any pushable entities in their path until they become blocked by a wall or other unmovable obstacle. They are typically used as a component of [[slider]] puzzles.

Pushers are not inherently dangerous, but once in motion, they cannot be reset short of restoring from a previous save.

== Quirks ==

* Statless Pushers and Pushers created with [[ZZT-OOP]] ('''#put <dir> [color] pusher''') are immobile and always display char 31 (down-arrow.)

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

Player

2021-04-19T16:11:02Z

Rbts: typo

{{Element
|name=Player
|zzt-oop name=player
|category=item
|id={{Byte|4}}
|color={{ColorSwatch|fg=white|bg=blue}}
|char={{CharSwatch|2}}
|stats=yes
|cycle=1
|destructible=yes
|effect on movement=
|uses zzt-oop color=no
}}

The '''Player''' is the user's in-game avatar.

= Capabilities =

Besides the [[monitor|title screen monitor]], the player is the only in-game ZZT element that responds directly to user input. It's also the only element that can collect items, unlock [[door|doors]], and issue [[touch]] events to [[object|objects]]. It can change the current active [[board]] by touching [[passage|passages]] and [[edge|board edges]].

= Appearances =

During a game session, ZZT assumes that only one player exists and that it occupies slot 0 in the [[stat list]]. Additional player entities (colloquially referred to as ''player clones'') can be placed in the editor or created at run-time with [[ZZT-OOP]].

The player is meant to effectively be indestructible, even on [[game over]], but can be erased from a board as a result of the [[conveyor|conveyor stat glitch]]. The player's tick function handles input, so if the player is destroyed in this manner, ZZT itself will become unresponsive.

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

Player

2021-04-19T16:09:51Z

Rbts: My bad, just realized 'destructible' in the infobox is referring to a field in elementDefs in the source

{{Element
|name=Player
|zzt-oop name=player
|category=item
|id={{Byte|4}}
|color={{ColorSwatch|fg=white|bg=blue}}
|char={{CharSwatch|2}}
|stats=yes
|cycle=1
|destructible=yes
|effect on movement=
|uses zzt-oop color=no
}}

The '''Player''' is the user's in-game avatar.

= Capabilities =

Besides the [[monitor|title screen monitor]], the player is the only in-game ZZT element that responds directly to user input. It's also also the only element that can collect items, unlock [[door|doors]], and issue [[touch]] events to [[object|objects]]. It can change the current active [[board]] by touching [[passage|passages]] and [[edge|board edges]].

= Appearances =

During a game session, ZZT assumes that only one player exists and that it occupies slot 0 in the [[stat list]]. Additional player entities (colloquially referred to as ''player clones'') can be placed in the editor or created at run-time with [[ZZT-OOP]].

The player is meant to effectively be indestructible, even on [[game over]], but can be erased from a board as a result of the [[conveyor|conveyor stat glitch]]. The player's tick function handles input, so if the player is destroyed in this manner, ZZT itself will become unresponsive.

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

Player

2021-04-19T15:52:51Z

Rbts:

{{Element
|name=Player
|zzt-oop name=player
|category=item
|id={{Byte|4}}
|color={{ColorSwatch|fg=white|bg=blue}}
|char={{CharSwatch|2}}
|stats=yes
|cycle=1
|destructible=
|effect on movement=
|uses zzt-oop color=no
}}

The '''Player''' is the user's in-game avatar.

= Capabilities =

The player is the only in-game ZZT element that responds directly to user input, and also the only element that can collect items, unlock [[door|doors]], and issue [[touch]] events to [[object|objects]]. It can change the current active [[board]] by touching [[passage|passages]] and [[edge|board edges]].

= Appearances =

During a game session, ZZT assumes that only one player exists and that it occupies slot 0 in the [[stat list]]. Additional player entities (colloquially referred to as ''player clones'') can be placed in the editor or created at run-time with [[ZZT-OOP]].

The player is intended to be indestructible, even on [[game over]], but can be erased from a board as a result of the [[conveyor|conveyor stat glitch]]. The player's tick function handles input, so if the player is destroyed in this manner, ZZT itself will become unresponsive.

On [[title screen|title screens]], a [[monitor]] exists in place of the player to handle keyboard input.

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

Slime

2021-04-18T22:54:51Z

Rbts:

{{Element
|name=Slime
|zzt-oop name=slime
|category=creature
|id={{Byte|37}}
|color=
|char={{CharSwatch|42}}
|stats=yes
|x-y step=
|cycle=3
|p1=Cloning counter
|p2=Cloning threshold
|score=
|destructible=no
|effect on movement=
|uses zzt-oop color=yes
}}

'''Slimes''' are creatures which clone themselves across empties and fake floors, leaving [[breakable|breakable tiles]] in their place. The player can destroy a single slime by touching it. They cannot be harmed by bullets or bomb blasts, though they may incidentally disappear without cloning if they happen to be blocked at the right moment.

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

Slime

2021-04-18T22:50:53Z

Rbts: Created page with "{{Element |name=Slime |zzt-oop name=slime |category=creature |id={{Byte|37}} |color= |char={{CharSwatch|42}} |stats=yes |x-y step= |cycle=3 |p1=Cloning counter |p2=Cloning thr..."

{{Element
|name=Slime
|zzt-oop name=slime
|category=creature
|id={{Byte|37}}
|color=
|char={{CharSwatch|42}}
|stats=yes
|x-y step=
|cycle=3
|p1=Cloning counter
|p2=Cloning threshold
|score=
|destructible=no
|effect on movement=
|uses zzt-oop color=yes
}}

'''Slimes''' are creatures which clone themselves across empties and fake floors, leaving breakable blocks in their place. The player can destroy a single slime by touching it. They cannot be harmed by bullets or bomb blasts, though they may incidentally disappear without cloning if they happen to be blocked at the right moment.

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

Object

2021-04-18T22:16:26Z

Rbts:

{{Element
|name=Object
|zzt-oop name=object
|category=creature
|id={{Byte|36}}
|color=
|char=
|stats=yes
|x-y step=Yes
|cycle=3
|p1=Character graphic
|p2=Message [[lock]]
|score=
|destructible=no
|effect on movement=
|uses zzt-oop color=yes
}}

'''Objects''' are ZZT's general-purpose, customizable entity. While objects do nothing on their own, they can be programmed with [[ZZT-OOP]] to perform simple tasks such as moving, shooting and displaying text. It's possible to build more complex mechanisms using [[if|conditional statements]], [[label|label manipulation]] and [[send|object-to-object communication]].

== Quirks ==

=== Dynamic Object Creation ===

Objects created with ZZT-OOP (like executing '''#put [dir] object''' in the direction of an empty space) have no ZZT-OOP program and default to a blank graphic (char 1). Objects can be cloned with their state and program intact via [[duplicator|duplicators]].

=== Changing an Object's Color ===

Objects cannot change their own color, and '''#become [color] object''' will delete the object's ZZT-OOP program and assign it char 1. All objects of a given color on the board can be changed at the same time using '''#change [old_color] object [new_color] object'''. One object may '''#put [dir] [color] object''' in the direction of an existing object and change its color that way.

=== Gameplay ===

* The [[player]] cannot shoot an object while standing directly next to it: there must be at least one space between them and the object. The reverse is ''not'' true for objects.

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

Object

2021-04-18T22:15:42Z

Rbts: Created page with "{{Element |name=Object |zzt-oop name=object |category=creature |id={{Byte|36}} |color= |char= |stats=yes |x-y step=Yes |cycle=3 |p1=Character graphic |p2=Message lock |sco..."

{{Element
|name=Object
|zzt-oop name=object
|category=creature
|id={{Byte|36}}
|color=
|char=
|stats=yes
|x-y step=Yes
|cycle=3
|p1=Character graphic
|p2=Message [[lock]]
|score=
|destructible=no
|effect on movement=
|uses zzt-oop color=yes
}}

'''Objects''' are ZZT's general-purpose, customizable entity. While objects do nothing on their own, they can be programmed with [[ZZT-OOP]] to perform simple tasks such as moving, shooting and displaying text. It's possible to build more complex mechanisms using [[if|conditional statements]], [[label|label jumps]] and [[send|object-to-object communication]].

== Quirks ==

=== Dynamic Object Creation ===

Objects created with ZZT-OOP (like executing '''#put [dir] object''' in the direction of an empty space) have no ZZT-OOP program and default to a blank graphic (char 1). Objects can be cloned with their state and program intact via [[duplicator|duplicators]].

=== Changing an Object's Color ===

Objects cannot change their own color, and '''#become [color] object''' will delete the object's ZZT-OOP program and assign it char 1. All objects of a given color on the board can be changed at the same time using '''#change [old_color] object [new_color] object'''. One object may '''#put [dir] [color] object''' in the direction of an existing object and change its color that way.

=== Gameplay ===

* The [[player]] cannot shoot an object while standing directly next to it: there must be at least one space between them and the object. The reverse is ''not'' true for objects.

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

Kangaroo effect

2021-04-18T15:36:16Z

Rbts: Created page with "The ''Kangaroo Effect'' is a visual technique for displaying art on dark boards outside the field of vision of the player entity. For gameplay reasons, torches,..."

The ''Kangaroo Effect'' is a visual technique for displaying art on dark boards outside the field of vision of the [[player]] entity. For gameplay reasons, [[torch|torches]], [[passage|passages]], and the player are unconditionally visible on dark boards. By placing large quantities of these entities with the same foreground and background color, one can depict inaccessible regions as solid bodies.

A precursor to the effect is found in [https://museumofzzt.com/file/d/catalog.zip?file=CATALOG.ZZT&board=5 some early ZZT worlds], where plain brown-on-black torches are used on dark boards to suggest a thick forested area.

Player

2021-04-18T15:34:53Z

Rbts: Created page with "{{Element |name=Player |zzt-oop name=player |category=item |id={{Byte|4}} |color={{ColorSwatch|fg=white|bg=blue}} |char={{CharSwatch|2}} |stats=yes |cycle=1 |destructible=no |..."

Torch

2021-02-13T13:08:50Z

Rbts:

{{Element
|zzt-oop name=torch
|id={{Byte|6}}
|char={{CharSwatch|157}}
|color={{ColorSwatch|fg=brown|bg=black}}
|category=item
|stats=no
|destructible=no
|effect on movement=solid, collectible by the player
|uses zzt-oop color=no
|visible in dark=yes
}}

The '''torch''' element is ZZT's built-in method for giving the player torches. Touching a torch will add 1 to your torch counter and display the message "Torch - used for lighting in the underground."

Pressing the "T" key in a dark room will light a torch for 200 ticks. Pressing "T" in a non-dark room will display the message "Don't need torch - room is not dark!" In either case, if you don't have any torches then pressing "T" will display the message "You don't have any torches!"

When a torch is active, the game will draw a circle around the player that is roughly 50 pixels in diameter. At its widest points, the lit portion of the room extends 4 tiles north and south of the player, and 7 tiles east and west of the player. (Interestingly, the shape of the torchlight is the exact same shape as a [[bomb]] explosion.)

Each extra [[player|player clone]] on a board will exhaust an extra torch tick every cycle.

Since torches are one of the few elements that are visible in the dark, they can be used to give dark rooms decorative contours and shape. This is colloquially referred to as "The Kangaroo Effect."

Torches are also useful as a means of programmatically obtaining brown, e.g., by [[change|#changing]] another item to a torch and back.

{{ElementsNavbox}}

Send

2021-02-13T01:45:00Z

Rbts:

{{DISPLAYTITLE:send}}

'''#send''' is a [[ZZT-OOP]] command that provides a means of directing one or multiple [[object|objects.]] When an object receives a message from '''#send''', it checks its program for a matching [[label]], and if found, continues program execution from that point. ZZT's manual compares it to the GOTO statement in BASIC.

Objects can send messages to themselves to control their own program flow, as well as send to other objects. An object can manage multiple instances of a label with [[zap|#zap and #restore]], allowing different reactions to the same received message string. If an object needs to perform a task without interruption, it can turn off all incoming messages with the [[lock|#lock]] command.

== Syntax ==
* Object sending a label to itself: <code>#send self:<label></code>
* Object sending a label to multiple objects (and possibly itself as well): <code>#send <all|others|[[Object Name|name]]>:<label></code>

'''#send''' is unique among ZZT-OOP commands in that the command part can be omitted as a shortcut: <code>#label</code> is functionally identical to <code>#send self:label</code>, so long as <code>:label</code> exists somewhere in the code and ''label'' isn't the name of a command like <code>[[die|#die]]</code>.

== Quirks ==
* A locked object will not receive external messages, but it can still '''#send''' messages to itself. This includes when sending to all objects with <code>#send all:label</code>.

{{ZZT-OOP navbox}}

Send

2021-02-13T01:43:46Z

Rbts: Created page with "{{DISPLAYTITLE:send}} '''#send''' is a ZZT-OOP command that provides a means of directing one or multiple objects. When an object receives a message from '''#s..."

{{DISPLAYTITLE:send}}

'''#send''' is a [[ZZT-OOP]] command that provides a means of directing one or multiple [[object|objects.]] When an object receives a message from '''#send''', it checks its program for a matching [[label]], and if found, continues program execution from that point. ZZT's manual compares it to the GOTO statement in BASIC.

Objects can send messages to themselves to control their own program flow, as well as send to other objects. An object can manage multiple instances of a label with [[zap|#zap and #restore]], allowing different reactions to the same received message string. If an object needs to perform a task without interruption, it can temporarily turn off all incoming messages with the [[lock|#lock]] command.

== Syntax ==
* Object sending a label to itself: <code>#send self:<label></code>
* Object sending a label to multiple objects (and possibly itself as well): <code>#send <all|others|[[Object Name|name]]>:<label></code>

'''#send''' is unique among ZZT-OOP commands in that the command part can be omitted as a shortcut: <code>#label</code> is functionally identical to <code>#send self:label</code>, so long as <code>:label</code> exists somewhere in the code and ''label'' isn't the name of a command like <code>[[die|#die]]</code>.

== Quirks ==
* A locked object will not receive external messages, but it can still '''#send''' messages to itself. This includes when sending to all objects with <code>#send all:label</code>.

{{ZZT-OOP navbox}}

Set

2021-02-13T00:46:11Z

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

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, 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. 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 manually. Several games have the player use this feature intentionally (eg to open an inventory menu) and not as a cheat.

== ''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.)

== 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}}

Go

2021-02-11T22:26:59Z

Rbts: Created page with "{{DISPLAYTITLE:go}} '''#go''' (Shortened: '''/''') is a ZZT-OOP movement command which makes an object move one step. If the destination is blocked by an..."

{{DISPLAYTITLE:go}}
'''#go''' (Shortened: '''[[Movement|/]]''') is a [[ZZT-OOP]] movement command which makes an [[object]] move one step. If the destination is blocked by an obstacle, the object will wait until the path is clear before stepping into the spot and continuing on with program execution.

== Syntax ==
Full form: <code>#go <direction></code>

Shortened form: <code>/<direction></code>

{{ZZT-OOP navbox}}

Try

2021-02-11T22:19:34Z

Rbts: Created page with "{{DISPLAYTITLE:try}} '''#try''' (Shortened: '''?''') is a ZZT-OOP movement command which attempts to move an object one step in a given direction. Unlike..."

{{DISPLAYTITLE:try}}
'''#try''' (Shortened: '''[[Movement|?]]''') is a [[ZZT-OOP]] movement command which attempts to move an [[object]] one step in a given direction. Unlike [[go|#go]], '''#try''' will not block program execution if the object is incapable of moving to its destination.

If '''#try''' is unsuccessful, an optional command can be executed, similar to [[give|#give]] and [[take|#take]]. This is not supported with the shortened variant.

== Syntax ==
Full form: <code>#try <direction> [<failure_command>]</code>

Shortened form: <code>?<direction></code>

{{ZZT-OOP navbox}}

Lock

2021-02-11T16:28:24Z

Rbts: Created page with "{{DISPLAYTITLE:lock}} '''#lock''' and '''#unlock''' are ZZT-OOP commands that control whether an object receives messages from external sources. While locked, an..."

{{DISPLAYTITLE:lock}}
'''#lock''' and '''#unlock''' are [[ZZT-OOP]] commands that control whether an [[object]] receives [[messages]] from external sources.

While locked, an object will not receive incoming messages from other objects, or built-in messages such as <code>[[touch|#touch]]</code>. A locked object can still <code>[[send|#send]]</code> messages to itself, as well as send outgoing messages to other objects. This allows objects to complete sequences of commands without interruption.

If a locked object reaches an <code>[[end|#end]]</code> command (or the end of its program) without unlocking, it will become unresponsive, as there is no way to unlock an object remotely.

== Quirks ==
* A locked object executing <code>[[send|#send all:<message>]]</code> will send <message> to itself as well.

{{ZZT-OOP navbox}}

Unlock

2021-02-11T15:54:41Z

Rbts: Redirected page to Lock

#REDIRECT [[lock]]

Restart

2021-02-11T00:00:25Z

Rbts: Created page with "{{DISPLAYTITLE:restart}} '''restart''' is a built-in ZZT-OOP message that resets an object's instruction counter, making it continue execution from the top of its program..."

{{DISPLAYTITLE:restart}}

'''restart''' is a built-in [[ZZT-OOP]] message that resets an object's instruction counter, making it continue execution from the top of its program.

== Syntax ==

Object restarting itself: <code>#restart</code>

Restarting any objects called <code>@bandit</code>: <code>#bandit:restart</code>

Restarting all objects on the board: <code>#all:restart</code>

Object restarting other objects on the board: <code>#others:restart</code>

{{ZZT-OOP navbox}}

Walk

2021-02-10T23:20:40Z

Rbts: Created page with "{{DISPLAYTITLE:walk}} '''walk''' is a ZZT-OOP command that makes an object move automatically, independent of conventional movement commands (<code>#go</code>,..."

{{DISPLAYTITLE:walk}}

'''walk''' is a [[ZZT-OOP]] command that makes an [[object]] move automatically, independent of conventional movement commands (<code>[[go|#go]]</code>, <code>[[try|#try]]</code>).

Once <code>#walk</code> is executed, the object will move in the specified direction on every cycle tick. If a walking object is blocked by an obstacle, it will send a [[thud]] message to itself, unless it's [[lock|locked]].

To stop walking, use <code>#walk [[idle]]</code> or <code>#walk [[idle|i]]</code>.

== Syntax ==

<code>#walk <direction></code>

== Notes ==
* Objects will not push other entities as a result of walking.
* <code>#walk</code> operates independently of other movement commands, so an object can appear to move diagonally by walking along one axis and using <code>#go</code> or <code>#try</code> on the other.
* [[flow]] refers to an object's current walking direction, and can be used in conjunction with [[Direction modifiers]] to steer it. For example, <code>#walk cw flow</code> will make an object turn clockwise.
* Internally, ZZT object walking is implemented with two delta variables. Modifying these variables with an enhanced editor beyond the ranges of -1 to +1 will cause the object to skip across terrain.

{{ZZT-OOP navbox}}

Direction modifiers

2021-02-10T23:06:04Z

Rbts: #move -> #go

In [[ZZT-OOP]], a direction modifier is a word that prefixes a direction to create a new direction. If you like, you may think of them (in math terms) as relations which take a given "input" direction and produce an "output." They are explained in detail below.

==cw and ccw==
'''cw''' and '''ccw''' are ZZT-OOP direction modifiers which modify the direction clockwise and counter-clockwise, respectively. For example, <code>cw n</code> evaluates to <code>e</code>, but <code>ccw n</code> evaluates to <code>w</code>.

==opp==
'''opp''' is a ZZT-OOP direction modifier which evaluates to the exact opposite of the given direction. For example, <code>opp n</code> evaluates to <code>s</code>.

==rndp==
'''rndp''' is a ZZT-OOP direction modifier which causes the object to choose a random direction perpendicular to the succeeding direction, rather than simply use the succeeding direction. For example, <code>#go rndp e</code> causes the object to attempt to move one of two directions perpendicular to east, that is, randomly north or south. For more information, see [[Random directions#rndp|rndp]].

==Combining Direction Modifiers==
Multiple direction modifiers can be combined in a single line. Lines written this way will cause the object to treat each modifier as "modifying" the rest of the written direction, so that it is "evaluated" in pairs from right-to-left. As a concrete example, the following combination <code>opp cw n</code> evaluates like this:

<pre>
opp cw n
= opp (cw n)
= opp e
= w
</pre>

And <code>opp ccw rndne</code> would evaluate this way:

<pre>
opp ccw rndne
= opp (cw (randomly n or e))
= opp (randomly e or s)
= randomly w or n
</pre>

{{ZZT-OOP navbox}}

Seek

2021-02-10T00:06:00Z

Rbts:

{{DISPLAYTITLE:seek}}

'''seek''' is a [[ZZT-OOP]] direction token which points towards the [[player]].

When an [[object]] and the player are aligned horizontally or vertically, '''seek''' will point directly to the player. When not aligned, it will randomly pick one of two directions (with a 50-50 chance) that generally lead to the player. For example, if an object is located to the northeast of the player, the command <code>#go seek</code> will make the object step south ''or'' west.

== Quirks ==
* '''seek''' is reversed when the player is [[Energizer|energized]]. One can work around this by checking the [[energized|energized flag]] and branching to alternate commands that use ''[[opp]] seek'' instead.

{{ZZT-OOP navbox}}

Seek

2021-02-10T00:04:13Z

Rbts:

{{DISPLAYTITLE:seek}}

'''seek''' is a [[ZZT-OOP]] direction token which points towards the [[player]].

When an [[object]] and the player are aligned horizontally or vertically, seek will point directly to the player. When not aligned, seek will randomly pick one of two directions (with a 50-50 chance) that generally lead to the player. For example, if an object is located to the northeast of the player, the command <code>#go seek</code> will make the object step south ''or'' west.

== Quirks ==
* '''seek''' is reversed when the player is [[Energizer|energized]]. One can work around this by checking the [[energized|energized flag]] and branching to alternate commands that use ''[[opp]] seek'' instead.

{{ZZT-OOP navbox}}

Seek

2021-02-10T00:03:34Z

Rbts: Created page with "{{DISPLAYTITLE:seek}} '''seek''' is a ZZT-OOP direction token which points towards the player. When the object and player are aligned horizontally or vertically,..."

{{DISPLAYTITLE:seek}}

'''seek''' is a [[ZZT-OOP]] direction token which points towards the [[player]].

When the [[object]] and player are aligned horizontally or vertically, seek will point directly to the player. When not aligned, seek will randomly pick one of two directions (with a 50-50 chance) that generally lead to the player. For example, if an object is located to the northeast of the player, the command <code>#go seek</code> will make the object step south ''or'' west.

== Quirks ==
* '''seek''' is reversed when the player is [[Energizer|energized]]. One can work around this by checking the [[energized|energized flag]] and branching to alternate commands that use ''[[opp]] seek'' instead.

{{ZZT-OOP navbox}}

Idle

2021-02-09T18:48:36Z

Rbts: Created page with "{{DISPLAYTITLE:idle}} '''idle''' ''(shortened: '''i''')'' is a ZZT-OOP direction token which does not point in any direction. It can be used with go and try to make t..."

{{DISPLAYTITLE:idle}}

'''idle''' ''(shortened: '''i''')'' is a ZZT-OOP direction token which does not point in any direction. It can be used with [[go]] and [[try]] to make the object delay execution for one cycle, or with [[walk]] to stop the object from automatically walking.

{{ZZT-OOP navbox}}

Comment

2021-02-09T15:42:54Z

Rbts: Not sure how to word this

Any [[ZZT-OOP]] line beginning with an apostrophe ('''<nowiki>'</nowiki>''') is treated as a '''comment''' and ignored by the interpreter. Comments provide a way for the programmer to document their code, or to quickly disable lines of code without deleting the text.

Comments are used in the implementation of [[zap|zapping and restoring labels]].

The apostrophe must be the first character on the line. Any leading whitespace will cause the line to be treated as display text. Text placed after commands may be ignored in a manner similar to comments due to how the interpreter parses code lines.

{{ZZT-OOP navbox}}

Comment

2021-02-09T15:38:37Z

Rbts: leading space note

Any [[ZZT-OOP]] line beginning with an apostrophe ('''<nowiki>'</nowiki>''') is treated as a '''comment''' and ignored by the interpreter. Comments provide a way for the programmer to document their code, or to quickly disable lines of code without deleting the text.

Comments are used in the implementation of [[zap|zapping and restoring labels]].

== Notes ==
* The apostrophe must be the first character on the line. Any leading whitespace will cause the line to be treated as display text.

{{ZZT-OOP navbox}}

Comment

2021-02-09T15:36:23Z

Rbts: Created page with "Any ZZT-OOP line beginning with an apostrophe ('''<nowiki>'</nowiki>''') is treated as a '''comment''' and ignored by the interpreter. Comments provide a way for the progr..."

Energizer

2021-02-09T12:53:53Z

Rbts: energized player vulnerable to bomb blasts

{{Element
|zzt-oop name=energizer
|id={{Byte|14}}
|char={{CharSwatch|127}}
|color={{ColorSwatch|fg=dark purple|bg=black}}
|category=item
|stats=no
|destructible=no
|effect on movement=solid, collectable by the player
|uses zzt-oop color=no
}}
The '''energizer''' element is a single-use invincibility item that operates similarly to the ''power pellet'' from ''Pac Man'' or the ''starman'' from ''Super Mario Bros.'' When collected, the player is "energized" for 75 ticks. Collecting another energizer while still energized will reset the energizer counter to 75 ticks.

While energized, the player is invincible against all built-in damage sources except for [[bomb|bomb blasts]], and is able to safely destroy all enemies on contact. However, objects are still able to use [[take|#take health]] or [[endgame|#endgame]] to hurt the player. Also while energized, the [[seek]] direction is reversed, so that objects that go <code>/seek</code> or built-in enemies that seek towards the player will go away from the player instead.

[[ZZT-OOP]] provides two ways to detect if a player is energized. When the player picks up an energizer the message [[energize]] is sent to all objects on the board. Also, the internal flag [[energized]] is set for the duration of the player being energized.

Energizers are useful as a means of programmatically obtaining dark purple, e.g., by [[change|#changing]] another item to an energizer and back.

{{ElementsNavbox}}

If

2021-02-08T22:25:41Z

Rbts: Created page with "{{DISPLAYTITLE:if}} '''if''' is a built-in ZZT-OOP command which evaluates the state of a flag, conditionally executing another command if it is true. '''if''' can te..."

{{DISPLAYTITLE:if}}
'''if''' is a built-in [[ZZT-OOP]] command which evaluates the state of a [[flag]], conditionally executing another command if it is true.

'''if''' can test the status of internal flags ([[alligned]], [[blocked]], etc.), and also a set of user-assigned flags, of which ten can be active at a time.

== Syntax ==
<code>#if <flag> [then] <command></code>

Notes:
* "then" is decorative and can be omitted.
* The final command does not require a <nowiki>'</nowiki>#<nowiki>'</nowiki> symbol.

== Chaining if Commands ==

Multiple '''if''' commands can be chained together on one line to test more than one flag at once. The rightmost command will execute only when all preceding '''if'''s evaluate to true, similar to a logical AND operator in other languages.

<code>#if <flag1> if <flag2> <command></code>

{{ZZT-OOP navbox}}

Cycle

2021-02-08T20:26:55Z

Rbts: Minor typo fix

'''Cycle''' can refer to an element's '''cycle parameter''' (which dictates how often a statted element updates), or the [[ZZT-OOP]] command '''#cycle n''' (which sets an object's cycle parameter to n). An element with a cycle parameter of ''n'' updates once every ''n'' ticks. The exception is for elements with a cycle of zero, which never update themselves.

For objects placed with the default editor, the default cycle value is 3. Thus, for games made with the default editor, it is common to see <code>#cycle 1</code> as the first line of ZZT-OOP in order initialize the object. External editors can modify the cycle parameter, usually rendering that code unnecessary.

Note that elements with the same cycle number do not necessarily execute on the same tick. The element's index on the stat list is also a factor. The exact formula used to determine if a statted element executes on a given tick is <code>(CurrentTick mod Cycle) = (CurrentStatTicked mod Cycle)</code>. Note that <code>CurrentTick</code> is reset to a value of 1 whenever it exceeds 420 (not a joke), so elements with a cycle value greater than 420 will never update.

The command '''#cycle''' will silently ignore non-positive values - that is, values smaller than 1.

== Bugs and Quirks ==

* Due to a division-by-zero error, cycle 0 [[Transporter|transporters]] will crash the game when rendered.

{{ZZT-OOP navbox}}

Touch

2021-02-08T18:24:23Z

Rbts:

{{DISPLAYTITLE:touch}}
''':touch''' is a built-in [[ZZT-OOP]] label that triggers when the [[player]] touches (bumps into) an [[object]].

== Notes ==
* Object-to-object collisions do not emit '':touch'' events.
* [[lock|Locked]] objects do not emit '':touch'' events, and therefore won't react to the player touching them.

{{ZZT-OOP navbox}}

Touch

2021-02-08T18:22:42Z

Rbts: Created page with "{{DISPLAYTITLE:touch}} ''':touch''' is a built-in ZZT-OOP label that triggers when the player touches (bumps into) an object. == Notes == * Object-to-object colli..."

{{DISPLAYTITLE:touch}}
''':touch''' is a built-in [[ZZT-OOP]] label that triggers when the [[player]] touches (bumps into) an [[object]].

== Notes ==
* Object-to-object collisions do not emit '':touch'' events.
* Locked objects do not emit '':touch'' events, and therefore won't react to the player touching them.

{{ZZT-OOP navbox}}

Not

2021-02-08T17:55:31Z

Rbts: Created page with "{{DISPLAYTITLE:not}} '''not''' is an internal flag in ZZT-OOP. It negates the result of condition checks which follow it within an #if statement. For example, <code..."

{{DISPLAYTITLE:not}}
'''not''' is an internal flag in [[ZZT-OOP]]. It negates the result of condition checks which follow it within an [[if|#if]] statement. For example, <code>#if not foo give torches 1</code> will add 1 to the [[Torches]] counter if no flag named "foo" is set.

{{ZZT-OOP navbox}}

Any

2021-02-08T03:17:55Z

Rbts: Created page with "{{DISPLAYTITLE:any}} '''any''' is an internal flag in ZZT-OOP. When called, it scans the entire board for matching entities, and evaluates to true if at least one instance..."

{{DISPLAYTITLE:any}}
'''any''' is an internal flag in [[ZZT-OOP]]. When called, it scans the entire board for matching entities, and evaluates to true if at least one instance is found. '''any''' can detect anything with a [[ZZT-OOP name]], and a color argument can be specified as well.

'''any''' does not look beneath statted entities, so it's possible for it to miss things that are under objects, such as fake walls.

== Usage Example ==

This object changes its char graphic whenever there is at least one (bright) red gem on-screen.
<pre>
@object
#cycle 1

:loop
#if any red gem char 2
#if not any red gem char 1
/i#loop
</pre>

{{ZZT-OOP navbox}}

Energized

2021-02-08T02:54:47Z

Rbts: Created page with "{{DISPLAYTITLE:energized}} '''energized''' is an internal object flag in ZZT-OOP. This flag is true when the player has temporary invincibility from having touched an En..."

{{DISPLAYTITLE:energized}}
'''energized''' is an internal object flag in [[ZZT-OOP]]. This flag is true when the player has temporary invincibility from having touched an [[Energizer]].

== Usage Example ==

This object shoots randomly when the player is energized:
<pre>
@object
#cycle 1

:loop
#if energized shoot rnd
/i#loop
</pre>

{{ZZT-OOP navbox}}

Contact

2021-02-08T02:46:51Z

Rbts: Created page with "{{DISPLAYTITLE:contact}} '''contact''' is an internal object flag in ZZT-OOP. This flag is true for an object when it is standing directly next to the player, and false ot..."

{{DISPLAYTITLE:contact}}
'''contact''' is an internal object flag in [[ZZT-OOP]]. This flag is true for an object when it is standing directly next to the player, and false otherwise.

== Usage Example ==

This object walks toward the player until it's standing next to them.
<pre>
@object
#cycle 1

:loop
#if not contact ?seek
/i#loop
</pre>

{{ZZT-OOP navbox}}