FANDOM

A FANDOM user
  Loading editor
  • https://www.mediawiki.org/wiki/Extension:Variables has now been activated for the wiki, in case you were interested!

    Also /wave back, as I was running round Windurst Walls like a maniac trying to hoard shards of sunlight last night, so apologies for my bad manners. :)

      Loading editor
    • View all 5 replies
    • (Loops and Arrays were also added, btw)

        Loading editor
    • Ooo... Loops are a bigger deal than variables. It means you can use infinite generic parameters (e.g. {{{1}}}), which means no more repeated "quest 1, quest 2, quest 3..." only to find out you need one more for this one item. I'll definitely be refining a few templates when I find the time (I've been swamped lately).

        Loading editor
    • A FANDOM user
        Loading editor
  • Did you get this e-mail?

    "Hello from FANDOM,

    On May 25th, 2018 the General Data Protection Regulation (GDPR), a new European data protection regulation, will go into effect. Unfortunately, in order to comply with this regulation, we will remove the Monobook skin from our network as it is not possible to bring it into compliance.

    We understand that this is a drastic step and is an inconvenience for you and your community but we must be in compliance with this new regulation. For more information about the GDPR, please see https://www.eugdpr.org/gdpr-faqs.html"

      Loading editor
    • Yeah, I saw... I'm super bummed about it, both because I really don't like the Oasis skin and because I've been doing so much work to support both layouts recently. I'm not sure why Monobook is even an issue, either. I'm familiar with the new law and I don't see why a skin would cause issues (it's all about requiring sites to make user data portable and erasable, which has very little to do with the front-end).

      I was hoping to create a Monobook-like replacement skin - I'm really not a fan of the Wikia/Oasis skin for this site - but it looks like having multiple Wikia-style skins is no longer an option.

        Loading editor
    • I read through all of their forum posts on Community Central, as it seems there was a demand for clarification on this, and it sounds like Monobook collects user data in a certain way which may not be compliant. In order to prevent ambiguity, and because they don't have the resources to allocate to making the necessary modifications, they've decided to kill it altogether.

      One thing is that it sounds like this was met with significant resistance within the FANDOM organisation, as they have said the late-notification of the issue was because it went 'down to the wire' as to whether it would be kept.

      Currently, I'm using a global.css to hide the wikia rails to avoid all of that Fandom trash. I kept them up for ages because I wanted to be exposed to the same experience most users are, but then I started seeing spoilers on article titles within a day of ST:Discovery episodes being broadcast, so they had to go!

      Anyway, here's to hoping the feedback they're receiving currently will go some way to providing a better/alternative to Oasis.

        Loading editor
    • My current solution: Monoasis

      I'm still hoping for an option to add another skin where we could have free reign to do what we want, but user styles will have to hold me over in the mean time.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hiya Karu!

    I want to create a tooltip popup for the Monster Rearing page, wherein if you hover over the Feed type in each Monster section (under Evolutions) you get a tooltip popup of the list of items that Feed consists.

    I've used labelled sections to label up the Feed lists at the top of the page, then used this code to create the tooltip:

    {| class=ffxi-table width=60%
    ! align=left | Feed:
    | {{Tooltip|id=Fruits|text=Fruits|tooltip={{#lst:Monster Rearing|Fruits}}|width=300px}}
    |}
    

    Gives:

    Feed: Fruits

    That seems to work fine, but when I add a second type in and separate them with BR, the second type is included in the first tooltip instead of a second mouseover appearing below, and I can't work out for the life of me why!!

    {| class=ffxi-table width=60%
    ! align=left | Feed:
    | {{Tooltip|id=Fruits|text=Fruits|tooltip={{#lst:Monster Rearing|Fruits}}|width=300px}}<br>{{Tooltip|id=Meats|text=Meats|tooltip={{#lst:Monster Rearing|Meats}}|width=300px}}
    |}
    

    Gives:

    Feed: Fruits
    Meats

    Any ideas at all?

      Loading editor
    • Weird, posting that code here seems to give both text 'Fruits' and 'Meats' and their tooltips, though for some reason the 'Meats' tooltip is missing the bullet points.

      In my sandbox, the same bottom code only gives 'Fruits' and puts the 'Meats' within the 'Fruits' tooltip, see here: User:Haldarn/Monster Rearing

        Loading editor
    • Fixed. It was because the tooltip was a span instead of a div, so things like tables and lists wouldn't work properly inside it (spans are meant for inline content, not blocks). This could have been fixed without changing the template by wrapping the offending tooltip content in a div, but I realized that there was no reason for the template to use a span in the first place, so I just went ahead and changed the template. Keep an eye out for any side effects of that, though.

        Loading editor
    • Amazing, thanks so much! :)

        Loading editor
    • A FANDOM user
        Loading editor
  • Hello, it's me again, bugging you about something else. And how was your day? I tracked down what seems to be a Fishing Template formatting error to this update (http://ffxiclopedia.wikia.com/wiki/Bastore_Sardine?diff=prev&oldid=1573556) done by Karubot on May 28, 2017. I chose this example because it uses the current fishing template, though it seems to have happened to every fish I've checked. If you'll notice, the asterisk in front of every line item moved to the left one space into the adjacent column, with the far left Location column ones gone altogether. This is what the template displayed at the previous edit (http://ffxiclopedia.wikia.com/wiki/Bastore_Sardine?diff=prev&oldid=1562913). The legend at the bottom also appears to be missing, unless that only appears if one of the legend items is referenced. It should still appear, though.

    Thanks for your efforts in the stuff you do.

      Loading editor
    • Whoops. Thanks for pointing that out. It should be fixed soon, if it isn't already. It was due to a mistake that I made when I adjusted the "ffxi-table" class the other day.

      The legend was missing there because the {{Fishing}} template wasn't being used, but I've fixed that now as well.

      Thanks for bringing this to my attention!

        Loading editor
    • A FANDOM user
        Loading editor
  • No input necessary, just wanted to show something!

    I've designed a table and appropriate templates for eg, weapon category pages.

    User:Haldarn/Axes

    The first 40 examples have been checked and formatted, the rest of the page is a mess that I'm updating article-by-article.

    This uses #dpl to pull the damage and delay out of the Item Statistics template and then runs a calculation on them to create base dps.

    I've also used #dpl to pull the item image filename out of the article's {{Item Image}}, which I think basically means that #lst is now obsolete? Rather than continue to manually add in missing labelled sections, I'm going to strip that out of as much referential code as I can now and go straight to the template. As far as I understand it from the #dpl manual, there is no extra processing overhead to directed #dpl like this in comparison to #lst (#dpl is only an processing issue when it involves collating data from across the entire wiki, like WhatLinksHere if I understand it right)

    Dammit I wish I'd understood this better a couple of months ago!

    Finally, one weird behaviour I noted was that sorting the table by Name resulted in articles that had an apostrophe within their title somewhere appearing out of order at the top... odd. Fixed by using PAGENAME: encoding in the template for a data-sort-order= property... in case you ever run into something similar!

      Loading editor
    • Yep, it turns out Labeled Section Transclusion is just a safer, narrower version of Dynamic Page Lists, so we really don't have too much use for LST. I was under the impression that LST is more efficient than DPL, but it seems they're pretty much the same when used the same way. Oh well. At least that makes things cleaner going forward.

      As a side note, make sure to protect any templates that use DPL, especially if they'll be widely used - we really don't need someone who doesn't know what they're doing tinkering with DPL in a template.

        Loading editor
    • Understood, shall do from now on.

        Loading editor
    • A FANDOM user
        Loading editor
  • User:Helios314 highlighted that changes to the {{Abundance}} has meant that any pages that call the template without parameters generate a messy string of broken formatting code. I've fixed the Chocobo Digging and Treasure Casket pages they mentioned, but no idea if they occur elsewhere.

    Separately, but related, now anything that calls {{Abundance}} with 0|0 parameters results in 0%Unknown(0%), for which we get the expression's 'Divide by zero' error, which can screw up formatting on pages that have limited space for the Abundance result. I had a quick look, but am pretty confident you'll understand better than I where exactly an IF statement belongs that'll prevent that from appearing at all.

      Loading editor
  • This was a project I've been meaning to do for a while, so I finally knuckled down for a couple of nights last week with a lot of tea and got on with it.

    I've uploaded *all* of the item icons in the game at the moment with the format #####.png (inc. transparency), as you'd expect.

    To complement this, and the work we've done with section Item Image, I've created Category:Item Index. This lists all Item articles, in alphabetical order, whether we have them on the site yet or not. It displays their:

    • Icon ID - which btw can also be used for ffxiah.com direct links, rather than relying on text-matching. I'm currently using this as the reference when updating icon ids into {{Item Statistics}}.
    • Icon - this was mainly so I could double-check that they were all uploaded, but also to give a home to the majority of the images that would otherwise currently be orphans.
    • Article name - removing all of the abbreviations from the game's inventory name to FFXIclopedia's article naming convention was a huge job (about 10% of all items), and I'm glad it's done. There will be a minute amount of mistakes for fringe cases, which I am correcting as I review, simultaneously updating my source spreadsheet.
    • Item Image - pulled in with our favourite #lst. It enables us to at a glance see if these images are outdated, badly cropped, missing (redlink) or without the lst formatting (blanks). I think there's at least one other editor that will appreciate this!

    So, further to my previous post below regards {{I}} and {{In}}, I've added all of the icon ids for Articles appearing on the Expert Recipes page manually (as well as a smattering of newer articles I've added, or old ones I've updated ove rthe last couple of months). Would it be possible to bot the rest in? I have a spreadsheet that lists Item ID (icon id) versus Article Name (as per the index, so I reckon 99% correct).

    edit: I meant to ask, with regards Category:Item Index, I created {{NavItemIndex}}, which I'm almost happy with. The only issue I have with it is that whichever page you visit with it on, it defaults to the first tab rather than the tab with the open page on as you'd expect. I had a look through tabber's info, but I couldn't find any mention of being able to set the default tab to something other than the first. Any ideas, or alternatives you can think of? It's not a huge issue, as the category is really a page for editors and not for regular users.

      Loading editor
    • Wow, that's a huge undertaking. Impressive.

      I definitely appreciate the ability to look for missing/bad item images and missing item pages.

      I can add those item ids by using a spreadsheet and a plugin for AWB - it's something I haven't used before, but it looks simple enough. I think I'll change the "icon id" option to "item id" in {{Item Statistics}}, since they're the same. I initially envisioned reusing icons as much as possible (thus a separate "icon id"), but I can understand why you didn't choose to do it that way. Hmm... Do redirects work with files? I wonder if we could reduce duplicates by having the higher numbered item icons redirect to the lowest numbered version...

      Also, what do you think about moving Category:Item Index to a regular page (possibly in the FFXIclopedia namespace) and having the ranges as subpages? It's pretty low priority, but it might be a little better structured that way.

      Regarding {{NavItemIndex}}: I poked around in Tabber's source code and it looks like the only way to specify which tab is open is to link to an anchor/id, like this: [[Sam - Sao#S|Sam - Sao]] (Sam - Sao).

        Loading editor
    • Hah. And there was me putting it in the FFXIclopedia namespace to begin with (it was just a two-column table of names vs numbers). I had to divvy it up for loadspeed when I extended its function - there's 100-200 lines in each page's table now. Then, with those 200 separate pages, I thought they should all have a category, lest they be without category, which I understood was a wiki no-no. And hence the base page at Category:Item Index was born.

      Subpages seems like the better option though, as now any of those pages come up in Search - a side-effect I hadn't anticipated.

      I've been using "icon id" in {{Item Statistics}}, no probs. Do you think there's another use for that info inside that template that means renaming it would be appropriate? Making the AH link part of it..? (I know you've said before that you prefer it lower down the page!) Or are you thinking wider DPL functions that don't have to rely on Article/Item names?

      As for duplicate icon images, I think they're a necessary evil - it has happened before that S-E have replaced a standard repeated icon with different ones. Granted, at this point in the game, it seems unlikely, but they may do something eg putting number on Storage Slip icons. We're set up to deal with that with a simple re-upload and no code changes. Also, at less than 1KB each, even all 21k of them only take up 28MB, so I can't see duplication causing any issues?

      Thanks for solving my {{NavItemIndex}} issue for me; seems like that'd be the perfect solution, which I'll implement shortly!

        Loading editor
    • Yep, I've been coming around to the idea of having the AH and DB links in the statistics section (possibly still having the AH link in How to Obtain, though). I've also been toying with the idea of including more technical information on the wiki, which item ids would be a part of. (Other things would be model .DAT files and the like. I don't know if that's a bad road to start down, though.) If I were to change it, I'd either make icon id an override for icons or just bot uses of "icon id" to "item id", so no manual changes either way.

      The icon images suggestion is just me over-optimizing - old habits die hard. Using redirects (which do work, it turns out) would only serve to reduce file size and get rid of the duplicate file warnings on the file pages. You could, however, still replace the redirect with a new file if they ever changed the icon, though it might require deleting the page... But yeah, not needed and more effort than it's worth.

        Loading editor
    • A FANDOM user
        Loading editor
  • Well this was a nice surprise. Something I'd been trying to do for a year or so suddenly fell into place after Desz got me thinking and also because Tooltips now work in a certain way (or I just realised they could be used that way).

    Turns out it was very easy and elegant code!

    So I finally picked up my crafting tools to bring my Clothcraft back up to cap, and create the necessary pages to do so. In making Category:Clothcraft/Expert, I've made a couple of new templates:

    • {{I}}: 'I' for 'Iconned Item' or somesuch. I wanted to keep the title brief, as I envisage it being used often in summary lists.
    • {{In}}: 'In' for 'Inline Iconned Item'. Again, a brief title.

    {{I}} uses #dpl to automatically apply the 32x32 icon infront of an Item Article link, as long as the icon id is declared in {{Item Statistics}}. It then uses #lst to create a mouseover tootlip of the Item Image section (it could use #dpl instead if the Item Image was within {{Item Statistics}}, but I gather we've just spent the last couple of years moving the Item Image outside of that template! It would work either way.

    {{In}} does the same, but with a 16x16 icon, and hence is useful for when items are in sub-lists (like recipe ingredient lists).

    I think I'm going to add a |noicon parameter, so that the templates can be used for the mouseover tooltip without the icon if needs be. Any other comments or observations would be appreciated. Not sure if it would be appropriate or even possible to roll this out site-wide via automation.

      Loading editor
    • View all 7 replies
    • I think you're on the right track with the gradient backgrounds - I'd prefer to limit the number of CSS color backgrounds we implement, so using table backgrounds for more diverse color coding is an appealing idea.

      Another idea is to use standard cell backgrounds for the body of the table, but color-code the headers - it's something that was done on the recipe pages, but isn't terribly effective there.

      I like all of those examples, but the Red Mage table is the least palatable to me - I think it's because it's not as gradual/subtle of a change. I also don't like the missing cells - I'm assuming you don't like the look of empty cells, so maybe use gray cells and put an em dash (—) or en dash (–) in them?

      Just some constructive criticism, though - it's looking good!

        Loading editor
    • Yeah the Red Mage tables were me seeing if a triple-change on the gradient looked good, but I agree - it's not subtle and hence impacts on the readability of the information. I've changed it to two shades of the original pink header.

      I felt that empty cells were unnecessary, as it's additional code for no data. I've added them into those tables for now, so I can get a feel for how they look over a few weeks whilst I use the page.

      I think my rationale there is that data tables are created with each row (record) having a column (field), whether that be zero-value or not. In these cases, blank cells or cells with '-' in them are suited.

      However, when tables are used for the primary purpose of displaying information in an aesthetically pleasing way, I wouldn't raise the blank cells.

      Now, what you consider the aforementioned JSE tables as is possibly another matter. Personally, I think that it would be appropriate for any 'data table' to be classified 'sortable', as that demonstrates the record/field relationship (whether that's practical in a given case, ie tables with one or two records, would determine whether it was appropriate). However, any that would never be sortable are hence geared toward display and so blank cells could be omitted.

      Thanks very much for the feedback!

        Loading editor
    • A FANDOM user
        Loading editor
  • Hello Karu,

    I have been speaking frequently with Haldarn lately and he recommended that I talk to you as well. I am a returning editor, with a few friends actually, and looking where I could be the best help besides general page editing. Let me know if you ever visit the Discord too. I can be found under the same name. - Deszerath

      Loading editor
    • Hi!

      I'm not sure I'll have much work for you, since a lot of what I do lately is just bot and template work, but I'll keep you in mind if I ever need help with anything too complex for a bot.

      If you're looking for things in general to work on, we're missing pages for a lot of the items from around the start of Seekers of Adoulin and beyond. The wanted pages and stubs are a good place to look, but if you'd rather do it by content, the Reforged Empyrean Armor and High-Tier Mission Battlefields rewards are good places to start. Just remember to refer to the Item Template so that they have the latest formatting.

        Loading editor
    • Sounds great! I will start on that as soon as i finish some work on the job pages. Some of them are just so out of date on template, format, and information. I am using the layout being produced by Haldarn at the moment ass i figured that would be a great start.

      When i start on Seekers content in game i will be sure to bring over information i find from the game as well.

      Thanks for all the tips!

        Loading editor
    • A FANDOM user
        Loading editor
  • Hey Karu, what do you think of this layout?
    User:Haldarn/Arke

    I've always felt the current monster pages had far too much whitespace and what little info on the pages was displayed poorly. This is my first effort at reviewing that. Notice I've put Testimonials back on the main page, but in a collapsed-by-default section.

    I'm going to run through it with a few different mobs to check I haven't missed anything obvious but would appreciate any comments if you get the time (and anyone else reading!).

      Loading editor
    • Yeah, the monster pages have been in need of work for a while. I'm not terribly happy with the way Template:Monster Information turned out and Template:Infobox Monster is not great on functionality. A change is probably due.

      So, my biggest concern is how this is going to be implemented: are you thinking of making it a template or just putting the content on every page? As we've seen with the item section template, there are some technical issues with collapsible headers inside templates, both with the visual editor freaking out and the inability to section edit. Not using a template means it's hard to make global changes and opens them up for user variance and error, even when using substitution to generate the page the first time.

      Another possibly large concern is that this seems to only work for single monsters - how will it work with monsters that appear is several zones and have different levels/behavior/stats?

      On the smaller scale, I mostly have minor suggestions:

      Basic Stats
      • "Behavior" is the American English spelling; it's not a big deal, but for consistency, we should probably use American English over Commonwealth English on this site where possible.
      • Add the traditional A, S, H, L, etc. below the behavior icons for more familiarity.
      • The "Aggressive" icon could probably be improved - I had to hover over it to know what it was indicating (although the above suggestion could mitigate this).
      • Add a section below behavior for notes, like "Links with Treants" or "Aggressive only during the day" (though that could maybe be an icon).
      Rewards
      • Despoil needs a section.
      • Add a section for Crystals (and maybe Seals?).
      • Move "Titles" out of the loot table and make it a single line instead of a list since you only ever get one title from a monster (I think?).
      • Some monsters have loot breakdowns (e.g. "One of: ", "Zero to one of", etc.) and it might look weird/cramped in that table. Making drops span both columns would be a quick fix, but a fancier solution might be worth it.
      Spawns
      • Move the "Location" column to the first or second column for familiarity.
      Spells, Abilities & Stats
      • Make the HP, MP, DEF, and EVA columns into rows instead - it's a little easier to read that way, in my opinion. You could still have two sets side-by-side to reduce whitespace.
      • Add icons to the status resistances to make it easier to read. Maybe add a fifth column as well, since status effect names are pretty short.
      • "Species Ability" sounds a little awkward to me. The closest we have to an official name for them is "Monster Skill" from Monstrosity (a play on Weapon Skill, I would guess). Barring that, how about "Ability", "Monster Ability", or "Ability (Roc)"? "Special Ability" is fine too, but I don't think it's ever used in-game. "Species Ability" could probably grow on me if you're attached to it, though.

      As a final side note, the viewing experience is much better in Oasis - it'll need some tweaks in Monobook.

        Loading editor
    • Oh, I almost forgot about testimonials!

      I'm a little concerned about bringing them back to the main page. I think a "Strategy" section might be more appropriate, with a link to testimonials at the end.

      The issue with testimonials is that they're often long and detailed for tough NMs and you sometimes get people talking back and forth. It just ends up being a lot of clutter. It can be useful to sift through, but it's not really main page content.

      A Strategy section could be more like a collaborative walkthrough or guide, like the Quest pages, and could be separated into sections for different level ranges or setups.

        Loading editor
    • Thanks for the feedback! You've given me a lot to look at and think on, so I'll dig into it over the next few weeks.

      Basically I agree with everything you've written. There are a couple of things you've highlighted that require an elegant solution which I really need to have a think about. I was hoping to make a pure template, so I'll take a look again at the collapsible headers.

        Loading editor
    • A FANDOM user
        Loading editor
See archived talk page
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.