Sponsored Links
-->

Friday, January 19, 2018

4.16 Released! - Unreal Engine Forums
src: i.ytimg.com

This style for Lua-based Module:Sports table is meant to build group and league tables for competitions with a volleyball format. Note that this module is used extensively, so test potential changes rigorously in the sandbox and please ensure consensus exists before implementing major changes. The rest of this documentation explains how to use this module with the WL style in an article or template, check the table of contents for specific items.


Video Module:Sports table/Volleyball/doc



Usage

Basic usage

In it's simplest form only several parameters need to be used to build a table

In article

The main command is the {{#invoke:Sports table|main|style=Volleyball}} statement which basically calls the module and enables you to set everything up. Then you list the positions of the teams as |team1=, |team2=, etc for however many teams you need in the table. You can use full team names there without spaces if you want, but using codes (as in the example) can make it easier. For each team you now define the big wins small wins, small losses, big losses, sets won, sets lost, setpoints won and setpoints lost by using |bwin_TTT=, |swin_TTT=, |sloss_TTT=, |bloss_TTT=, |sw_TTT=, |sl_TTT=, |spw_TTT= and |spl_TTT= respectively (with TTT replaced by the team code). If you do not define these numbers, it is automatically assumed to be 0. It is good practice though to include them anyway and to align the columns using appropriate spaces (as in the example), so the code is easy to read. The last step now is to define the |name_TTT= parameters which determine what name is shown in the table, you can use wiki markup and templates in here as well. See #Dating to see how to change the update date.

In template

The markup is effectively the same, except the |template_name= with the actual name of the Template-page, which creates the V, T and E buttons that link to the template page (so you can easily reach it from any article it is included in).

Customization

Several things can be customized in these tables

Hiding played column

Setting |hide_played=yes hides the played column.

Wins or points

By default teams are ranked by wins, but also list points which can be adjusted as follows:

As a default a big win is worth 3 points, a small win 2 points, a small loss 1 point and a big loss 0 points, these values can be overwritten to what you need by |bwinpoints=, |swinpoints=, |slosspoints= and |blosspoints=. Teams can also start the season with bonus or penalty points, this can be included by using |adjust_points_TTT= for that specific team.

Alternatively teams can also be ranked by points (set |ranking_style=points to bold that row instead)


Footer options

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 |update=, see below for details. If no source is given a citation-needed tag is shown, |source= can provide an actual link. The classification results can be shown with |class_rules=, either directly or as a wikilink to a tie-breaker rules section. Using |only_pld_pts=no_hide_class_rules 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).

Dating

The default description is match(es), this can be changed by calling |matches_text= for any other term.

Active season

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 |update=date.

Completed season

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

Future season

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

Stacking

Using |only_pld_pts= makes the table smaller, which may lead to undesired width and linebreaks in the footer that can be fixed with parameter |stack_footer=. By setting |stack_footer=yes (or y, t, true or 1 or upper case variant of those) every new information, such as "source" and statuses, is displayed on a new row.

Without stack_footer
With stack_footer

Appearance

Only the position, team, matches and points columns can be displayed by defining |only_pld_pts=yes (or y, t, true or 1 or upper case variant of those); |only_pld_pts=no_hide_class_rules 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 |splitN= 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 |teamwidth=, 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 |postitle= and the position labels by |pos_TTT= for each team.

When multiple a table compares teams from multiple groups, the group can also be listed by setting |show_groups=yes (or y, t, true or 1 or upper case variant of those) and using |group_TTT= to indicate what teams comes from what group. The group column header can be customized by |group_header=, for example |group_header=<abbr title="League">Lge</abbr>.

Team highlighting and partial table

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 |showteam=TTT. A limited part of the table is shown by |show_limit=, with the number indicating the number of position to show (if this is an even number, and it is in the middle of the table, then this number will be rounded up to the next odd number to show symmetry above and below).

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

Results and status

Indicating results

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 |res_col_header= with predefined values of Q, QR, P, PQR, PR and R (indicating various combinations of promotion, qualification and relegation), any other entry than these exact codes will print as that entry in the column header. With N the position |resultN= 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 |col_RRR=. 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 (you can use either html colours, or RGB colour codes instead if you must [this is not recommended though, because it might violate WP:COLOR]). The text in the results column is now give by |text_RRR=, 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 (promotion, qualification, advancing to next round), blue for the second-level positive events (promotion play-offs when direct promotion exists, play-offs when direct qualification exist, secondary continental tournament), 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 (with lower levels corresponding to entry in lower rounds [green1 first, then green2, etc].) 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:

  • Football colour guidelines

Indicating status

The promotion/qualification/relegation status of a team can be indicated by |status_TTT= 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:

  • Teams start out without status letter
  • Teams that get eliminated get status (E)
  • Teams that can still finish worse than second (and might be eliminated) will remain without status
  • Teams that will finish at least second will get status (T)
  • Teams that will finish for sure second will get status (Q)
  • Teams that will finish for sure first will get status (A)

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 |status_text_L= to indicate a non-standard status.

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

Notes

When notes are present, they are automatically added to the footer. The following notes are available for teams with |note_TTT= 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 |note_res_RRR= and the result header can have a note with |note_header_res=. Head-to-head result tiebreakers are listed in the points column and can be inserted with |hth_TTT=, which can be shared between teams as with all-purpose notes.

Matches

The match list can be added by displayed by defining |show_matches=yes (or y, t, true or 1 or upper case variant of those). The column headers for the match results are defined by |short_TTT= for team TTT. The results for the game TTT vs. SSS can now be input by |match_TTT_SSS=. 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 |match_TTT_SSS_note=, this note can be shared with team TTT note by setting |match_TTT_SSS_note=TTT when |note_TTT= is set. The width of the match columns can be customized by setting |match_col_width= to the desired width.

Source of article : Wikipedia