Test case for this question. On the left is a DPL call trying to retrieve parameter values set in the making of the infobox on the right. It fails hard, there are many more parameters.
To simplify the test there's only one type of "effect", see the Details section.
- As a template,
#tagto build an infobox dynamically
- Infobox base effect adds an "effect" row to that infobox
- Effect STR bonus calls
Infobox base effectand passes arguments to it, though only one is actually displayed by the infobox.
- The template call to
Infobox weaveron this page injects instances of
Effect STR bonusand can override most of the parameters it sets.
- The call in point #4 is how this feature is meant to be used
- Other features want to rely on DPL to retrieve the data "stored" that way
- Phantom can replace any of the other templates in the
includestatement of a DPL call. It adds one table row per parameter stolen from the "real" template it replaces.
I can't get DPL to see most parameters, it only catches those that were defined in the top level, i.e. in the template call to
Infobox weaver when
Effect STR bonus.
I'd like to catch all values passed by
Effect STR bonus into
Infobox base effect.
Infobox base effectis not called directly on this page so it seems that DPL can't replace it to catch the values passed into it by
Effect STR bonus. If it's really the issue, any idea?