Pizza Tower Wiki:Guidelines, Editing & Help/Pre-release build pages

Pre-release builds are versions of the game that were made prior to the full release, showing the game in various states of development. Pre-release build pages contain information about the build's content, such as gameplay, differences between the previous build and final release, version changes of said build, and more.

Name Guidelines

Names are determined by the Itch.io page name it was published under, or the original .zip filename. There are some other things to keep in mind:

• Add the year in parentheses to the end of its name if the build uses a month for its name or its name is too similar to an existing build
• Add "(Build)" to the end of the build name if its name is generic (i.e. "GOLF" or "Desert")
  • Be sure to add a link to the build on the relevant disambiguation page!
• If a build name contains "Build" or "Demo," keep it
  • If both are present, use "Build" instead
• Steam pre-release builds do not have official names and are grouped together by months

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

Examples:

• 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)

Infobox

Prerelease build pages make use of the Infobox build template. This shows basic information of the build, such as its compilation date(s), file size, and safe download links. For information on how to use the template, please see its documentation.

As of July 18th 2024, links leading to leaked builds, i.e. build meant for private use or official playtesters only, are not allowed to have their download linked on the wiki at the request of Tour de Pizza. Documenting their content is completely fine, however.

Content

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.

Introduction

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

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.

Levels

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.

Revisions

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.

Bugs

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.