• Play
  • About
  • News
  • Forums
  • Yppedia
  • Help
Personal tools

Template talk:Infobox pirate

From YPPedia

Contents

Extended Usage Notes

Extended Usage Notes

Discussion

Additional conversation can be found at:

Redesign

Implementation Redesign and Crew / Flag Ranks

Since I had enough trouble weeding through all the writing above, I'm not going to make anyone else do that to see the most current issue related to this. First, look at the discussion on Template talk:Rank box. You'll find a link to my secondary sandbox (User:Thefirstdude/Sandbox/) which has an example of what I want in action.

The changes are twofold. First, the code on all the yoweb/# pages looked horrendous and redundant, so I tidied it up a LOT, making a single Ocean header template and a single Ocean box template. This made adding my next addition about 28 times easier, namely the addition of the rank parameter and icon. Now I would just like some opinions on both these changes, and what needs to be done to them (besides adding flag and governor icons, per Fiddler's example, which I just don't want to do until something is finalized due to the magnitude of changes needed to facilitate that). -- Thefirstdude (t/c) 20:39, 9 April 2007 (PDT)

I think it looks pretty good, but one concern I can see is the amount of space that adding the other icons is going to cause problems with longer ocean names. When Attesmythe first did it the trophy and portrait gallery icons didn't exist. I can't see getting a crew rank and flag rank icon let alone the governor icon beside Midnight. Any ideas on how to deal with that? -- Cedarwings (t/c) 22:01, 9 April 2007 (PDT)
IT looks good, but I'd recommend three changes. 1)Ocean header template seems to to be adding a layer of complexity merely for the sake of adding a layer of complexity. I'd drop it and stick with the way it is now. 2)Break Ocean box template into two templates, Oceanbox-first and Oceanbox. Oceanbox-first would be just what you have now, and Oceanbox would include border-top:0px; inside the first div as demonstrated here. This allows any yoweb box following the first to flow into the one above it without a huge border mess. This is the same solution that atteSmythe and I developed in November. 3)I'd like to see the default in the template to be no icon at all rather than a blank one. This can be accomplished easily using the {{ifdef}} (Usage) template. Good examples of that template in action can be seen on {{Infobox crew}} (Usage), {{Infobox flag}} (Usage), and {{Infobox island}} (Usage) where the respective yoweb id numbers are integrated.
OK. 1) I disagree - there is absolutely no reason to duplicate that same div statement 7 different times. What if, at some point, for some reason, someone wanted to make the text color white and the background color red? Instead of having to do it seven separate times, it would just need to be done once. That is the entire point of making templates.
2) and 3): Thanks for the tips, will do! -- Thefirstdude (t/c) 22:49, 9 April 2007 (PDT)
Okies done, see here for new example. But now the ocean names of the ones without icons look weird, and I don't think I have any idea what to do about it. -- Thefirstdude (t/c) 22:59, 9 April 2007 (PDT)
What about putting the rank icons on the right of the ocean name, with the other links? Also, we'll need some margin trickery to line the images up in the middle of the box. -- Covenant7 (t/c) 05:36, 10 April 2007 (PDT)
But now the ocean names of the ones without icons look weird, - I don't think there will be many examples of mixed usage. We'll most likely see all oceans with rank icons, or none of them. What about putting the rank icons on the right of the ocean name, with the other links? - I think to the left of the ocean name looks better, as it groups all the yoweb links on the same side of the box. no reason to duplicate that same div statement 7 different times. - My concern is that it adds another part that can break for an effect that can be achieved without the additional template. Come to think of it though, you can probably find a way to stuff that div statement inside the main template and drop it from the yoweb templates entirely. the amount of space that adding the other icons is going to cause problems with longer ocean names. - I think we can compromise and leave this change at one rank icon, giving the user the choice of which icon they want to use for each ocean. Users reading with larger font sizes are already going to be running into problems with this single icon addition; I think we have now maxed out the amount of information that can be squeezed into a single line.
Also, I'd like to suggest pirate2-rank1, pirate2-rank2, etc... as variable names for the second and third pirate's ranks.--Fiddler 14:31, 10 April 2007 (PDT)
I'm going to renumber all those points for easier reference.
1) You're probably right, OK.
2) That was my thought exactly, Fiddler.
3) Well, I agree now, but I was thinking that now that it's been split into oceanbox-first and oceanbox, it can just be added to oceanbox-first.
4) Agreed - I think a simple {{{crewrank|{{{flagrank|{{{governor|}}} }}} }}} statement would do it.
5) Sounds good, I was just working on getting one pirate working first. Also, why not add capacity for more pirates while we're at it? It's a fairly simple copy-paste job.
I'll see what I can do about putting this into practice. -- Thefirstdude (t/c) 18:03, 10 April 2007 (PDT)
Sorry for the delay in response. Re. 3):Sounds good. Re. 4): Huh? Re. 5): I think three works as a god limit, as it's also the limit of pirates available on a single account. Also, I'm going to be re-naming the variables used for multiple pirates over the next week or so. There are currently 98 articles to be changed; hopefully less by the time these changes are enacted. Ocean2-1 will become pirate2-ocean1, ocean 2-2 will become pirate2-ocean2, etc... to better work with the rank variable names.--Fiddler 11:13, 18 April 2007 (PDT)
4) Never mind. 5) nope - 3 on each ocean = 21 per account. But... I would really love having up to 5 pirates...
6) I honestly don't see anything wrong with the current variable names whatsoever, and I don't see how it would work better with the rank variable names. Perhaps you could enlighten me?
Now, about those rank things, I can't see a way to only allow one of the three possible kinds of icons. I was thinking of adding to the {{ifdef}} (Usage) a third variable for what to do if it's not defined. This would make this much easier, as well as lots of other things. -- Thefirstdude (t/c) 12:43, 18 April 2007 (PDT)
Oh also, thank you SO much for adding those line breaks, it was nearly impossible to read before. -- Thefirstdude (t/c) 12:51, 18 April 2007 (PDT)
Re. 6): It reads better if everything regarding pirate 2 has pirate2- as a prefix to it. As for only allowing one rank icon, there are only 11 icons altogether (cabin person, pirate, officer, fleet officer, senior officer, captain, titled, royalty, monarch, governor, and familiar.) If a user tries to define a rank other than one of those 11 options, then it will result in an error. I don't see why it's necessary to alter {{ifdef}} (Usage).--Fiddler 12:59, 18 April 2007 (PDT)
6) Meh, true, although I can't say I think it's worth changing the hundreds of pages now (of course, you set it up so it's not necessary to change anything). As for the other thing, slightly different way of thinking about it, but makes much more sense. Oh yeah, I guess I should restart my hacking up on your new version of the infobox pirate template. -- Thefirstdude (t/c) 13:35, 18 April 2007 (PDT)
Don't bother with the complicated defaults for pirates 2 and 3, just use the new variable names. Alternately, hold off on your hacking until the number at this page reaches 0 (currently at 82.)--Fiddler 13:44, 18 April 2007 (PDT)
I've actually just been working on the pirate1 so far, and I'm happy to report it now works perfectly (see here). Copy-pasting and changing the variable names shouldn't be too hard. -- Thefirstdude (t/c) 14:07, 18 April 2007 (PDT)
All done with the transition. Set up your sandbox with clean copies of the templates so I only have to copy/paste the code into the existing templates.--Fiddler 11:10, 19 April 2007 (PDT)
Okies, will do. Also, just an observation, wouldn't it be better to call the variables pirate2-galleries and pirate3-galleries? -- Thefirstdude (t/c) 11:59, 19 April 2007 (PDT)
For the {{Infobox pirate}} (Usage) new content, go here - just copy and paste and replace as wanted. For the yoweb link pages, copy and paste from here - for all the other numbers just remove some of the template calls from the end so that there are the right number. The content for the two new pages can be found here and here. I feel confident in your ability to write up some new usage notes, as well ;) -- Thefirstdude (t/c) 12:08, 19 April 2007 (PDT)
/me Pokes - is anything going to happen with this? -- Thefirstdude (t/c) 09:18, 4 May 2007 (PDT)
I'm sorry if I seem impatient, but it's been over three weeks since I posted the comment two above. I am sure I'm not the only one who would appreciate it if someone were done about implementing this. Thanks. -- Thefirstdude (t/c) 21:38, 11 May 2007 (PDT)

