Re: FFXIII locations

I'd say create FFXIII/-2 location template. Don't add LR there since it doesn't share any locations with the two previous games, we can mostly go on speculations of what some of the areas were in the past, like the Dead Dunes is Archylte Steppe+Mah'habara Subterra but it is not confirmed anywhere so yeah, a location template for FFXIII and FFXIII-2 (I think only three or four locations appear in FFXIII and FFXIII-2: Archylte Steppe, Sunleth Waterscape, Vile Peaks, and Yaschas Massif, but there might be few more), LR can use the generic one.—Kaimi (999,999 CP/5 TP) ∙ 17:16, May 13, 2016 (UTC)

Sweet. Will this do?--Magicite-ffvi-ios.png Technobliterator TC 17:45, May 13, 2016 (UTC)
Yes, this'll do.—Kaimi (999,999 CP/5 TP) ∙ 21:49, May 13, 2016 (UTC)

IP Edits


Character subpages

Hey, can you tell me when character subpages will appear? I ask because Brave Exvius recently got soft-launched and some characters articles will simply not be rather accessible due to their sheer length.—Kaimi (999,999 CP/5 TP) ∙ 18:07, May 16, 2016 (UTC)

Oh, for characters, that's almost ready. I've got {{Subpages}} about half complete, and I can add a few finishing touches then put it live in about a day or two. Only reason I haven't gotten around to splitting character pages into subpages and finishing that template is basically because of my exams (which will be done in a week or two), but we could probably hurry that up due to Brave Exvius.--Magicite-ffvi-ios.png Technobliterator TC 18:14, May 16, 2016 (UTC)

Userbox Idea

Seeing how the enemy templates handle images for multiple games now, could we apply the same thing to character boxes? Presuming we limit it to games in the same universe to avoid the obvious issue of bloating, we could display multiple appropriate images for a character. Say, Lightning in her three outfits, or Cloud in FF7, AC, and CC, or Rikku and Yuna with their two outfits. We could also use it for characters that significantly change appearance in one game, like Cecil and Zack. DrakeyC (talk) 19:14, May 18, 2016 (UTC)

Oh yeah, that's really easy to do if you want. Can do it on any of the userboxes you'd like me to.
By the way, I read your latest fandom article. Awesome stuff. You actually made me want to play FFII!--Magicite-ffvi-ios.png Technobliterator TC 19:54, May 18, 2016 (UTC)

Tetra Master stats

Hello, your input on this topic would be welcomed, as I'm not sure which of initial or max stats would be best. --Froggy25 (talk) 15:58, May 22, 2016 (UTC)

Sorry I didn't get to this. tbh I'm playing FFIX at the moment in the card tournament and still have no clue how Tetra Master works at all, so not sure how much I can help you.--Magicite-ffvi-ios.png Technobliterator TC 23:29, May 24, 2016 (UTC)

Coding help

Hey, could you take a look at this and help me, please? What I want to do is to create a template which will be put on Record Keeper ability lists (and maybe on individual ability articles at some point) where a person includes characters-in-question's name as parameters and the inclusion of a parameter name would result in showing the character sprite along with a link to their article. I also want to make this template because manually placing characters in the game order tends to be a bit time consuming. Also, how much such a template full of little images would impact loading speed? It would be used maximum of six times on a page.—Kaimi (999,999 CP/5 TP) ∙ 23:12, May 24, 2016 (UTC)

