Template:Drop: Difference between revisions
(add rendering component) |
mNo edit summary |
||
Line 8: | Line 8: | ||
|item_id = {{{item id}}} | |item_id = {{{item id}}} | ||
|tickets = {{{tickets}}} | |tickets = {{{tickets}}} | ||
}}{{#if:{{{name| | }}{{#if:{{{name|}}}|'''{{{name|[[{{{link|{{{name}}}}}}|NAME]]}}}'''<br>{{#if:tickets|{{Drop Rate|tickets}}}} | ||
}}</includeonly><noinclude>{{#cargo_attach:table = Drops}}</noinclude> | }}</includeonly><noinclude>{{#cargo_attach:table = Drops}}</noinclude> |
Revision as of 16:37, 6 July 2025
Template used for displaying and/or storing items and their drop locations in Cargo.
Parameter | Description | Type | Status | |
---|---|---|---|---|
source | source | no description | String | required |
table label | table label | no description
| String | required |
item id | item id | no description | String | required |
tickets | tickets | no description | Number | required |
name | name | no description | String | optional |
link | link | no description | Page name | suggested |
Notes
- Calls Template:Drop/Article.
- If used in a namespace, the store will fail with notice, superseding all other functionality.
- If any arguments that would be passed to Cargo are invalid, the store will silently fail.
- It is not known to me, at this time, if it is possible to make Cargo return an error if validation fails without duplicating the logic into the Drop template itself. As a stopgap, viewing page values will detail what fields are being sent to Cargo.
- Additionally, if any stores are rejected on a page using this template, all subsequent stores (using this template?) on said page will automatically fail.
This template adds rows to the table "Drops", which is declared by the template Drop/Cargo. View table.