From Traveller Wiki - Science-Fiction Adventure in the Far future
Jump to navigation Jump to search
Worlds in this Subsector

This template list in a navigation box, lists all of the Worlds in the wiki that link to the current page, and have a Template: World with a parameter matching the first parameter of this template.

Usually this is used for the Sector articles to allow creating a list of all the worlds within the particular sector. It can also be used to list worlds in a Subsectors as well.

 |<world link match>
 |<title of area>

The World Link match parameter matches either the world name, the sector name or the subsector name in the World Template to include in the list.

The title of area allows you to change the "Sector" in the title to "Subsector" or "Quadrant" as needed. The area title defaults to Sector.

This is an update of the Template: SectorWorlds. That template suffers from the problem if a world article is linked to more than one sector (via a link in the article), it shows up in the wrong list.

This template requires that the World article page have exactly one World template containing the name of the world and sector where it is found. All remaining links must use either normal links or Template: WorldS. This isn't true of many of the World articles (at this time this was written). So when replacing the SectorWorlds template with this template, you will need to verify and update all the world articles.

This template may also produce red-links. This is caused by an world article using a {{World|...}} template to refer to a red-link world and to the sector page in question. These also need to be fixed.

This template may also have a red-link to a "Template:World.dpl.default". This is caused by there being an article in the Category:Worlds linked to the sector that does not have a {{World|...}} template in the article.

In general, adding a Template:SectorWorlds to the article and then verifying that each article meets the formatting requirements above will resolve these last two issues.

This requires the #dpl (DynamicPageList) parser function