Oh, I really like this idea. Sounds easy, I fixed it for you, but it can be made better/faster in Lua, meaning that there will be no real load time issues at all. If I set up the module and everything, can you fill in the character's name and their sprite link?
Also, lots of little images wouldn't really impact load times much, especially when we (eventually!) move galleries to subpages and change to the native <gallery> format. Oh, and I think there will be support for things like this when Wikia rolls out whatever data storage things it has to replace SMW anyway, so eventually this'll be even easier to use.--Magicite-ffvi-ios.png Technobliterator TC 23:25, May 24, 2016 (UTC)
If Lua can help made it better/faster then it's all the better. I can fill the template no problem (there's no need for me to dabble in the module, yes?). Is the name good enough? I don't think a long name would be good. Also, I don't think the template supports yet multiple parameters? I'm trying to put WoL and Sarah as a test but only WoL appears. Maybe each character should be given a number, like Garland would be "2", then Sarah "3", and so on? Or would the module resolve that thing?—Kaimi (999,999 CP/5 TP) ∙ 23:37, May 24, 2016 (UTC)
You don't need to dabble in the module that constructs the template, you'd just need to add the names in the /data module, which would look like Module:Button/data. Template name is fine, I probably would've done with something like "FFRK Charicon" if it were me, though. The current template doesn't support multiple params, though the final one with a module will be able to support infinite params.
If you want to just use numbers to make it easier, this would work, just keep in mind it'd be complicated as you'd have lots of characters to assign numbers to which could make it difficult to remember which is which, and if you ever wanted to change the number a character was assigned to, you'd need the bot, or just to edit lots of pages. If I were doing that, I would probably associate them with the release as well as just a number, so like, FFI-3 instead. I generally think it's better to just use the character name of an abbreviation of the name, but if that's what you want to go with, I can try it.
One question, does the sprite filename always contain just File:FFRK [name].png? It'd make things easier if that's the case. I can try and finish this template/module after my exam tomorrow.--Magicite-ffvi-ios.png Technobliterator TC 23:53, May 24, 2016 (UTC)
Not all sprite filenames will have File:FFRK [name].png format. For example Cids are gonna also last named, and in the earlier days some files where added with a "Sprite" and the end of the name, complicating the manner a bit. Also "Template:FFRK Charicon" seems a good name: the mainspace template will go by that, okay?—Kaimi (999,999 CP/5 TP) ∙ 12:25, May 25, 2016 (UTC)
Sure, go for it. And if so, that's fine, just means an extra thing to take into account for the module. It caches everything, so we don't need to worry about that.--Magicite-ffvi-ios.png Technobliterator TC 12:48, May 25, 2016 (UTC)
So right now I should focus on filling the template and it will automatically get caught be the module?—Kaimi (999,999 CP/5 TP) ∙ 13:08, May 25, 2016 (UTC)
Any list of the character's name, the sprite name and the page that should be linked to would be fine, and then I can get the Module up hopefully by the end of the day.--Magicite-ffvi-ios.png Technobliterator TC 13:25, May 25, 2016 (UTC)

When you'll find some free time, can you please work on module for {{FFRK Charicon}}? I haven't added a few characters (like Mobius since I'm not sure if they'll make it to global, despite adding Garland and Sarah to the template who status is a bit less uncertain IMO, and a few Core classes since they're not in global and I'm not entirey sure of their ordering).—Kaimi (999,999 CP/5 TP) ∙ 11:30, May 26, 2016 (UTC)

Sorry, I have one last exam tomorrow morning which I really want to revise for because it's an important module. I promise I'll get the module done after I've finished.--Magicite-ffvi-ios.png Technobliterator TC 21:27, May 26, 2016 (UTC)
No prob. ;) —Kaimi (999,999 CP/5 TP) ∙ 21:33, May 26, 2016 (UTC)
Made a start, you can see Module:FFRK Charicon, and I'm testing it in my sandbox here. Currently dealing with a few errors, I'll have it working soon. Module:FFRK Charicon/data is where the stuff will eventually be stored.--Magicite-ffvi-ios.png Technobliterator TC 13:45, May 27, 2016 (UTC)
Thanks for the help, very appreciated.—Kaimi (999,999 CP/5 TP) ∙ 14:28, May 27, 2016 (UTC)
Done! Do you mind filling out FFRK Charicon/data? That should be all it needs now before it's complete, then I'll expand the doc on the template a bit more. I would myself, but I'm currently on a pretty meh-ish laptop.--Magicite-ffvi-ios.png Technobliterator TC 15:02, May 27, 2016 (UTC)
Okay, I can do it. Thanks again for your help.—Kaimi (999,999 CP/5 TP) ∙ 15:41, May 27, 2016 (UTC)

Hey, do you think you could make it that the "icons" are displayed in the very same order as in Module:FFRK Charicon/data? This is exactly like the game order available in menus so it would be a good idea for the template to display characters like the game does, order-wise, as I suspect many readers will have that order kinda memorized.—Kaimi (999,999 CP/5 TP) ∙ 18:52, May 27, 2016 (UTC)

