Template:Drop/doc: Difference between revisions
(clean up notes) |
No edit summary |
||
Line 14: | Line 14: | ||
== Notes == | == Notes == | ||
If '''any''' invalid parameters are provided, the store will silently fail. Additionally, if any stores are rejected on a page using this template, all subsequent stores using this template will automatically fail. | * If used in a namespace, the store will fail with notice. | ||
* If '''any''' invalid parameters are provided, 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 will automatically fail. |
Revision as of 11:10, 4 January 2025
Purpose
Template used for storing items and their drop locations in Cargo.
Parameter List
{{Drop |source <!-- The source of the drop. Only accepts a string, maximum 32 characters. --> |table_label <!-- The label of the table (e.g. "Clear Box", "Area Drops", "Mid-Mission Box", etc). Used to disambiguate sub-sources within a source. Only accepts a string, maximum 32 characters. --> |item_id <!-- The ID of the item. Only accepts a string, maximum 8 characters. --> |tickets <!-- The number of tickets allocated for the item, as an integer. --> }}
Notes
- If used in a namespace, the store will fail with notice.
- If any invalid parameters are provided, 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 will automatically fail.