Wiki Editing

This is a help page for wiki contributors. It has guides for editing standards, a list of templates, useful links, and more.

For further help and discussions, please chat in the *#wiki* channel on the LBR Discord. The current wiki admins are: RDMPixel, ScriptFactory, and Darkly77. At time of writing they are generally quite active on Discord.

## Images

Uploaded images are typically upscaled to x10. This makes it possible to scale them up in size where needed, and makes it easy to show them at their default size (ie. just remove a zero from their dimensions). If you're upscaling with Photoshop, choose the "nearest neighbor" option, which is pixel perfect.

When making a gallery, you can edit the gallery's `widths="xx"` attribute in the source editor to make each column and its image more narrow. The `heights` attribute can also be used.

Find more info, see Fandom's docs: Help:Galleries.

DefaultCommonUncommonRareEpicMythicalLegendary
## Upgrades/Shops

* Upgrades typically use the standard shown in the table below. They use class "`wikitable`". Their columns can be made sortable, mainly to sort by cost.
* For the Max column, a dash indicates that the shop does not limit the number of upgrades. To show a max value based on the inventory limit instead, use {{Calclimit}} and show in parentheses. For single purchases, max is 1 to differentiate from upgrades that are not limited by the shop.
* The upgrade description is often shortened to be more concise, and named "Effect". If the description was lifted straight from the game then it should be italicized to indicate so.
* Long notes are added as references, with the upgrade name in bold (so users don't need to click each reference to see what it points to).
* Numbers below 999 trillion are shown in metric first (999t, i.e. default notation), and higher numbers are shown in scientific notation first. Avoid numbers such as 10,000 as the comma here is locale-dependent (shown as . in some locales and in a different place for others). When possible, use the same notation everywhere on the page. Also remove spaces, for example 1e10 (10b), as numbers on the wiki are often more detailed than those in game.
* Base Price and Increase Multiplier are shown in a single column to make it easier to see how the result is determined, and for brevity.
* Nearly all shop purchases have pages that they should be linked to, for example Tree and Fertilizer details are discussed in Leaf Spawns. Because of this, use the entire upgrade name as the linked text. This also makes it so that links in the Effect column are often unnecessary.
* Prevent the Cost column from wrapping. In a table that spans the entire width of a page, cells narrower than the widest cell tend to wrap. To keep an entire column from wrapping, use `|style="white-space: nowrap"|` in a non-header cell on the longest/widest cell to affect the entire column.

1. ↑ **Cost**: Before discounts are applied. Costs for upgrades with multiple levels are shown with a formula, where *n* is the current upgrade level. If no levels have been bought yet, *n* equals 0.
2. ↑ **Leaf Marketing**: There is no direct limit on the number of upgrades, but there is a limit on how many basic leaves can be stored in inventory to make the purchase.

When referring to something named such as an upgrade inside a sentence or phrase, use *italics*. For example, it is recommended to upgrade *Leaf Marketing* for  Gold Leaves. Using **bold**, which seems to have often been done before this standards page was created, is unnecessarily emphatic.

*See also* links are often appropriate underneath headers and should be italicized.

## Tables

Tables are typically built with narrowness in mind, to reduce the need for panning left/right on mobile. For this reason, extra information is often added as reference notes, rather than in their own column.

There are 3 table classes available, which each make tables look different. Tables can also have no classes, which makes their borders invisible. Generally the preferred class is `wikitable`, which makes tables slim. The default table class is `fandom-table`.

`fandom-table`

 Content A
 Content A

`wikitable`

 Content A
 Content A

No Class

 Content A
 Content A

## Templates

### Custom Templates

There are a number of custom templates available, mainly for showing icons. Click the template name for docs/examples/previews.

In the visual editor, you can type `{{` to bring up the template inserter. You can press Tab to cycle through a template's fields, and press Ctrl+Enter to apply your template.

If designing or modifying a template, be sure to maintain template data in the documentation so that the template inserter works correctly. In most cases, parameters should be named and have position aliases to make them easy to work with in both the visual and source editors.

*See also: Special:UncategorizedTemplates, which shows the templates listed here, plus others created much earlier which have lower rates of usage across the wiki.*

Other Commonly Used Templates

1. ↑ **Opts:**  means this template can optionally show text/quantity.
2. ↑ 2.0 2.1 **Author:** Listed in case you have questions. Most authors are active on Discord.

### Template Docs

Documentation relating to templates.

* Help:Template types [Fandom]
* Help:Templates [Fandom]
* Help:Template [Wikipedia]
* Help:Template\_documentation [Fandom]
* Help:TemplateData [MediaWiki]
* Help:Conditional expressions [Wikipedia]
* Help:Extension:ParserFunctions *(if, switch)* [MediaWiki]
* Extension:Variables [MediaWiki]

## Useful Links

### Pages with Galleries

* Community Leaves
* Enemies
* Skins

### Sandboxes

These are test pages. They're generally only used by the author, but may have demos and tests that are useful.

* User:Darkly77/Sandbox — Includes demo pages for icons. May be made into proper wiki pages at a later date.
* User:ScriptFactory/Sandbox