You can already do that with the template if you place them in that order when you use the parameters.--Magicite-ffvi-ios.png Technobliterator TC 18:59, May 27, 2016 (UTC)

I realise that. What I hope is that the order will be as in the Module regardless of the order of parameters.—Kaimi (999,999 CP/5 TP) ∙ 19:11, May 27, 2016 (UTC)

Oh. That's not possible with how the recursion works. Sorry.--Magicite-ffvi-ios.png Technobliterator TC 19:14, May 27, 2016 (UTC)
Oh, okay. Good to know though. Thanks.—Kaimi (999,999 CP/5 TP) ∙ 19:17, May 27, 2016 (UTC)


I compared flexboxes to a couple of alternatives in my sandbox. A columned dl is awesome in theory, but only IE 10+ does columns right, not moz or webkit yet. A table isn't totally inappropriate at the semantics level, but like you said, not responsive at all.

So the flexbox solution is definitely looking like a winner. Even got it to look okay in IE 8 and 9 with an inline-block fallback.

Did you want to set a max-width on the children? With flex-wrap: wrap, the list items are allowed to go the full 100% of the container before wrapping. This isn't terrible, but two adjacent lists 51% wide will refuse to go next to each other, which may take up more space than desired. ライケン(Rigel Kent) (talk) 10:08, May 25, 2016 (UTC)

I imagine if I made it a CSS class, I'd set a max width on any child divs to be 50% or something? That'd probably make sense. Thanks for taking a look! I could probably make this a CSS class now. Only issue would be having to change all the location pages to use it...--Magicite-ffvi-ios.png Technobliterator TC 10:11, May 25, 2016 (UTC)
On second thought, max-width could squish contents too small on Monobook on small screens — especially if the contents are tables. I probably exaggerated the chance of a single long list item messing with layout. Maybe forget about max-width unless there's a need for it in real articles? ライケン(Rigel Kent) (talk) 12:05, May 25, 2016 (UTC)
Mhm, we'll see how it turns out. I'm going to push the class live at some point today, and hopefully see if other people are cool with adding it to pages.--Magicite-ffvi-ios.png Technobliterator TC 12:48, May 25, 2016 (UTC)
As you've probably seen, I've implemented it now, and added it to a few pages, bot will add it to the rest of them later. Let me know if you have anything to add/change.--Magicite-ffvi-ios.png Technobliterator TC 21:32, May 25, 2016 (UTC)
Oh, do you know if there's a better solution for Kefka Palazzo#Stats? I kind of want to handle it better for pages like Ten Moogles#Stats. Mostly in that I want it to be able to display five different tables on one row on the Ten Moogles page if someone has a large enough screen hypothetically, but display a row of three and a row of two for most other screens (like it is now), and for small ones, two rows of two and one row of one. Do you know if it can be done?--Magicite-ffvi-ios.png Technobliterator TC 21:41, May 25, 2016 (UTC)
Looks like .multicolumn can handle tables the same way it handles lists, using the rules at User:Rigel Kent/wikia.css. Strip out old .colN containers and all width declarations, put it in a new .multicolumn container, done. Padding instead of width seems to work well. The ".multicolumn > *" selector is so it'll work on divs, lists, tables, images, or whatever else is inside it. Also recommend no "div" before ".multicolumn" for similar reasons: a list could be a valid multicolumn container too, as could (in the future) a section, a nav, an aside, or other semantic alternatives to divs. ライケン(Rigel Kent) (talk) 22:37, May 25, 2016 (UTC)
Hm, yeah, I agree with doing that. I've edited the CSS. The table problem I had still persists, though; as I looked at your sandbox, it's only showing two tables per row, even if the screen would make it ideal for three on one row. From using inspect element, changing max-width to 33% allowed it to display three tables, but I honestly think the maximum width should be 50% in most cases. Do you know what the best way to allow it to display more tables per row is?--Magicite-ffvi-ios.png Technobliterator TC 22:47, May 25, 2016 (UTC)
Also make sure there are no inline width declarations inside the table. The headers sometimes have them. ライケン(Rigel Kent) (talk) 23:47, May 25, 2016 (UTC)
Oh, whoops, looks like the tables in my sandbox ended up slightly wider than the live tables. I'll slim them down a bit to hit the 1/3rd of Wikia skin width breakpoint. ライケン(Rigel Kent) (talk) 00:02, May 26, 2016 (UTC)
What's weird is the live tables like on Kefka's page take up all the width the max-width allows them to when not edited in the way they are on your sandbox. What we need is an easy way to stop them from doing that in multicolumn, without breaking stuff like on Underground Waterway (Final Fantasy IV)#Items - if I set flex-basis to 20% or something, it squishes that last li in the 3D ul, and I'm not sure if it wouldn't squish other tables.--Magicite-ffvi-ios.png Technobliterator TC 00:30, May 26, 2016 (UTC)
It's a dirty hack, but inline width declarations can be overridden by a .multicolumn table, .multicolumn th, .multicolumn td { width: auto !important; } rule (example). That'd be a quick fix, but ideally, the inline width declarations (and the hack) should probably all be removed and replaced with something independent of page width, such as padding, whenever there's a chance. ライケン(Rigel Kent) (talk) 08:11, May 27, 2016 (UTC)
Yeah, I agree that the inline widths should be removed from any table in multicolumn. I'm not sure what the best way to get tables' column widths to match evenly with one another is without inline widths, though. The temporary solution you gave would work, but I'm not sure how much it'd be needed, because there aren't many tables using multicolumn yet (I intend to change that eventually). If there prove to be a lot, could use that while cleaning up the rest of the tables?--Magicite-ffvi-ios.png Technobliterator TC 09:39, May 27, 2016 (UTC)

