Editing – Prerelease Build Pages

From Pizza Tower Wiki

Prerelease builds are versions of the game that were made prior to the full release. These show the game in various states of development. Prerelease build pages contain information about the build's content, differences, unused content within those builds, changes and hotfixes between each version of the build, and basic information. Basic information would include the date the build was compiled on, and the size of all of the files combined.

Naming Guidelines

Names are either determined by the build's itch.io page or the .zip's filename. There are some other things to keep in mind:

  • If a build uses a month for its name, add the year it was released to the end in parenthesis.
    • A year in parenthesis should be added if a build name is too similar to an existing build's.
  • If a build name is generic (i.e. "GOLF," "Desert"), add "(Build)" to the end of its page title. Make sure the page is searchable through a disambiguation. This is not needed for its infoboxes.
  • If a build has the words "build" or "demo" in its title, keep them. If both are present, use "build" instead.
  • If a build's official name is unknown, follow a similar naming structure other builds released around that time use.
  • Steam prerelease builds do not have an official name, and are grouped together by months.

Unofficial community given names, most commonly Pre-Early Test Build and Pre-Jay Leno Build are not allowed.

pizzatowerdemo_testerbuild1.zip - Tester Build
PT_Rework_v1.1.zip - Rework
PizzaTower_noisev21.zip - Noise (Build)
PizzaTowerSAGE2019_v14.zip - SAGE 2019 Demo
PTjanuarymonthlybuild1.zip - January Build (2019)


Prerelease build pages make use of the {{Infobox build}} infobox, showcasing basic release information, compilation date(s), types, file sizes and availability online with a download link if possible.


{{Infobox build
|title =
|image =
|build date = 
|release date = 
|build type = 
|file size = 
|download = 
|previous = 
|next =

The nine infobox functions are as follows:

  • title - The build's name based on the naming guidelines. If no title is present, the text Title missing! will appear.
  • image - A screenshot of the build's title screen. See below for more details.
  • build date - A date of compilation pulled from the game's data.win file. These must be in GMT+0 format. If a build page has several revisions, list all of them and note the version number for each build.
  • release date - The initial release date of this (series of) build(s).
  • build type - Makes use of another template ({{buildtype|build}}) to describe whether the build was released to the public, exclusively to Patrons or a select few playtesters.
  • file size - The build's compressed (.zip) file size in MB.
  • download - Download link(s) to the builds, with an {{availability|state}} template added to the end showcasing if a build is available, repacked or unavailable.
  • previous - A link to a previously released build. If this doesn't exist or isn't set, the text N/A will appear instead.
  • next - A link to the next released build. If this doesn't exist or isn't set, the text N/A will appear instead.

Preview images for the infobox are taken from either one of these scenarios and must follow the screenshot guidelines:

  • The game boots up to a title screen (eg. a screen with the game's logo) with a menu.
  • The game immediately boots the player into a playable state, with the screenshot taking place within the first area a playable character is present.

The {{buildtype|build}} template makes use of a tooltip to display additional information about each category. One of three options are available. If an invalid option is picked or a typo is present, the text will be replaced with "Improper template usage".

Example Result
{{buildtype|public}} Public

{{buildtype|patreon}} Patreon

{{buildtype|playtest}} Playtest

The {{availability|state}} template also makes use of a tooltip and is used to show if a build is available on either one of these public repositories, either in its original (.zip) or repackaged state. Much like the previous template, the text will be replaced with "Improper template usage" if the template is used improperly.

Example Result


{{Infobox build
|title = Early Test Build
|image = Earlytestbuild.PNG
|build date = 14-7-2018 23:50:39 '''(v1)'''<br>
16-7-2018 05:47:57 '''(v2)'''<br>
16-7-2018 08:57:04 '''(v211)'''
|release date = July 15th, 2018
|build type = {{buildtype|public}}
|file size = 24,3MB '''(v1, v2, v211)'''<br>25,6MB '''(Peter Griffin)'''
|download = [https://archive.org/download/pizzatowerdemobuildspublic/Public/pizzatowerearlybuildtest.zip v1] {{availability|yes}}<br>[https://archive.org/download/pizzatowerdemobuildspublic/Public/pizzatowerearlybuildtest_v2.zip v2] {{availability|yes}}<br>
v21 {{availability|no}}<br>
[https://archive.org/download/pizzatowerdemobuildspublic/Public/pizzatowerearlybuildtest_v211.zip v211] {{availability|yes}}<br>
[https://archive.org/download/pizzatowerdemobuildspublic/Public/pizzatowerdemo.zip Peter Griffin] {{availability|yes}}
|previous = [[Pizza_Tower_test]]
|next = [[Tester Build]]


It is important to document prerelease build pages much like one would document the final game. This means the page cannot only be a list of differences. To do so without proper organization and documentation would hinder the reader's experience and make it confusing for those looking to read about specific sections about the build.

Below are specific guidelines for each section to construct a page about a prerelease build.


Every build is compiled for a purpose, whether it be to test features, for an event, or to mark progress within the game's development. Before diving into the rest of the build's contents, it is important to note why a build was made. The reason for its existence does not need to be grande. If the build was made as a joke, do note it in the introduction. Avoid using terms like "alpha" or "beta", as these don't suit well.


Gameplay may be different from the release version of the game, whether it be drastic or minor. Primarily compare and contrast these differences to the final release. If possible, add differences from the previous version as well. When comparing gameplay from these builds to the final game, it is not uncommon that opinions about mechanics will be present. It is important to stay as objective as possible when writing and leave opinions out. If a mechanic is more clunky or harder to control compared to the final game, this can be noted on the page. Do not write "it was bad" or "it was better," as this does not help the reader.

If a playable character was removed or added, do write about it. If there are multiple playable characters, order them by sub-headers. For example, if Peppino and The Noise are playable, add sub-headers under gameplay and talk about their differences.

Transformations get their own section, separate from gameplay. When noting differences between the build and the final game, a list is acceptable for documentation. When noting multiple differences in one transformation, the first bullet point should note if the changes are minor or major, then subsequent bullets should be sub-bullet points explaining further in detail.

Enemies, like Transformations, get their own section separate from gameplay. They also follow the same format as documenting transformations.


Throughout the game's history, the levels have changed layout and names constantly. They are sometimes organized into sections, often called worlds or floors. If the build organizes the levels like this, organize it as such here with tabber. Call the level by the name it is given in the build, but do link it to its modern version's page if it exists.

Adding screenshots in this section is a must. If the build only has minor changes between it and the final version's level, screenshot where the differences are visible. At least one screenshot in each world or floor is required. The maximum per world or floor is five to avoid making a gallery in that particular section.

If there are changes within the tileset used for a level, do write about it. If tile placement is slightly different from the final game, do make note of it. If it appears in multiple rooms, do not specify its location, otherwise state the room the difference is in.

In older versions of the game, there may be more than three secrets. Do screenshot once per secret room, and write where they are located and how they can be accessed. Documenting differences between visual differences between the build and the final version's secret rooms follows the same principle as levels.


Occasionally hotfixes are released for builds. Note the differences between each revision. If bugs have been fixed in a revised build, note it here.

Minor Differences

There is a chance that there are differences outside of level design and gameplay are present. Those differences, including but not limited to changes in physics, object properties, and animations shall be located here. Differences between the HUD and menu screens must be written here as well.


Every version of the game is prone to bugs, and any that exist in every version of the build must be noted here. Errors, such as a Secret Eye being missing in a level or an enemy playing the wrong animation, will be written here as well. Write about what the bug is and how to trigger it. Make sure what is here is not intentional.