User:ZaptorZap: Difference between revisions
Jump to navigation
Jump to search
Created page with "== TETR.IO Map Format == {{Ambox | issue = '''''This section is a work in progress.''''' It will be fully realized within the week, I swear. (posted Wed 14 Jul 2021) | dat..." |
m bulking it out a tiny bit before i head to bed |
||
| Line 1: | Line 1: | ||
== [[TETR.IO]] | == [[TETR.IO]] map format == | ||
{{Ambox | {{Ambox | ||
| issue = '''''This section is a work in progress.''''' It will be fully realized within the week, I swear. ( | | issue = '''''This section is a work in progress.''''' | ||
| date = posted Wed 14 Jul 2021 | |||
| info = It will be fully realized within the week, I swear. [[User:ZaptorZap|ZaptorZap]] ([[User talk:ZaptorZap|talk]]) 10:47, 14 July 2021 (UTC) | |||
| image = [[File:Ambox_stub.png|50px]] | | image = [[File:Ambox_stub.png|50px]] | ||
}} | }} | ||
The purpose of this format is simple: allow the end-user to define a custom playfield, as opposed to an empty one, before gameplay. This playfield is normally one which is created to test a variety of case scenarios which may be otherwise difficult and time consuming to test legitimately with regular TETR.IO mechanics. Such case scenarios may include: | |||
# Testing the various kick tables, such as [[SRS]], and their interactions with board states. | |||
# Testing the [[top out]] mechanic and its interaction with the [[Rotate#Initial_rotation_system_(IRS) | initial rotation system]] and/or [[Hold_piece#Initial_hold | initial hold system]]. | |||
# Testing whether or not TETR.IO can handle unexpected line clears, such as [[T-Spin]] Mini Quads, or line clears consisting of 5 or more rows cleared at once. | |||
Because of these reasons, the proprietary TETR.IO map format has likely existed as long as TETR.IO itself. Despite this estimated age however, use of the custom map systems were limited to the developer<ref group=note>Before the ZEN mode update, players had one chance to play with a custom map. Custom maps were defined in QUICK PLAY during [[TETR.IO#April_Fools.27_2020 | April Fools' 2020]].</ref>, that is, until the [https://tetr.io/about/patchnotes/#chlog_4_0_0 ZEN mode update released]. This is due to the simple fact that ZEN progress is stored clientside, '''and this progress includes board state.''' | |||
=== Technical explanation of the format === | |||
=== Creating, and then accessing/importing your own maps === | |||
== Notes == | |||
<references group="note"/> | |||
Revision as of 10:47, 14 July 2021
TETR.IO map format
The purpose of this format is simple: allow the end-user to define a custom playfield, as opposed to an empty one, before gameplay. This playfield is normally one which is created to test a variety of case scenarios which may be otherwise difficult and time consuming to test legitimately with regular TETR.IO mechanics. Such case scenarios may include:
- Testing the various kick tables, such as SRS, and their interactions with board states.
- Testing the top out mechanic and its interaction with the initial rotation system and/or initial hold system.
- Testing whether or not TETR.IO can handle unexpected line clears, such as T-Spin Mini Quads, or line clears consisting of 5 or more rows cleared at once.
Because of these reasons, the proprietary TETR.IO map format has likely existed as long as TETR.IO itself. Despite this estimated age however, use of the custom map systems were limited to the developer[note 1], that is, until the ZEN mode update released. This is due to the simple fact that ZEN progress is stored clientside, and this progress includes board state.
Technical explanation of the format
Creating, and then accessing/importing your own maps
Notes
- ↑ Before the ZEN mode update, players had one chance to play with a custom map. Custom maps were defined in QUICK PLAY during April Fools' 2020.