Baldur's Gate Wiki
Register
Advertisement

This category houses all infobox templates, as well as those templates primarily designed to be used within infoboxes. Most of them are already migrated to portability.

Note: If these are edited, no matter the mask used, it might happen that they loose their portable status. This is shown, after the edit was saved, by a warning box at the upper right side of the page just below the "Edit" button, telling: "Migrate this infobox". In this case, the button inside the message to "generate draft markup" does not have to be used, as the infobox already was migrated once.
Most of the times, the status can be repaired by making a
null edit on the template's documentation, the link to which is usually found at the bottom of the page: click this link, click "Edit", make no change, but "Save" the page. Then click the link back to the template at the top of the page again, and the message about migration should be gone. If not, please contact an administrator.

Adding new infoboxes, if there's any need for this, should be done with the InfoboxBuilder, so that portability is granted from the start.

How to fill[]

– Some general information about infoboxes on the Baldur's Gate Wiki
Leave empty or not?
Infoboxes work in a way that empty/unused fields usually won't be shown. However, any editor of an article can't be sure if a parameter without a value was left empty on purpose or because the information wasn't known. When editing and you're sure about a field not needing a value, please use a comment – such as "<!-- 0 -->" – for it, rather than leaving it empty, to avoid uncertainties (such a comment still counts as "empty" and will not be shown on the article); fields where "yes" and "no" are the expected values should be set to "no" in this case.
Auto-cat and auto-link
Many parameters automatically categorize the article and/or link an entry to a related page. To make this work as intended, the "expected values" in each infobox documentation's "Fields and parameters" section[yet implemented only for items] should be regarded, as well as notes on formatting (usually without link brackets, "[[<…>]]") or singular/plural. However, for fields with multiple values – often due to differences between games/editions – or with notes or references, categories and links have to be set manually.
Auto-display
Another feature, some of the infoboxes use for some fields, is the automatic display of wanted entries, depending (or not) on "expected values" again (see above). This includes:
  • capitalization and singular/plural;
  • hiding of fields;
  • automatically generated fields;
  • automatically generated entries, even if fields were left empty.
Bugs
If in any field the actual information is different from what is shown or stated in-game, please use the correct information instead and mark this as a bug, both inside the infobox and on the page's main content:
  • add <sup>[[#Bugs|b]]</sup> at the end of such infob;
  • add – if not already present – a new section ==Bugs== to the article – near the bottom, but before a "Gallery", "External links" or "References";
  • add a note about the bug to this section, starting with an asterisk, "*"; if the bug appears only in a single game or is edition-dependent, add the related game icon(s) at the start of this note; in this case, please mention also that the bug "is fixed in …";
  • add the article to the bugs category if not already in it.

Please note that in this case the above explained auto-linking/-categorizing feature for this infobox field is disabled and such has to be done manually.

The previously used method of displaying the false in-game information crossed-out ("<s><…></s>") and adding the correct info behind shouldn't be used anymore. Instead, this should be mentioned on the article's main content in the related section, in addition to being noted under "Bugs".

All items (74)

Advertisement