#### 아래글 옵션
The footer information can be customized (although notes and status will be inserted automatically if they are called; see XXX and YYY). The update date is set by , see below for details. If no source is given a citation-needed tag is shown, can provide an actual link. The classification results can be shown with , either directly or as a wikilink to a tie-breaker rules section. Using suppresses the classification rules (this should only be used in template calls when multiple groups are summarized on a page and the rules are listed elsewhere on that page).

##### 날짜
The default description is match(es), this can be changed by calling for any other term. 

When the season is active, the footer should include the date of the last match played that is included in the table. This can be achieved by setting .

When all matches have been played, the season is completed and the update line can be removed by setting .

Before any games are played, the date of the first game should be indicated by using and setting the start date by .

##### 쌓기
Using makes the table smaller, which may lead to undesired width and linebreaks in the footer that can be fixed with parameter . By setting  every new information, such as "source" and statuses, is displayed on a new row.

#### 모양
Only the position, team, matches and points columns can be displayed by defining ; suppresses the classification rules only (this should only be used in template calls when multiple groups are summarized on a page and the rules are listed elsewhere on that page). A line can be added between section of the table (if desired) by adding with N the position below which the bar should be shown. (Note that this bar will not be shown for the bottom position in the table). A custom width of the team column can be set by , for example when multiple groups exist within one tournament and you want to force the same width on all groups. The position column header can be customized by and the position labels by for each team. When multiple a table compares teams from multiple groups, the group can also be listed by setting  and using to indicate what teams comes from what group.

#### 팀 강조 및 순위표 일부만 표시
When using a table on a team (season) page, you might want to highlight the team (and possibly only show part of the table), especially after a template call to a long league table. Team TTT is highlighted by . A limited part of the table is shown by , with the number indicating the number of position to show .

A table can also start at position N, by using in the module call.

### 결과와 상태

#### 결과 표시
The result of the table rankings can be indicated by a coloured bar and text indicating the result. The header of this column is defined by with predefined values of Q, QR, P, PQR, PR and R , any other entry than these exact codes will print as that entry in the column header. With N the position declares the codes (or words if you want that instead) for the results column. Now when RRR is the results column, the colours are defined by . The colours green1, green2, green3, green4, blue1, blue2, blue3, blue4, yellow1, yellow2, yellow3, yellow4, red1, red2, red3, red4, black1, black2, black3 and black4 are predefined and should be used preferentially per consensus on WT:FOOTY . The text in the results column is now give by , which can (and should) link to the relevant competition articles.

Consensus is also to use the colours in the following way: Green should be used for the top-level positive event , blue for the second-level positive events , red for bottom-level negative events (relegation) and yellow for other level events. In addition, lower level colours should be used when teams qualify for different rounds  Black should be used when teams do not play a full season and their results are expunged or void. This consensus exists to have a uniform table appearance across Wikipedia. In addition, some wikiprojects have more detailed guidelines:

#### 상태 표시
The promotion/qualification/relegation status of a team can be indicated by with the letters indicated above (although only the ones in use for this style are shown below the table). The letters will appear next to the team in the order given. Whichever letters are called out in the table will automatically be explained alphabetically in the footer.

These letters can be used for all scenarios as exemplified by the following group phase example with 4 teams that play 3 matches where the first advances directly, the second team will go to play-offs and the remaining two teams are eliminated:

If these scenarios are not sufficient, some style have wild letters L (marked with a question mark in the overview). They should be accompanied by to indicate a non-standard status.

Most styles allow for these letter to be placed after the team name or before, set or respectively, the default value can differ and it's use differs between sports or regions.

### 노트
When notes are present, they are automatically added to the footer. The following notes are available for teams with for a note for a team, when this note is a team code with a defined notes, they will share the note. Results can have notes with and the result header can have a note with . Head-to-head result tiebreakers are listed in the points column and can be inserted with , which can be shared between teams as with all-purpose notes.

### 경기
The match list can be added by displayed by defining . The column headers for the match results are defined by for team TTT. The results for the game TTT vs. SSS can now be input by . Future games can be listed with their date (possibly between small tags) or they can be left blank. (Note that this calls Module:Sports results to build the match table.) A note can be added to a result using , this note can be shared with team TTT note by setting when is set. The width of the match columns can be customized by setting to the desired width.

|sandbox||
Category:Fb templates