This page discusses things one should know when publishing and subsequently filling out the publication page for TASVideos. It is designed to guide a publisher though the publication process and minimize errors.
For information on the requirements for the position, consult Roles.
This section walks a publisher through the publication form as well as additional steps that need to be taken to publish a movie.

Game header information

Game version

Use USA, JPN, or Europe for their respective regions. Use JPN/USA for multi-region releases. For worldwide releases ("JUE" or "W"), use "Any". ROM version and revision ("v1.1", "PRG0") identifiers should be added if necessary.

Game name

Branch name

General notes

Structure

The point of having branches is to highlight specific goals that the runs can have. Such goals can be of two kinds:
We don't have "default goal", therefore we don't use "any%" as a branch label. Instead we try to tell what is unique in every branch: something other branches of the same game don't represent. To figure out what to put in the branch label, we need to answer this question:
Is the condition set in this run so common that the opposite is an exception?
Something must be considered possible unless we are sure it is not. Obsoleted movies should count. Statistics can be assessed on 2 levels:
There are cases where some branch is unique in not setting any unique conditions. There is nothing to put in its label, because it explicitly avoids unique goals. We call such runs trunk and leave their labels blank. Remember that this is not related to "any%" or "default goal", because these things are complicated, relative, and not always clear. Also note how "trunk" describes the same thing as "branches" in real world: they describe a tree. We try to structure runs of the same game in a similar manner.
Sometimes it's not possible to have a single branch that does nothing unique. It can happen when an internal game condition is used in several available ways across branches, and neither is uncommon ("1 player" versus "2 players", "warps" versus "warpless", "Sonic" versus "Knuckles"). Since neither of such options is overwhelmingly common and neither is rare, we label each of them, as long as more than one is represented. In that case we don't have a trunk, nothing to be left without label.

When there is only one branch

For goals that are generally uncommon and can not be a trunk (pacifist, playaround, various kinds of major skip glitches, newgame+, etc) it is preferred to put a label even if there are no counterpart runs. This works the same as with branches of a single game, just on a bigger scale, and has the same purpose: highlighting unique goal types.
Goals that are common (specific player count, character choice, route through the map) don't have to be labeled if there are no counterpart runs.

Percentage labels

If the game has a built-in definition which best describes a run, then use it where it makes sense to do so. For example, the Metroid series displays an item collection percentage upon game completion, use 0% or 100% to describe a branch as depicted in-game.
If the game does not have a built-in definition, or the built-in definitions aren't necessarily used, for example a Metroid run which aims to visit the entire map, pick a concise description which best describes the goal, for example 100% map.

Major skip glitch labels

If the glitch used or avoided has a common name, such as BLJ (Backwards Long Jump) in Super Mario 64, put just its name in the branch label.
If it has no special name, but belongs to a common glitch type (SRAM glitch, game end glitch, warp glitch, demo glitch), put both the type and the word "glitch" in the label.
If it has no common name and doesn't belong to a common glitch type, invent a new descriptive and accurate type for it. Consult with community members and staff as mentioned above.

ROM name

Use ListAllMovies as a reference of previous spelling & naming conventions.

Tier

Flags

Various extra flags:

Game select

Select the game this publication is for. Use GamenamesEditor to create the entry if needed.

Player information

General rules on the entries

Example:
John Smith (johnS), Frank Black, BigBrain5 & HRT (taser888)

Submitted name(s), nick(s)

Select player

Sometimes, the player already exists in the database, but the publication form does not recognize the similarity and offers to create a new player entry. Be sure to select manually the existing player from the "select player" select box in those cases. (Applies to Xipo among some others.)
Remember, if this is an author's (or author combination) first publication they will need to be tied to their forum account (see below).

Files

Input file

Attaching a screenshot

MKV/MP4 files

This site was born from of the need to provide good-quality multimedia files of TAS movies. We take quality very seriously, and strive to produce files that are both pleasant to watch and are as small as possible. This is one of the guidelines we follow in the publications; the Encoder Guidelines tells more and is mandatory reading for anyone who wants to make MKV/MP4 files to be published on this site.

Adding a BitTorrent file

All video files must be available through the site's BitTorrent tracker.

Adding mirror and streaming URLs

For publication purposes, a mirror of the downloadable encode and a streaming media must both be present - this makes it easy for our viewers to obtain and/or view the video.
Note: When creating an archive.org collection, avoid using quotes in the entry name.

Description and movie categories

Select the movie that will be obsoleted

Categories

Movie description

Additional steps

Assign new player roles/ranks

Ensure availability of new videos


PublisherGuidelines last edited by Nach on 3/29/2018 7:39 PM
Page History Latest diff List referrers View Source