Okay, I made the changes, but I'm not sure where it went wrong, so I reverted the changes. The addition of the two new pages don't seem to be referenced from anywhere, or did I misunderstand that they aren't actually new pages but changes that need to be made on existing pages. -- Cedarwings (t/c) 00:07, 12 May 2007 (PDT)

Ah wow I feel bad for neglecting this for so long. I think I wasn't quite clear enough about my instruction regarding the /yoweb/# pages. After replacing the appropriate section of the main template page with the above-linked stuff, each of the /yoweb/# pages needs to be updated. I only linked to the code for the /yoweb/7 page as the others are exactly the same, just have a different number of references to the new pages. Hope it makes more sense now :) -- Thefirstdude (t/c) 22:40, 18 May 2007 (PDT)
Aaaaaaaaahhhh... Also as I was just looking over the code in adding support to it for 6 pirates (that change happened while I was waiting for this, heh) I noticed I'd forgotten a }} at the end of the last template usage. That may have been the source of the problems, although I'm not entirely sure what happened since I came to this so late, so I may be way off. -- Thefirstdude (t/c) 22:49, 18 May 2007 (PDT)

AAAAAAAAHHHHH is right! Everything looked good until I looked at a page like Beartooth's that had multiple pirates on it and it was calling for undefinited rank icons since rank= was not listed. If pirate2-rank1=fleet officer was added it worked fine. I thought the {{Ifdef}} (Usage) template was supposed to take care of whether it was necessary, or not, to call for the rank icon if one was listed or not. I have reverted the changes I made to {{Infobox pirate}} (Usage). Have a look and see if you can see something that was missed. I have left the changes to the yoweb pages as they still work with the old version of the template. -- Cedarwings (t/c) 01:47, 19 May 2007 (PDT)

