#OPENTTD SCENARIOS CODE#

Useful to mark unacceptable versions based on arbitrary criteria, for instance unsupported dependency versions. Specify 'minimal acceptable version' - any versions lesser than it will be marked with crimson color.

Specify empty header to remove it completely. Most badges may be tweaked by specifying additional parameters in the URL. May be tweaked with header, minversion, and allow_ignored parameters (see below). Pick as many as you want! You may add ?header= to the URL to leave only the version. These show version in specific repository. May be tweaked with header parameter (see below). These badges also support minversion= parameter. There may be multiple versions, for example devel and newest, or multiple variations of the same version encountered in some repositories (e.g. This shows latest version(s) known to repology. Tiny badge with latest packaged version(s) Debian Stable, Testing, Unstable and Experimental all belong to a single family and are thus only counted once. Repository family is an aggregation of related repositories, e.g.

This shows total number of repository families featuring this package. Feel free to submit PRs with missing dates. Note however that this will only work for repositories which have end of life date ( valid_till) set in the configs. You may also exclude old and no longer supported repositories with exclude_unsupported=1 parameter. use exclude_sources=modules,site to exclude e.g. You may exclude specific kinds of sources ( repository, modules, site) with exclude_sources parameter.

It's also possible to specify number of columns with columns= parameter.

#OPENTTD SCENARIOS CODE#

HTML code for right-aligned badge (most useful for README.md as it allows other content to flow around it not leading to space waste): This badge shows versions and up to date status of this project in all known repositories.

Openttd scenarios