Help Request


Navbox Help

Hi, I'm Pmbarbieri from the Italian final Fantasy Wiki. I wanted to make the tables and infoboxes on my wiki look like those on this one, but I am not very good at using codes and templates. I was hoping to find some help from you, since you're one of those who worked on templates like Navbox. Could you help me? --Pmbarbieri (talk) 21:22, June 3, 2016 (UTC)

I'd be happy to help. Can you be more specific about what you want?--Magicite-ffvi-ios.png Technobliterator TC 21:23, June 3, 2016 (UTC)

Just to have boxes like, for example, the FFX Location infobox with collapsible parts. Not necessarily the same as yours, but at least capable of working the same way. Just compare my page of Luca with yours. I'd like to be able to make infoboxes like that. --Pmbarbieri (talk) 21:33, June 3, 2016 (UTC)

Oh, that's easy. Since they use portable infoboxes, it'll work anywhere on Wikia. Since I'm a Vanguard, I can set it up for you if you'd like, you don't need to give me admin rights or anything.--Magicite-ffvi-ios.png Technobliterator TC 21:39, June 3, 2016 (UTC)

Great. Can you do it now? Jus try on the page I showed you. ^^——Preceding unsigned comment was added by Pmbarbieri (talkcontribs). Please sign your posts with ~~~~.

I'll set something up this weekend, please bug me if I forget. One question, though - why can't you just copy and paste the contents of Template:FFX Location and then translate it? There are a few CSS pages that you might need to import into yours (not copy and paste, just import), I'll have to get back to you on that, though.--Magicite-ffvi-ios.png Technobliterator TC 22:48, June 3, 2016 (UTC)

Like I said, I'm not very good with codes. I tried to copy-paste the template, but it doesn't seem to be compatible with my wiki's CSS. I don't know what to import to fix that. --Pmbarbieri (talk) 23:02, June 3, 2016 (UTC)

It won't be at the moment, because it relies on MediaWiki:Custom-releases.css. Just as an FYI for the future, as well as copying our Common.css and Common.js, you also need to copy any other pages attached to them, which will be listed at the top as well. So for JS, you also need MediaWiki:ImportJS, for CSS, you need Custom-releases.css.
However, at some point, I should have something set up for you to be able to just import Custom-releases.css into your CSS, so that any edit we make to one page you don't need to copy over.--Magicite-ffvi-ios.png Technobliterator TC 23:06, June 3, 2016 (UTC)