Oh bah, it's the wiki code going insane over default values. I'm going to try something out now. -- Thefirstdude (t/c) 09:09, 19 May 2007 (PDT)
OK, should be alright now. Thanks so much, sorry for missing all these stupid things :) -- Thefirstdude (t/c) 09:16, 19 May 2007 (PDT)
Woohoo! Thanks Fiddler! -- Thefirstdude (t/c) 12:36, 21 May 2007 (PDT)

Very quick suggestion... the directions don't include rank. Could someone add that? Thanks! ^_^ Sashamorning 14:14, 21 June 2007 (PDT)

Please please please please please? Something perhaps like what I requested a month ago over here? Please? -- Thefirstdude (t/c) 19:30, 21 June 2007 (PDT)
Also Could Some One Add where it links to your crew. It would really be nice if the pirate info box would list/link to the pirate's crew User:Pizzab
No. This can be done within the article itself. --Thunderbird 23:20, 15 July 2008 (UTC)

Pluralisation

First of all I'm very sorry if somebody has commented on this before - I did read the whole talk page and if anybody did then I missed it. But... I was just thinking, If the "Pets" and "Trinkets" boxes can only have one thing in them, why make them plural? Surely the Template:My Pets should have a "Pets" button (which I don't think it does) and the infobox should just say something like "Favorite Pet." I can't remember whether the trinkets box is the same - I have never used it, only seen it used. Does the copyright on the YPP interface prevent you from changing the text on the button? If not, it wouldn't be vey difficult to change... just a thought --Smc508 22:30, 3 January 2007 (PST)

I don't think any of us have thought of that before. Good idea! Nice and simple, I like it.--Fiddler 22:42, 3 January 2007 (PST)
Heartily agree etc, etc... That's bugged me for a while that the "title" was plural while only displaying a single of each item. I just hadn't given it enough thought to come up with a solution. A simple change in the button text to something more...singular, sounds like it would do it. --Muffynz 00:07, 13 January 2007 (PST)

Portrait link

Hello. I am curious as to why the link to the portrait image uses the Page name, and not the piratename, for the link. This is rather annoying for me, especially as I was making the Basic pirate template, as it prevents my usage example from working correctly. If you're left wondering, this template is mainly for my uses, as actually writing out all of that stuff over and over again, nearly-identically, for dozens of pirates, who I can guarantee will never come and want to edit their pages, gets extremely tedious. Thanks! --Thefirstdude 6:40, 1 February 2007

