User talk:4e696e6a6f795844/Sandbox

Question

Hey just a quick question, you know how you said you tried to use dpl on tooltips, does that you mean you are trying to link the tooltip in the item infobox to tooltip page? LordofEditing =(Talk)= 00:28, 8 December 2016 (UTC)

Yeah, in my opinion, it's easier that way, rather than going through each wiki page and typing the tooltip out. 4e696e6a6f795844 (talk) 00:54, 8 December 2016 (UTC)

Have you figured out how to link the tooltip word to the page itself? LordofEditing =(Talk)= 01:07, 8 December 2016 (UTC)

If you mean formatting the tooltip to be like "Tooltip: [tooltip]", then yes. Compiling the other infobox's tooltips and armor set bonuses into one row is the real problem right now. 4e696e6a6f795844 (talk) 01:16, 8 December 2016 (UTC)

What I meant is whether or not you could link the word tooltip in the item infobox before the text. For example | tooltip = Pizza. Doesn't work there, for some reason. LordofEditing =(Talk)= 01:20, 8 December 2016 (UTC)

Ah, I totally misread what you were saying. To be honest, its best not to link tooltips in the item infobox until it's near completion- you wouldn't want to click on the link to find it isn't finished yet... 4e696e6a6f795844 (talk) 01:42, 8 December 2016 (UTC)

True... LordofEditing =(Talk)= 06:26, 8 December 2016 (UTC)

Complicated

I took a quick look at your code here and I was wondering why this is so complex. A lot of items seem to be be entered explicitly. Is this because of DPL difficulties with merged pages or something? I'm just concerned that if this is used at a wiki article it'll be difficult for others to maintain in the future. Equazcion ^(talk) 23:26, 13 Dec 2016 (UTC)

The parts entered in text are due to DPL merging tooltips, such as the George's Outfit outputting "Oh myyy!""Oh myyy!""Oh myyy!""Oh myyy!" if I were not to override it. I was thinking of converting it to {{#dpl:}} format so I could use line breaks, but that proved to be difficult, as then I would have to evade all the bars with {{!}}. I do see your point though, maybe I should look into simplifying it... 4e696e6a6f795844 (talk) 23:47, 13 December 2016 (UTC)

Ah I see. Just want to make you aware of a couple things that may help:

You can put the format on a separate template page. This is how DPL listings are handled on most pages here. The syntax in the DPL statement would be include={included template name¦listing format template name}. See Swords/dpl for an example of how they look.

This has a couple of benefits. You wouldn't need to do a lot of that "vardefine" hacking with the comma character, as format templates let you refer to template parameters using named triple-brackets ({{{tooltip}}}).

It also means, as you can see at the Swords DPL template, that you can choose not to output a listing based on a conditional. We could use the "listexclude" parameter in {{item infobox}} to avoid the repeats. Again you can have a look at Swords/dpl for how it's used. Basically it's a conditional that doesn't output anything for item infoboxes with listexclude=yes.

I think we could add listexclude=yes to the individual templates on merged pages without messing up other DPL listing -- or if that is a concern, we could add a new exclusion parameter to {{item infobox}} especially for these types of listings. Equazcion ^(talk) 02:11, 14 Dec 2016 (UTC)

Immunity Dpl

I don't mean to step on any toes, but you may want to take a look at the dpl I created at User:Ferretwings/Sandbox/DPL#Immunity_Dpl – Ferretwings ^(talk) 20:04, 27 February 2017 (UTC)

Better than what I could do, I would have never thought that I could just check every immune in one dpl with regex. Is it OK that I use your code for the immunity listings? 4e696e6a6f795844 (talk) 20:34, 27 February 2017 (UTC)

Yes, of course :) I do so love it when a plan comes together. – Ferretwings ^(talk) 22:02, 27 February 2017 (UTC)