Many thanks. I tried to copy-paste many of your templates, mediawikis and modules to try and do it on my own, but I didn't obtain anything. In particular, I tried to recreate your Navbox template to fix some issues in the navigation boxes for the game, since they were copied from your old navboxes: just check the bottom of any Final Fantasy Tactics related page on my wiki to see what I mean. --Pmbarbieri (talk) 23:14, June 3, 2016 (UTC)

Yeah, I totally understand how you feel. Our wiki has been changing really rapidly lately, and you guys are always several steps behind. It's why I'm looking at ways that you can just import our pages, rather than copy and paste every single time, so that they update on your end automatically. I promise you that with the coming changes ot the wiki in the next year or two, once those are finished, you won't need to update much again.--Magicite-ffvi-ios.png Technobliterator TC 23:26, June 3, 2016 (UTC)

RE: Gallery


Re: Character subpage splitting

Yes, I will happily help, but my edits will be a bit slow this month since it's exams time at my uni now. I can understands "/Other appearances" and "/Gallery", but would "/Gameplay" be for? Is it to make main character articles main story-oriented and move the not-so-main story-oriented things to subpages?—Kaimi (999,999 CP/5 TP) ∙ 23:50, June 4, 2016 (UTC)

Best of luck with the exams! And it'll make more sense when I show an example.--Magicite-ffvi-ios.png Technobliterator TC 00:00, June 5, 2016 (UTC)
Sorry, didn't realise how little time I'd have today. I can start next week. I'm also not sure if we should keep the subpages template or just link to subpages using main or something.--Magicite-ffvi-ios.png Technobliterator TC 21:44, June 5, 2016 (UTC)
Yes, we can delay it till next week. We just shouldn't make delaying the habit with how rapidly SQEX (re-)releases games.—Kaimi (999,999 CP/5 TP) ∙ 13:10, June 7, 2016 (UTC)

Gallery image size concerns

OK, I understand that the Mother Ship wants us to use HTML5/CSS scripting for image galleries now, but the default display size really does not work for things that are more stubbish or where the full image is meant to be displayed as a thumbnail. Based on the other wiki I edit for, I assume there's a parameter can be set somewhere to make sure these things display in the proper orientation and size on all devices. Is there anything we can do to correct this issue? Swordzmanp236 (talk) 01:04, June 6, 2016 (UTC)

