Template:Recipes/register
跳到导航
跳到搜索
This template is used to store the data for a recipe into the cargo database.
Usage
{{recipes/register
| version = <recipe exclusivity (see below)>
| result = <result item name> | resultid = <result item ID> | amount = <result item amount> | note = <note text> | image = <result item image>
| station = <crafting station name>
| <ingredient 1 name> | <ingredient 1 amount>
| <ingredient 2 name> | <ingredient 2 amount>
...
| <ingredient n name> | <ingredient n amount>
}}
| version = <recipe exclusivity (see below)>
| result = <result item name> | resultid = <result item ID> | amount = <result item amount> | note = <note text> | image = <result item image>
| station = <crafting station name>
| <ingredient 1 name> | <ingredient 1 amount>
| <ingredient 2 name> | <ingredient 2 amount>
...
| <ingredient n name> | <ingredient n amount>
}}
For <ingredient name>, you can use the following syntax to customize its image/note: <itemname>(#i:<image>)?(#n:<note>)?
. You can use &
to represent the item name in #i:<image>
. Further more, #i:old
is a shortcut for #i:& (old).png
. For example: Tungsten Bar#i:old
is same as Tungsten Bar#i:& (old).png
and will get 钨锭 (same as the result of {{item|Tungsten Bar|image=Tungsten Bar (old).png}}
). This is mainly used in old-version-exclusive/platform-exclusive recipes.
Notes
- All result and ingredient amounts are required, even if they are 1.
- The
parameter is only to be used if there are two or more recipes for a result item or if a result item is only craftable on a proper subset of the versions it is available on (i.e., if it can be crafted on one version but not on another). Result items that are exclusive to at least one version generally do not getversion
tags, since the little version icons added by {{item}} sufficiently denote exclusivity of the entire recipe (the same applies to recipes including ingredient items that are exclusive to any version).version
- Use {{eversions}} with
as the parameter's value.code=y
- Use {{eversions}} with
- The
andnote
parameters are rarely used, and are only appropriate in edge cases. Forimage
, if l10n is needed, you should use l10n ref instead of actual text. For example,note
|note=#note_moon_1
will usel10n['result_note']['#note_moon_1']
from Module:Recipes/l10n as result note. - This template shouldn't be used on normal pages, and instead should only be used on
Recipes/[station]/register
subpages. Here's a list of all those subpages:
分类:
- Pages setting LuaCache keys
- Templates using Lua
- Templates using Cargo
- Recipes templates