Template:Drop/doc: Difference between revisions

From Phantasy Star Universe Clementine
mNo edit summary
(add name)
Line 9: Line 9:
},
},
"description": {
"description": {
"en-ca": "The source of the drop. Maximum of 32 characters."
"en-ca": "The source of the drop. Maximum of 32 characters. Stored in Cargo."
},
},
"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. Not stored in Cargo. If omitted, the template will not render."
}
}
}
},
},
"description": "Template used for storing items and their drop locations in Cargo. "
"description": "Template used for displaying and/or storing items and their drop locations in Cargo. All parameters within are stored in Cargo unless otherwise stated."
}
}
</templatedata>
</templatedata>


== Notes ==
== Notes ==
* If used in a namespace, the store will fail with notice.  
* If used in a namespace, the store will fail with notice.
* If '''any''' invalid arguments are provided, the store will silently fail.
* If name is provided, the template will render a table row.
* 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.

Revision as of 16:02, 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. All parameters within are stored in Cargo unless otherwise stated.

Template 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

Unknownoptional

Notes

  • If used in a namespace, the store will fail with notice.
  • If name is provided, the template will render a table row.
  • 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.