...Still not sure what you mean. I don't think this is an urgent issue to correct, firstly as no one has given themselves time to get used to the new galleries, and secondly, because "things that are more stubbish" shouldn't be more stubbish, they should eventually have a lot more content. But as for changing the size on a few specific galleries, you just answered your own question.--Magicite-ffvi-ios.png Technobliterator TC 11:32, June 6, 2016 (UTC)
I'm of the same opinion, at least fix to 25% image size of galleries with less than four images (aka leave empty spaces) instead to oversize them; they looks odd -.- By the way, would you take a look at List of Final Fantasy Trading Card Game cards/Ice that I moved just now? For me the new gallery is not working properly but the code is all there, maybe is just an issue with my chaced data. In case you confirm me that it is fine I will ask to remove the redirect. Thank you : )
TTFan from JP (talk) 12:23, June 6, 2016 (UTC)
The page works fine for me. One thing the gallery does is that it only loads images when it has to, to improve page loading times, which is why they weren't all there immediately.
Also, I'm not going to lie, galleries with less than four images do look way oversized, if you ask me. Instances like this are where I think resizing the gallery might not be a horrible idea - if that's what Swordzman meant by "more stubbish", then I'm not opposed to the idea.--Magicite-ffvi-ios.png Technobliterator TC 12:30, June 6, 2016 (UTC)
Most likely is not only that. As he wrote we lost at least one good feature: to show a whole image in a discrete space (now we have an even larger square and the image is cutted above/below or left/right thus, missing information). Even if we are able to input parameter like percentage of the total area in order to show more than four images, more than two rows, most likely is impossible to add a parameter with aspect ratio of each image, or maybe is? : ) Mind my case with Triple Triad (Portal App) tutorial cards for example: if inside the code gallery I can put something like style=image-size:72px;aspect-ratio:original;column:6;row:2 and then each image will be shown resized accordingly would be already great. Of course you must set some limit or we will be quickly back to a situation in which all of the images are shown again ^_^" One note aside, what about removing every image? Japanese Wikia and Wikipedia alike barely use them ; )
TTFan from JP (talk) 13:19, June 6, 2016 (UTC)
Ah, I forgot one thing. In case images are all of different sizes, the whole thing is a lots more complicated (I have no idea here) -.-
TTFan from JP (talk) 13:22, June 6, 2016 (UTC)
Not sure what you mean. However, at some point when you require all these features, it may simply be better to use a table instead. Just remember to check how it looks in the mobile preview as well.--Magicite-ffvi-ios.png Technobliterator TC 15:07, June 6, 2016 (UTC)
All right, here you go. Pick an event from FFRK. Any event. One thing that the gallery does is blow the banners up to way out of proportion, let's say 300% of normal size. From my end, it looks like only the center 1/3 of the Japanese plaques show up in this new tile design. It just looks UGLY, and we need a workaround. Swordzmanp236 (talk) 19:55, June 6, 2016 (UTC)
Alright, I see what you mean. My first question would be, why would you create a gallery that exists solely for the Japanese banner, if it won't contain anything else (forgive me if it contains more than that, I only sampled a few pages)? There are other places to put it. If we set up an FFRK Event infobox, we could easily put the Japanese banner image in a separate tab, or something like that. Or we could easily place it somewhere else on the page, such as directly below the main image. While I agree with you that it doesn't look great when a gallery has one image in, galleries aren't supposed to have only a single image. But if this becomes a more recurring problem, no need to use gallery parameters, I'll just look at a CSS solution.--Magicite-ffvi-ios.png Technobliterator TC 20:32, June 6, 2016 (UTC)
Aight, you're going to have to discuss a possible solution with Miyuron or Kaimi on that one. I just write the scenarios and apply the design elements they've used. Dangerous Beauty premieres tonight (my local time), so we can start there. Swordzmanp236 (talk) 20:57, June 6, 2016 (UTC)
Sure, will do. Thanks for bringing this to my attention anyhow, we knew there would be problems with changing the gallery, but they'd have to be addressed after the change. Sometimes the problems are less with the gallery and more with the use of the gallery, so it's just important to work out which is which.--Magicite-ffvi-ios.png Technobliterator TC 21:03, June 6, 2016 (UTC)

We could create a template for FFRK events and put global and Japanese banner there. Among the information provided by the infobox we could include characters, their Memory Crystals, abilities acquired and such. It wouldn't be much of a problem to fill for events starting with Tifa reissue, but the early ones might prove harder to fill. Would that do?—Kaimi (999,999 CP/5 TP) ∙ 22:13, June 6, 2016 (UTC)

Yep, sounds perfect. It could be similar to Template:FFRK Dungeon?--Magicite-ffvi-ios.png Technobliterator TC 22:19, June 6, 2016 (UTC)
Sorry, I'm back : ) Well, some may be turned into tables but at the moment I don't know if we have some tool that can replace the old "use" of galleries. As you correctly pointed out the main issue is the use, what they are good for now. If you mind the "other appearance" section of any character, monster, job, etc. there there are high chances that in the past, even a single image was placed in a gallery... But I want to highlight another matter about the old galleries: I never used to add parameters to the old gallery code but here and there some are still keeping it, the class parameter. Is it of some use or can be removed? In my case, TT(PA), I placed anchors inside them but now I had to remove and replace linkings, they just works wrongly now. There is a better place where to report these kind of details?
TTFan from JP (talk) 06:00, June 7, 2016 (UTC)
Class has no use, it was kept in just as a place holder in case it is one day used. It's not a big deal if you leave it out. And as for reporting issues, there's the forum, but my talk page is generally fine. It's not like a lot of people use it when IRC exists.--Magicite-ffvi-ios.png Technobliterator TC 06:41, June 7, 2016 (UTC)
Quick update: I've put Dangerous Beauty online sans images for now. Hopefully youse guys can use that as a test case. Swordzmanp236 (talk) 08:05, June 7, 2016 (UTC)

