Template:Drop: Difference between revisions

From Phantasy Star Universe Clementine
(Created page with "<noinclude>{{{{FULLPAGENAME}}/doc}} </noinclude><includeonly>{{#if:{{NAMESPACE}} | |{{#cargo_store: _table = Drops |source = {{{source}}} |table_label = {{{table label}}} |item_id = {{{item id}}} |tickets = {{{tickets}}} }} }}</includeonly><noinclude>{{#cargo_attach:table = Drops}}{{{{FULLPAGENAME}}/doc}}</noinclude>")
 
mNo edit summary
Line 9: Line 9:
|tickets = {{{tickets}}}
|tickets = {{{tickets}}}
}}
}}
}}</includeonly><noinclude>{{#cargo_attach:table = Drops}}{{{{FULLPAGENAME}}/doc}}</noinclude>
}}</includeonly><noinclude>{{#cargo_attach:table = Drops}}</noinclude>

Revision as of 15:10, 15 March 2024


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

Template parameters[Edit template data]

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.

This template adds rows to the table "Drops", which is declared by the template Drop/Cargo. View table.