Template:Drop/doc: Difference between revisions

From Phantasy Star Universe Clementine
No edit summary
(split rendering components to own page)
 
(7 intermediate revisions by the same user not shown)
Line 9: Line 9:
},
},
"description": {
"description": {
"en-ca": "The source of the drop. Maximum 32 characters."
"en-ca": "The source of the drop. Maximum of 32 characters. Stored in Cargo."
},
},
"example": {
"example": {
Line 22: Line 22:
},
},
"description": {
"description": {
"en-ca": "The label of the table the drop belongs to. Max 32 characters."
"en-ca": "The label of the table the drop belongs to. Maximum of 32 characters."
},
},
"example": {
"example": {
Line 57: Line 57:
"type": "number",
"type": "number",
"required": true
"required": true
},
"name": {
"label": {
"en-ca": "Item Name"
},
"description": {
"en-ca": "The name of the item. Used for Template:Drop/Article."
},
"example": {
"en-ca": "Eternal Psychodrive/U+"
},
"type": "string"
},
"link": {
"label": {
"en-ca": "Link to Page"
},
"description": {
"en-ca": "The page of the item. Used for Template:Drop/Article. "
},
"example": {
"en-ca": "Eternal Psychodrive/U+"
},
"type": "wiki-page-name",
"suggested": true
}
}
}
},
"description": "Template used for displaying and/or storing items and their drop locations in Cargo.",
"paramOrder": [
"source",
"table label",
"item id",
"tickets",
"name",
"link"
],
"format": "block"
}
}
</templatedata>
</templatedata>


== Notes ==
== Notes ==
* If used in a namespace, the store will fail with notice.  
* Calls [[Template:Drop/Article]].
* If '''any''' invalid arguments are provided, the store will silently fail.
* 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.
** 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.
* Additionally, if any stores are rejected on a page using this template, all subsequent stores (using this template?) on said page will automatically fail.

Latest revision as of 17:05, 6 July 2025

This is a documentation subpage for the Template:Drop page.

Template used for displaying and/or storing items and their drop locations in Cargo.

Template parameters

This template prefers block formatting of parameters.

ParameterDescriptionTypeStatus
sourcesource

no description

Stringrequired
table labeltable label

no description

Suggested values
Clear Box Area Drops Mid-Mission Box
Stringrequired
item iditem id

no description

Stringrequired
ticketstickets

no description

Numberrequired
namename

no description

Stringoptional
linklink

no description

Page namesuggested

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.