Can you make an option to make the images fit within the frames instead of getting their parts cropped out? Some galleries look really bad, like the merchandise galleries and game packaging artwork galleries. Monterossa (talk) 08:17, June 7, 2016 (UTC)

I've heard people complain about parts being cropped out, but I've never seen it? So I really cannot comment there at all.--Magicite-ffvi-ios.png Technobliterator TC 08:36, June 7, 2016 (UTC)
Recently you edited Cecil Harvey page and there are a lots of galleries there, less or more odd looking. The reason is that the more an image is away from an aspect ratio of 1:1, the more will be cropped out. If you mind that Full-HD is 1920x1080px with a ratio of 1.77, this means that (depending how it is rotated) will lose 20% from each sides or 40% of the bottom. Best iPhone ratio, always in the case of screenshots as a whole, is 1.5 of the old iP4; iP5 is already at 1.775. Old NTSC, PAL systems are around 1.33 while the Golden Rectangle ratio is 1.618. In short, we need a fix that fit : )
TTFan from JP (talk) 09:13, June 7, 2016 (UTC)
But we're...not worried about iPhones? They use a different Mercury skin, which renders galleries completely differently - so it really makes no difference.--Magicite-ffvi-ios.png Technobliterator TC 10:15, June 7, 2016 (UTC)
As the galleries, both our old code and the portable version, are designed to be a set of thumbnails you can click on to get the full sized image, I struggle to see how "the thumbnails get cropped" is a major issue. -- Some Color Mage ~ (Talk) 10:30, June 7, 2016 (UTC)
The day I will find a good looking way to turn a gallery into a table (or anything else), I will do it : )
TTFan from JP (talk) 11:14, June 7, 2016 (UTC)
If you need a table, you really should just use a table and not a gallery. Again, that applies to both our and Wikia's versions of galleries. -- Some Color Mage ~ (Talk) 11:51, June 7, 2016 (UTC)
And to add to what SCM said, this a perfect example of a table that can fulfil your needs.--Magicite-ffvi-ios.png Technobliterator TC 12:12, June 7, 2016 (UTC)

Okay guys, because this section has been really bloated, I'm just going to make a few things straight. I get it, it's a massive change moving to the new gallery, we expected there to be several issues - in fact, I expected there to be far more than there were. But some of the feedback I'm getting here is not that helpful. Please stop and consider the following before you rush to post here:

  • In many instances, check if the galleries were misused instead of broken - a gallery for only a single image, or a gallery that attempts to contain too much information, for instance, should not have been using the gallery template, and should not now use Wikia's gallery. Please stop and think about whether the gallery feature is being appropriately or optimally used before saying that it's a massive bug that needs to be fixed.
  • Add screenshots or links to any issue you are having. Giving me a generic "I have this problem, fix it please" message without properly showing me what the problem is won't put me in a good position to help you out. I am very likely to use a different device to you, with a different screen size, a different operating system, maybe even a different web browser.
  • Give the gallery templates some ample time. It's a jarring change, but I seriously question whether a lot of these concerns are legitimate issues as opposed to an emotional reaction to change. And by that I'm not saying I don't want your input, I'm just saying that you should give them time to get used to them, and if an issue you have is still a major issue later on, is not a misuse of the gallery template, and is a proven and legitimate problem, it will be looked at.

I welcome any and all substantial feedback on the gallery transition, I need to hear input if we're going to make it work for us. But I can't deal with multiple complaints that don't appear to have much substance to them or that I can't really comprehend. And I also don't want to make knee-jerk reaction CSS changes that may not serve a proper purpose. So I'd really like anyone posting to take these things into account before you ask for a quick gallery hack fix.--Magicite-ffvi-ios.png Technobliterator TC 12:12, June 7, 2016 (UTC)

FINAL FANTASY X/X-2 HD Remaster Omega Ruins Chests PC Strategy

Hi, in your article about Omega Ruins, you wrote "The exception is the PC HD remake version, where players can reroll to get the 99 Warp Spheres by using the save in the ruins". Can you confirm this strategy? What is your source? --Siegfriedmk (talk) 15:52, June 10, 2016 (UTC)

Community content is available under CC-BY-SA unless otherwise noted.