"I am curious as to why the link to the portrait image uses the Page name, and not the piratename," Because Millie (Midnight) and Millie (Viridian) are about different pirates, but have the same pirate name. By using the page name each article can have a separate image. "actually writing out all of that stuff over and over again, nearly-identically, for dozens of pirates, who I can guarantee will never come and want to edit their pages" Copying and pasting from a previous effort would only involve you typing out three more words than using this new template. In addition, should anyone else wish to expand that page, or to include additional information, they will need to convert from your template to the standard infobox template.
If you really want to save yourself the trouble, use {{subst:Basic pirate| when filling out pages. When you save the article it will leave behind the actual code involved in showing the page and not just the template call. In this case that means that the opening sentence and the {{Infobox pirate| will be fully included and editable.--Fiddler 07:48, 1 February 2007 (PST)
And yet again I'm left feeling stupid. Thank you so much. Sorry for continuing to cause trouble. :( --Thefirstdude 7:37, 1 February 2007

Limit of 3 pirate names

It looks like the template only allows three pirate names, is this correct? There are some people who have more than 3 pirate names so it may be an idea to extend this a bit, to 6 maybe? -- Vorky 04:21, 26 April 2007 (PDT)

This is correct - I mentioned it in the above lengthy discussion somewhere. There are several points to consider in this regard, however: each account can have three pirates per ocean, usually at most two of which are actively used; all the semi-redundant linking code in the template looks ugly enough already (yes, blame my computer science teacher for my obsession with code cleanliness); and finally, each pirate can have a Yoweb link for up to 7 oceans - 21 Yoweb links is already too much. Although, it is true that people who want more than 3 pirates will seldom have each of them on more than a few oceans. In short, I'm rather undecided on this. Perhaps there should be a separate, similar template called something like "Infobox pirate multiple", something like there is for flags with many blockades; it would have capacity for, say, 9 pirates, but only up to two oceans for each (the pirate-name-header takes up as much, if not more, space than a Yoweb link box). In short, I think capacity for the current 21 Yoweb links is about the limit - what do you think? -- Thefirstdude (t/c) 05:51, 26 April 2007 (PDT)
I was just trying to fix Poowin so a fourth showed up when I realized the template was limited. I think adding a few more, like 6 as Vorky suggests would be useful. It's pretty rare that people have a zillion different names because they tend to like to "protect" their names on other oceans. --Guppymomma 08:26, 29 April 2007 (PDT)
Although I agree that very few people will want 6 pirates on 7 oceans each - probably 6 pirates with 3 oceans each is a stretch - I tried a mock-up with the first three pirates capable of 7 oceans and the last 3 only two. Extended example can be seen here. Although I agree the chances of someone actually doing that are very low, I think it makes my point; however, just to take it a bit further, I made a slightly more realistic example here. It still does not entirely fit on my screen. In my opinion, when the infobox stuff on the right side extends beyond about 90% of my Firefox window, it is very obnoxious. Don't get me wrong - I think more pirates is a great idea - I'm just a bit concerned with it becoming incredibly long to the point of eyesore. -- Thefirstdude (t/c) 10:25, 29 April 2007 (PDT)
6 pirates with the current infobox scheme seems reasonable but if there's problems, I'll revert the template back. With the new infobox scheme, I agree with Thefirstdude that it could get excessively long with too many pirate names but then something would have to be figured out for alts which would otherwise have very short stub articles. There already are pirate articles which put a little too much information into the infoboxes via the custom field. -- Faulkston 10:40, 29 April 2007 (PDT)

Rendering fix - suggestion

There is a bug in the template subpages that causes the infobox to render poorly in Firefox and Opera. While they aren't currently protected and I could add the change myself, I just finished teaching myself enough CSS to figure this out, and I know the pages are protected in spirit. So, here's my proposed fix: add "clear: both;" to the top <DIV> of Template:Infobox_pirate/yoweb/oceanbox. For good measure, might want to add it to oceanbox-first as well. Alternatively you could use the {{clear}} template, but it seemed more appropriate to just throw in the raw CSS here. My work can be found in my sandbox at User:Chupchup/Sandbox/Infobox_pirate/yoweb/oceanbox. Chupchup 20:53, 14 July 2007 (PDT)

I'm not entirely clear on what is being poorly rendered. Could you perhaps explain it better, or perhaps provide a screenshot?--Fiddler 21:53, 14 July 2007 (PDT)
Okay, it's like the difference between a LF and a CR/LF in a text file - or, like a Wiki talk page, when people put enough :::: colon indentations when replying in a thread. It's most noticeable if you use Firefox or Opera to directly visit a subpage like Template:Infobox_pirate/yoweb/3. When multiple oceans are displayed using yoweb/2, yoweb/3 and so forth, the subsequent {{{oceanN}}} link (or the rank icon, if it exists) begins not flush with the left margin of the box, but beneath the end of the previous {{{ocean}}} link. This is how it behaves in Firefox; Opera apparently does something different. The cause appears to be persistent "float:" or "position:" properties retained from the oceanbox above it, causing the left-justified floaters to flow diagonally, rather than start a new "table row" as they should. The "clear" property (which is the entirety of the Wiki template {{clear}}) seems to be just what the doctor ordered. On closer inspection, we may be able to get away with "clear: left;" but, this is something I didn't test. Chupchup 00:16, 15 July 2007 (PDT)
I understand what you are saying, but I have not noticed any visual problems with it since I created the new stuff (oceanbox and rank icons) back in April. This includes the problem[s] you are describing. It looks perfect to me when I view yoweb/N directly and when it's used on a pirate page. This is in both FF 2.0.0.4 and IE 7. It's been a while since I used FF 1.5, but I'm pretty sure it looked fine in that too. -- Thefirstdude (t/c) 06:26, 15 July 2007 (PDT)
I don't see the visual rendering problem either. I'm using Firefox and Internet Exploder as well. As Fiddler requested, a screenshot of a pirate page with the rendering issue would be helpful. Along with information on what version of Firefox & what OS you are running. --Guppymomma 07:11, 15 July 2007 (PDT)
I just tried it with the latest (9.2.1) version of Opera, and I don't see any rendering issues there, either. -- Thefirstdude (t/c) 08:42, 15 July 2007 (PDT)
It has to do with larger font sizes. Try rolling the text size up until it breaks. I have some before-and-after screenshots here. My User-Agent is Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.4) Gecko/20070508 Iceweasel/2.0.0.4 (Debian-2.0.0.4-0etch1) -- Chupchup 17:29, 15 July 2007 (PDT)
Ah. Now I know what you're talking about. I fail to see why anyone would want to use such a large font size as to break it, but anyway, I tried it out with your version, and as I predicted, it's much, much more broken than the current version. It doesn't display anywhere near properly even at a normal font size, to say nothing at all about larger ones. I'm not sure what the problem is as I haven't delved into your code, but messing with clears like you say you did very, very often leads to unwanted breakage in surprising places. Please see screenies here. -- Thefirstdude (t/c) 01:19, 16 July 2007 (PDT)
Well, at the time you took those screenies, I was still randomly flailing at the code, trying all sorts of things to see what they would do. Sorry I've created quite a large volume of recent edits, but there's no need to get defensive about your code, because I'm fairly convinced now that the constraints of WikiCode won't lend a solution here, nor is it worth obsessing over correct formatting of someone else's infobox while I try to teach myself this stuff. -- Chupchup 02:49, 16 July 2007 (PDT)
I'm sorry you feel I'm being defensive. I agreed there was a problem - I disagreed it was severe enough a problem to warrant head-banging over its fix.
I'm not sure how you want to fix the problem and how this is being constrained by Wikimarkup. Any CSS will work just the same here as it does anywhere else.
I'm not sure what you mean by "obsessing over correct formatting." You may want to take a look at Template:Infobox pirate/yoweb/7 before my changes for an idea of what I had to wrangle with.
Finally, with most template projects, vast numbers of small edits are to be expected.
 :) -- Thefirstdude (t/c) 09:23, 16 July 2007 (PDT)

Multiple pets?

Is there any reason why we could not include multiple pets? I have my 3 children as tigers and would like to include all 3 on my personal page.... btw thank you for making this template as amazing as it is already.

Wrong filename in template usage example

The usage specifies that the image Portraits-Piratename.jpg is used. As it really uses Pirates-Piratename.jpg, the documentation should be fixed. Guess there are a few Portrait-Piratename.jpg's around because of this (at least the one i uploaded first Image:Portraits-Straydog.jpg, if anyone with access fixes, please delete it).

Fixed, thanks! --Nicksterv (t/c) 06:35, 19 December 2007 (PST)

Rank Field

Can someone update the usage notes to include the rank field? I'm awful with the code like that, so it'll take me about... a year to do it properly. Thanks! --Fannon 11:46, 10 January 2008 (PST)

I just dont know what type of rank box yer talking about, the type that I have used is on the page called Instantflash, and also here is the format I used inside the infobox: |custom={{Rank box|title=x|crewtitle=y}} (x=Flag Title, Member, Lord or Monarch, y=Crew title, as in, First Mate, Sailmaster, etc. --Instantflash 16:57, 15 January 2008 (PST)
This was about the rank field in the infobox and not about a rank box. This was dealt with already, I just forgot to leave a message that I took care of it. -- Cedarwings (talk) 17:59, 15 January 2008 (PST)

Trinket labels

Is is possible to allow adding the trinket label to this like with Template:My trinkets? It would be even better if it was in the tooltip, but that may be impossible with the current setup. --Silverspoon 22:53, 10 February 2008 (PST)

Counter

I just noticed the article counter is still active...is this intentional? --Thunderbird 21:36, 20 February 2008 (PST)

passing of 3rd color argument

To enable three color trinkets for this infobox I'd like some admin to pass trinketcolor3 on as tertiary (and change the usage accordingly), thanks:

{{Infobox pirate/trinket/{{{trinket|no}}}|trinket={{{trinkettype|}}}|primary={{{trinketcolor1|}}}|secondary={{{trinketcolor2|}}}|tertiary={{{trinketcolor3|}}}}}

--Alfwyn 06:05, 8 March 2008 (PST)

Added. Ugh things are laggy today! --Guppymomma 07:43, 8 March 2008 (PST)

Familiars

If someone could add two more familiar templates (11&12). There is a pirate (Urgghh) that has obtained 12 familiars. Thanks --Instantflash 17:56, 15 March 2008 (PDT)

There are pirates that have a lot more then that. The number has been capped at 10 and will not be increased. Have a look at Jaed's page as an example of what happens when you change the number above 10. -- Cedarwings (talk) 18:07, 15 March 2008 (PDT)

We may want some guidelines for what counts as "winning" a familiar. I see pages describing pirates who have purchased familiars in auctions as winning them. I'm okay with that for Pirates who won familiars in official Ringer auctions, since those are the original events that spawned the familiars (and in some cases a more in depth competition than a standard auction). But I'd think that familiars purchased privately should only be listed under familiars owned.

In other words, there should be exactly one place where any familiar could be listed as "won" in the wiki, the winner of the event for which it was created. Drc500free 06:42, 23 June 2008 (PDT)

In other words, there should be exactly one place where any familiar could be listed as "won" in the wiki, the winner of the event for which it was created.
That is the policy as it's been understood and enforced for quite some time. I've had quite strong arguments with people trying to claim familiars that were purchased privately as won. Unfortunately, the proliferation of pirate articles since the policy change two years ago has made review of details such as who initially won a familiar all but impossible. The link from the ocean name in the familiar box to the ocean's list of familiars is a small step at enforcing some honesty and accuracy when listing won familiars. --Fiddler 14:29, 23 June 2008 (PDT)
Fair enough. So it would be valid to edit a page that lists both that a series of familiars were purchased and that they were won? --Drc500free 07:23, 24 June 2008 (PDT)

Would Serpents or Ippolitos awarded from CI's and SMH's booty division count as a familiar won or just a familiar owned? --Interguy1 04:34, 17 April 2010 (UTC)

They would count as familiars won. -- Cedarwings (talk) 15:13, 17 April 2010 (UTC)

Multiple Trinkets

Similar to the multiple pets suggestion, could we somehow have multiple trinkets? I know I, for one, have more than one trinket that I'm proud of. --Jlh0605 19:43, 1 October 2008 (UTC)

I don't think the multiple pets suggestion was actually implemented, and I don't think this should be put in the infobox either. There's the possibility of people wanting to list all of their trinkets in this fashion, which would just be unwieldy. There's always the placing of multiple trinkets in the article itself (using a show/hide box if needed). --Thunderbird 23:43, 1 October 2008 (UTC)
The multiple pets were implemented using the "custom" parameter in the template. There has been no "official" implementation of multiple pets in the template. -- Cedarwings (talk) 05:45, 2 October 2008 (UTC)

urlencoding piratenames

Currently the names of the brigand kings appear with plusses instead of spaces in order to prevent breaking the resulting url part (see Brynhild Skullsplitter for example). This workaround would be unnecessary, if the name would be encoded with the urlencode magicword inside the template.

The encoding could be done at different places in the template cluster. One possibility would be to do it in Template:Infobox pirate/yoweb/oceanbox-first and Template:Infobox pirate/yoweb/oceanbox, I have sandboxed this approach at User:Alfwyn/Sandbox.

Another possibility would be to defer some of the encoding to Template:Extnavimg, since this template may profit from having it's link argument properly encoded anyway. The two aforementioned templates would need to be modified with that approach too.

--Alfwyn 20:21, 11 November 2008 (UTC)

Pirate Portrait

I recently issued a solo portrait on my pirate. I now have two ie. my free one and the one I bought. I have set it so that on my in-game pirate page my new (and cooler) portait appears, but I cannot seem to make this happen on my YPPedia page. Anyone who knows how to fix this please let me know.

My YPPedia Page

My In-Game Page

Thanks, Raggedjoe of Viridian

Basically you need to re-upload your new portrait over the top of the old one (that is, go to the location of the old portrait, and click "upload a new version"}. Then press "refresh", as images get cached in the server. --Belthazar451 12:28, 25 February 2009 (UTC)
I appear to be an epic fail, because I cannot manage top do this. My browser rejects the file upload. Is it possible you can do it for me?--Raggedjoe 17:14, 25 February 2009 (UTC)

Infobox pirate and capitalization control

According to a discussion at User:Amoyer/Templates/Capitalization/Infobox pirate, all piratenames should have had their first letter capitalized, but the lowercase before that dropped. For some reason that change was never actually implemented. Is there something you can think of that would break by surrounding piratenames by a {{ucfirst: }} ? --Alfwyn 16:00, 4 July 2009 (UTC)

Vargas the Mad. Brynhild Skullsplitter. Barnabas the Pale. The Widow Queen. Et cetera. The original idea seems to have bean to leave pirate2 unmodified so that the German names were left unaffected, but that doesn't seem to have turned out in practice. In addition, now we have Spanish. And what happens when we add French, say? Far better, I think, to manually correct the few pirates who try to be difficult about things than to break the ones that SHOULD have a capital in the middle. --Belthazar451 00:03, 5 July 2009 (UTC)
Could always add a BK parameter to the template that would bypass the capitalization control, along the lines of what we did for the ultlist template. Thoughts on that? I really like the capitalization control. -- Cedarwings (talk) 01:55, 5 July 2009 (UTC)
Well, the idea was to use {{ucfirst: }} in all cases (instead of {{ucfirst:{{lc: }}}}). That just capitalizes the first letter and leaves the rest alone. This catches the most common mistake without breaking anything I know. --Alfwyn 13:37, 5 July 2009 (UTC)
By making a little modification to User:Amoyer/Templates/Capitalization/Infobox pirate to now include a BK parameter, you can see the results here. If a BK=yes parameter is added, then the piratename will appear as typed. We can apply this change to the piratename, pirate2 and pirate3 or for that matter all instances where the name appears to solve this problem. I would really prefer to see capitalization control back in place. I still find numerous instances where people aren't capitalizing ocean names, pet items (types, colors) and pirate names correctly. -- Cedarwings (talk) 15:44, 5 July 2009 (UTC)
You're really getting the hang of this #ifeq thing, aren't you? =) But yeah, I agree that it works like that. If I can make one sort-of-related suggestion, though, it might be an idea to capitalise the sample code as things should be capitalised. So for example, instead of reading |piratename=piratename, it should read |piratename=Piratename. --Belthazar451 23:04, 5 July 2009 (UTC)

(undent)Changes have been implemented. -- Cedarwings (talk) 01:21, 6 July 2009 (UTC)

Reducing sub-templates

I'm not sure people dislike sub-templates as much as I do, but how much is it worth trying to remove them from the infoboxes? I see a little more logic to it when we're looking at an endless series of numbered sub-templates, but we can also do away with yes/no sub-templates at the expense of slightly more complicated code. For example, we can do away with the portrait yes/no subtemplates by replacing the line

{{Infobox pirate/portrait/{{{portrait|no}}}|piratename={{{altname|{{PAGENAME}}}}}}}

with

<div style="border:1px solid gray; margin-bottom:3px; background:white;">{{#ifeq {{{portrait|no}}} | yes | [[Image:Pirates-{{{altname|{{PAGENAME}}}}}.jpg|{{{altname|{{PAGENAME}}}}} | [[Image:portraitempty.png|{{{altname|{{PAGENAME}}}}} has no portrait]]]]</div>

For numbered sub-templates, the main culprit here in the pirate infobox is the familiars. We can easily do away with all the templates numbered 11 and above by inserting the line

{{#ifexpr {{{familiars}}}>10 | <font size="+{{#expr ({{{familiars}}}/10)-1}}">{{{familiars}}}!</font>}}

... somewhere. Might have to shift some of the table code out of the sub-templates to make it work properly as well. Not sure if it's really worth it, or if I'm just blabbering, though. --Belthazar451 12:26, 23 August 2009 (UTC)

I don't think it is worth changing the yes/no code of existing templates. The subtemplate method has the advantage that it reacts better to misspelling (e.g. it displays a red link, instead to defaulting silently to not-yes). Cutting down on the familiar sub-templates on the other hand would be a good idea I guess. Currently we have to create new ones (or at least a new redirect) everytime someone hits a number we don't have a sub-template for. --Alfwyn 12:49, 23 August 2009 (UTC)
I just put my nose to the grindstone for a little bit and managed to come up with a solution to the subtemplate issue. Whee! (Well, the familiar one, at least) --Thunderbird 19:34, 14 March 2012 (PDT)

Why did this template become impossible to display the OM doll in "trinket" field?

After a update at 18:37, 19 June 2010 by Belthazar451 (Force trinket colours to be lower-case), this template seems that became impossible to show the OM doll. So I've thought we users need "custom" field if we want to set OM doll on infobox. If so, would you please add "How to display OM doll in infobox" into Usage? (Or should not I display OM doll?)--Piripuwa 06:27, 20 June 2010 (UTC)

Belthazar changed it to force all colors to be lowercase, since that's how they all work. The OM doll part is an exception, which I fixed for this by editing the part that references them. --Thunderbird 06:54, 20 June 2010 (UTC)
Ah, me stoopid. I knew there was a reason it wasn't auto-lower-case. Completely forgot about the OM doll. --Belthazar451 11:40, 20 June 2010 (UTC)
Yup, we looked at doing a lot of things when we first started looking at forcing capitalization in a number of place but came to the conclusion that trinkets names just were not worth it and so it was abandoned. This will probably mean that some of the event trinkets will not work either. -- Cedarwings (talk) 05:08, 21 June 2010 (UTC)
Aye, Alfwyn already fixed most of them - he missed the Sea Battle trinket, which I've now done. I only changed the trinket colours, incidentally - there's too many proper nouns in the trinket names to try any sort of case-forcing there. And on that note, the "Baby portrait of Adm. Finius" template name is written different - doesn't anyone find that confusiong? --Belthazar451 06:02, 21 June 2010 (UTC)

Making more than 21 familiars automatically default to 21

If we put {{#ifexpr: {{{familiars|0}}} <= 21 |{{{familiars|0}}}|21}} in place of {{{familiars|0}}} - then we hopefully wouldn't need to create redirects to the 21 familiar subtemplate, the main template would automatically use it if there are more than 21 familiars. --Sagacious (talk) 02:02, 18 July 2010 (UTC)

You could even make the 11 familiar template cover the function of the 21 familiar template by using
{{#ifexpr: {{{number|0}}} >= 21 |<font size="+1">{{{number}}}!</font>|{{{number}}}!}}
That would mean changing my above suggestion to:
{{#ifexpr: {{{familiars|0}}} <= 10 |{{{familiars|0}}}|11}}

--Sagacious (talk) 02:14, 18 July 2010 (UTC)

I realised we scale to larger font for the number using other templates. My sandbox has example results, but a tweak to my suggestion for the 11 familiar template so the font gets larger with more familiars:
{{#ifexpr: {{{number|0}}} >= 21 |<font size="+{{#expr: (({{{number|0}}} - 20) / 20) round 0}}">{{{number}}}!</font>|{{{number}}}}}
I picked 20 because it seems to be roughly the right number that scales the font size well. Font size increase seems to be capped at 5.
Yeah it looks complicated - but has to be better than 88+ subtemplates. --Sagacious (talk) 02:53, 18 July 2010 (UTC)

Adding ocean categories automatically

Is it possible to tweak this template, or rather, one of its children, so that it adds e.g. Category:Cerulean Ocean pirates automatically based on the oceanN parameters? It seems redundant to keep adding those templates to the bottom of the page and keep them in sync with the infobox. Chupchup 23:22, 11 May 2012 (PDT)

This template is in use on Ringer pirate pages, which don't have the ocean categories. It's also in use on a handful of user pages, though an auto-category can be made to not work on user pages (the Oceans template was already made to not work on user pages some time ago). --Thunderbird 23:28, 11 May 2012 (PDT)

Multiple portraits (portraits for alts)

Is it policy to only have one pirate portrait per page, or are alt portraits allowed too?

I ask because I can hackily add multiple portraits by adding multiple instances of infobox pirate to a page (by substing subsequent infoboxes, as with Topgunner). This means alts can get their own portraits. It would be nice to have a pirate1-portrait=yes syntax, so I can include some old alt images into pirate pages (otherwise they'd be deleted) without using the hacky subst solution. I am thinking of adding this functionality to the template.

Please would you tell me if I should not be doing this! Cheers. --Therobotdude 18:28, 15 August 2015 (PDT)

Powered by MediaWiki
Attribution

Puzzle Pirates™ © 2001-2016 Grey Havens, LLC All Rights Reserved.   Terms · Privacy · Affiliates