Re: FFXIII locations[edit source]

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[edit source]

ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG

Character subpages[edit source]

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 {{tl|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[edit source]

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[edit source]

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[edit source]

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)

Flexbox[edit source]

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[edit source]

ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG

Navbox Help[edit source]

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:infobox 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[edit source]

ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
ACRudeBox.PNG
Technobliterator.png
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG

Re: Character subpage splitting[edit source]

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)

Okay, no problem. Just a question: the other day I saw at the appropiate forum topic that for "/Other appearances" to appear a character is required to have at least 5 appearances, correct? I don't think it'll be a problem with FFXIII characters, but there there are other games which have around that number of "other appearances," so I want to make sure in advance before I'll probably go wild a little.—Kaimi (999,999 CP/5 TP) ∙ 20:31, June 21, 2016 (UTC)

Yeah, 5 other appearances not including non-FF appearances, just so we don't end up making tiny subpages for everything - while FFXIII characters will probably be fine indeed, I don't think most FFIV characters will need an other appearances split. We don't have to go for that though, I just think that'd be the best way to do it. Thanks for help!--Magicite-ffvi-ios.png Technobliterator TC 20:37, June 21, 2016 (UTC)

Also, some characters who are candidates for subpage splitting (like "Sarah (Final Fantasy)") are not exactly playable in their original game. Do we still, for the sake of consistency if nothing else, also categorize their subpages like "Category:Final Fantasy Y playable charcters <subpage name>"?—Kaimi (999,999 CP/5 TP) ∙ 14:54, June 26, 2016 (UTC)

If they're non player characters, go for "Category:Final Fantasy Y non-player charcters <subpage name>". Even if it's only a small category, the name has to make sense.--Magicite-ffvi-ios.png Technobliterator TC 14:58, June 26, 2016 (UTC)

Okay, but what if a character is playable in other games relating to their main game, like FFXIII series: should Noel and Serah get a category for FFXIII-2, and what about characters "playable" via Paradigm Pack system there? (The Paradigm Pack question is also kinda related to the Creature Creator system from FFX-2HDR since the system is similar from what I can tell, although I never played the remaster.)—Kaimi (999,999 CP/5 TP) ∙ 15:03, June 26, 2016 (UTC)

In that case, you should use the category for the game in which they're playable. "Category:Final Fantasy XIII-2 player character gameplay" for Serah. For characters playable through things like Paradigm Pack, I don't remember how that works. Can you control them that way? If not, then "Category:Final Fantasy XIII-2 non-player character gameplay", and if you can control them, "Category:Final Fantasy XIII-2 player character gameplay" because then they technically are playable, or maybe "Category:Final Fantasy XIII-2 guest character gameplay".
I should warn you not to read too much into what I've done on other pages regarding categories and some things. For instance, with FFX, Yuna and Rikku will definitely need "Category:Final Fantasy X-2 player character gameplay" when I get around to also splitting Paine's page, and Auron, Tidus etc will definitely need a "Category:Final Fantasy X-2 non-player character gameplay" because of Creature Creator. So you should do what makes the most sense to you.--Magicite-ffvi-ios.png Technobliterator TC 15:12, June 26, 2016 (UTC)

Could I have you put up the links to Y'shtola/Other appearances? Might want to take a look at the other MMO stuff too, since the characters seem to be everywhere. Swordzmanp236 (talk) 19:57, June 29, 2016 (UTC)

I can, but is there any reason why you can't you do it yourself? Unless you mean getting everything to link to the new subpage, in which case the bot will do that anyway when the job is mostly finished. And Shantotto is probably the only one that needs an other appearance subpage.--Magicite-ffvi-ios.png Technobliterator TC 20:03, June 29, 2016 (UTC)
Just need the link lists, thanks, and you do that so well. Swordzmanp236 (talk) 20:08, June 29, 2016 (UTC)
Ah, that part. Okay, I'll handle it on that page.--Magicite-ffvi-ios.png Technobliterator TC 20:24, June 29, 2016 (UTC)

Gallery image size concerns[edit source]

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 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[edit source]

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)

Uh, it's not my article? No one "owns" any article on the wiki. And I didn't write that particular sentence either, so I can neither confirm it nor provide a source. Feel free to add {{citation needed}} next to any claim that seems dubious though. You may want to ask Tia-Lewise or Monterossa, who actually own the PC version of the game.--Magicite-ffvi-ios.png Technobliterator TC 15:56, June 10, 2016 (UTC)

Sorry. There was your name in a topic on Steam discussion forum of the game. Thanks for the info. --Siegfriedmk (talk) 16:01, June 10, 2016 (UTC)

Galleries in infoboxes[edit source]

I am not sure of it's just me or some Wikia bug, but <code><gallery></gallery></code> doesn't appear to work in infoboxes where it's supposed to create tabs when used. Can you tell me which is it, and when it will probably be fixed?—Kaimi (999,999 CP/5 TP) ∙ 16:01, June 16, 2016 (UTC)

It's a Wikia-wide bug caused by a patch, and will be fixed in under 24 hours.
Unrelated, but you caught me at a good time; I'm just about to start the subpage split project, will have something ready shortly.--Magicite-ffvi-ios.png Technobliterator TC 16:11, June 16, 2016 (UTC)

Embedded gallery bug[edit source]

Looks like we've got a bonafide bug here, since yesterday.

The scenario: A new infobox template relies on the use of embedded image galleries for proper display. If an image source name contains a symbol of any kind, that image is not processed.

To reproduce Create or use a template, then place gallery tags inside it. For this bug to reproduce, at least one of the enclosed filenames must contain a symbol such as an apostrophe (') (e.g. File:FFRK The Pulse Fal'Cie Event.png )

This issue does not manifest in standalone galleries.

--Swordzmanp236 (talk) 16:08, June 17, 2016 (UTC)

Please take a look at my message in the section above. I know you told me how to reproduce the bug, but I can't really help you unless you show me examples.--Magicite-ffvi-ios.png Technobliterator TC 16:12, June 17, 2016 (UTC)
Certainly. Take a look at the source for Destiny's Path and The Pulse Fal'Cie (Record Keeper) for examples. Let's use Two Sides of a Coin as the control for the test. Swordzmanp236 (talk) 16:24, June 17, 2016 (UTC)
Got it, thanks. This is probably something that happened after the bug yesterday. I can't fix it, so it's best to report it to Wikia. If you tell them what you just told me, they should hopefully be able to fix it.--Magicite-ffvi-ios.png Technobliterator TC 16:28, June 17, 2016 (UTC)
Before I bug it out to The Mother Ship, thought I'd let you know that this bug seems to affect the desktop view only; mobile seems OK. (verified this afternoon local time) Swordzmanp236 (talk) 00:53, June 18, 2016 (UTC)
Haha, I love how you call them "The Mother Ship". Okay, they'll definitely want to know that too.--Magicite-ffvi-ios.png Technobliterator TC 00:54, June 18, 2016 (UTC)
Update from Central: it's a system-wide issue which they're still looking at. We're going to have to be extremely careful as to how images will be named when uploaded. They just can't contain the single-quote/apostrophe mark anywhere if they are to be used in embedded galleries. Swordzmanp236 (talk) 05:24, June 19, 2016 (UTC)

Rydia/Other appearances[edit source]

This page was mistakenly categorised in Category:Final Fantasy IV player character galleries‎. I already added it to Category:Final Fantasy IV player character other appearances, but I cannot remove the wrong category. Would you be able to do it?--LeafShinobi (talk) 00:37, June 22, 2016 (UTC)

Way ahead of ya. It's really easy to remove categories, just edit the page, and then in the category list on the right, delete it by pressing the icon.--Magicite-ffvi-ios.png Technobliterator TC 00:39, June 22, 2016 (UTC)
Thanks. Just noticed this part was hidden when I was editing.--LeafShinobi (talk) 00:43, June 22, 2016 (UTC)

RE: FFX Models[edit source]

ACRudeBox.PNG
Technobliterator.png
Technobliterator.png
ACRudeBox.PNG

Non-Final Fantasy appearance prior appearances[edit source]

Hello Technobliterator, when you have the time could you take a look at this topic. Here's a short summary; A bunch of "objects" have made an appearance prior to their appearances in Final Fantasies and later incorporated into the Final Fantasy franchise. Fenrir9 (talk) 14:47, June 26, 2016 (UTC)

Sure, I'll respond.--Magicite-ffvi-ios.png Technobliterator TC 14:58, June 26, 2016 (UTC)

Hate it when I'm bored...[edit source]

Started an article on Apple proper, seeing as they're behind a couple pieces of hardware that are already here. And since we cover Microsoft, Nintendo and Sony in 1-2 pages apiece, why not? Actually, looking for ways I can connect it to these other hardware stubs without going too far overboard. Suggestions? Swordzmanp236 (talk) 00:16, June 30, 2016 (UTC)

I'd just establish the context behind Apple as the people who made the Mac and iOS devices, and maybe mention how no games in the series really released on anything made by Apple until the iPhone. If you really want to add more, could add that they came up with smartphones first.--Magicite-ffvi-ios.png Technobliterator TC 11:32, June 30, 2016 (UTC)
Aight, take a swing if you want. I'm pretty sure that they didn't invent the smartphone per se. I'll even leave it to you as to which of Apple's many apples to use as a logo. You speak in six colors, sliced glass, or solid? Swordzmanp236 (talk) 05:34, July 1, 2016 (UTC)
No, they didn't invent the smartphone, but mostly any smartphone made since the iPhone has followed the same format, even if that format was just borrowed from tons of different places. And the solid one is probably the best fit, whatever is used in macs or ios now.--Magicite-ffvi-ios.png Technobliterator TC 18:19, July 2, 2016 (UTC)

Character-specific abilities navbox[edit source]

Hey, you think we could acually make this live? It would certainly help with putting navboxes on ability articles which can't exactly have skillet navboxes in them. I realize the name might be a bit long (we prefer two-word names when it comes to things like that I think), but it's an accurate name.—Kaimi (999,999 CP/5 TP) ∙ 23:34, June 30, 2016 (UTC)

There's only one problem with it that I have: it should be based on the subseries rather than on the games. For instance, Paine did not appear in FFX, so Spira should be the classes used, and Reno was not playable in FFVII, so CompVII is more appropriate. Another thing is I'm not sure how I feel about using those ifstrings on collapsibles, but that's a small thing we can change later and doesn't need changing now.
Other than that, go for it. I really dig the idea of the box, it could be super useful.--Magicite-ffvi-ios.png Technobliterator TC 23:41, June 30, 2016 (UTC)
The template is actually an edit of {{navbox weapons}} IIRC, hence the ifs, so when adding that template to, let's say, "Omnislash" article we would type {{Character-specific abilities|FFVII}} so when a reader would uncollapse the template it would initially open on FFVII-related content. If it's to be based on subseries then "Spira series" is an absolutely bad name for it: "Final Fantasy X series/FFXser" would be a better name IMO.—Kaimi (999,999 CP/5 TP) ∙ 00:01, July 1, 2016 (UTC)
I agree with "Final Fantasy X series", but the class is currently "Spira series" for some stupid reason. Might change that in a month or two when it's finally time to overhaul that class system.--Magicite-ffvi-ios.png Technobliterator TC 00:03, July 1, 2016 (UTC)
Can the template's name stay or do we want to abbreviate it, like "Charex abil" (which would be actually rather confusing for some editors I suppose)?—Kaimi (999,999 CP/5 TP) ∙ 12:01, July 2, 2016 (UTC)
No need to abbreviate it, the name isn't that long.--Magicite-ffvi-ios.png Technobliterator TC 12:09, July 2, 2016 (UTC)
Okay, I will shortly put it live. Do you plan on any changes? I can change class colors (and I think section names would be needed to be changed appropiately as well).—Kaimi (999,999 CP/5 TP) ∙ 17:45, July 2, 2016 (UTC)
Nothing at the moment, it's fine for the time being. If we need to make any change, there's no harm in doing so later, presumably when we get wikia's portable navboxes.--Magicite-ffvi-ios.png Technobliterator TC 18:19, July 2, 2016 (UTC)

Portable navboxes? That sounds pretty cool!—Kaimi (999,999 CP/5 TP) ∙ 18:28, July 2, 2016 (UTC)

Hell yeah. Hopefully they'll also be so much faster at loading. No official announcement of a release date or even if they're definitely coming, but I think they're extremely likely.--Magicite-ffvi-ios.png Technobliterator TC 20:08, July 2, 2016 (UTC)
That'd be cool if it came to that. Also, since we're going really detailed do you think we could also make categories for those abilities too? Basically they'd be called "Category:<char_name> specific abilities", or should we drop the word specific although in that case we would need to include spells in these categories if we would drop the word "specific".—Kaimi (999,999 CP/5 TP) ∙ 21:11, July 2, 2016 (UTC)
Hm, I'm not sure if we'd need to include the character's name in the category, but if you want to do that, something like "<char name> command abilities" would work, but honestly "Character command abilities" would be fine. Assuming all of them are command abilities? I thought that was the case anyway.--Magicite-ffvi-ios.png Technobliterator TC 21:17, July 2, 2016 (UTC)
Some are commands, some are abilities from skillsets, e.g. Yuna's "Grand Summon" is a command, but Lulu's "Firaga Fury" is an ability from a skillset, so it's not all that clear cut IMO. (Well, that's how I understand the difference between command and an ability: command is in the same tier of a menu as "Attack" and "Item" and selecting it results in performing an ability, as opposed to ability from a skillset where you pick a command and it opens a submenu with abilities associated with the command.)—Kaimi (999,999 CP/5 TP) ∙ 21:33, July 2, 2016 (UTC)
I just assumed it meant what it did in FFIX. "Command ability" is an active ability that is used when you select it, "support ability" is just a passive ability that's always on. If we were going by that, then Lulu's Firaga Fury would be a command just like Fury would be a command. But that might not be how other people use it and I might be wrong.--Magicite-ffvi-ios.png Technobliterator TC 21:36, July 2, 2016 (UTC)
Aren't you confusing command and skillset abilities now? But we're getting off track, aren't we?—Kaimi (999,999 CP/5 TP) ∙ 21:43, July 2, 2016 (UTC)
Yeah...:P I wonder if we should ask Xenomic what to name the category instead? He'd probably know better, he normally sorts out ability organizing and stuff.--Magicite-ffvi-ios.png Technobliterator TC 21:51, July 2, 2016 (UTC)

Well, I still stand by ""Category:<char_name> specific abilities" since it's the most descriptive and allows us to avoid putting general abilities into it. Plus, we could (and should) ignore wether the ability is a command or a part of a skillset if it's associated with the character. No point in debating about such things when there are more pressing matters.—Kaimi (999,999 CP/5 TP) ∙ 22:00, July 2, 2016 (UTC)

Yeah, sure. The category name works fine, it's just not what I would've chosen if I were doing it.--Magicite-ffvi-ios.png Technobliterator TC 22:03, July 2, 2016 (UTC)
You prefer to put them in a generic category, the same way they're put on a single navbox rather than on individual ones?—Kaimi (999,999 CP/5 TP) ∙ 22:13, July 2, 2016 (UTC)
That's what I'd probably do if it were me. Creating specific categories per-character is fine, though, so just do what you think is best.--Magicite-ffvi-ios.png Technobliterator TC 22:18, July 2, 2016 (UTC)
I'd rather get input from few more people before I'll go crazy with categorizing.—Kaimi (999,999 CP/5 TP) ∙ 22:47, July 2, 2016 (UTC)

I would prefer signature abilities over character-specific abilities, seen too many RPGs or other media (manga/anime/etc) that uses the word "signature" to describe an ability associated with a specific character in their fandom. Fenrir9 (talk) 00:37, July 3, 2016 (UTC)

Oh, I wouldn't mind that. "Signature abilities" sounds like a good name IMO and is actually a better term in our case since there are few abilities shared between specific characters (like some Monk abilities) that they're not as "character-speficific" but more of "signature" or "commonly associated with them" abilities. If we were to go with "Signature abilities" we would need to change the template name, but that's no biggie.—Kaimi (999,999 CP/5 TP) ∙ 13:39, July 3, 2016 (UTC)

So, um... No one sees a problem with renaming the template and making template-wide category instead of character-specific categories?—Kaimi (999,999 CP/5 TP) ∙ 10:10, July 10, 2016 (UTC)

Quick Request[edit source]

ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
Sounds like you may need a "batch image converter", or whatever it's called. Do be careful, as searching for one of these often smacks you into a paywall, or worse yet, malware. Swordzmanp236 (talk) 21:45, July 4, 2016 (UTC)
Technobliterator.png
ACRudeBox.PNG
ACRudeBox.PNG
Technobliterator.png
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
Technobliterator.png

Page splitting time?[edit source]

I've been thinking, similar to what we've been doing with the characters with a crap-ton of appearances, we've got now this massive list of FFRK events that needs to be divvied up. I'm all set to copy/paste a portion of the list into a new page, but I'd like some community feedback first. Actually, it's one big question. How would youse guys like these lists to be titled: "Challenge Event/__________ "? (fill in the blank) Swordzmanp236 (talk) 22:54, July 4, 2016 (UTC)

I'm not really as familiar with FFRK as with the other games, since I haven't played in ages and won't be able to for a few months due to needing a new phone. But go ahead with making subpages, you don't need permission.--Magicite-ffvi-ios.png Technobliterator TC 23:26, July 4, 2016 (UTC)
Not asking for permission per se. I'm asking what the title of the subpages ought to be. Like, what's the protocol for splits of this type? Swordzmanp236 (talk) 23:40, July 4, 2016 (UTC)
...and it's done! Swordzmanp236 (talk) 16:51, July 5, 2016 (UTC)

IRC Down?[edit source]

BlueHighwind TA.png
Technobliterator.png

One step left[edit source]

As you can see, I trimmed and split the Shantotto page earlier today. Long past due. Now, we need the short list in the vacated section. At your leisure, of course. Swordzmanp236 (talk) 00:02, July 13, 2016 (UTC)

User:Kaimi/FFRK Abiltrait[edit source]

So I'm working on User:Kaimi/FFRK Abiltrait which I intend to use on those ability tables for FFRK (I went with a template for a standarized layout), but I'm not sure what wrong with the <code>{{expr:}}</code> I'm using to calculate the damage potency. Can you help me out?—Kaimi (999,999 CP/5 TP) ∙ 17:05, July 23, 2016 (UTC)

Think it should work now? But anyway, you need a hash because it's a parserfunction, so {{#expr:}} is what you want.--Magicite-ffvi-ios.png Technobliterator TC 17:22, July 23, 2016 (UTC)
I forgot that. I feel so ashamed. OTL Thanks for the help. ;) —Kaimi (999,999 CP/5 TP) ∙ 10:11, July 24, 2016 (UTC)

A useful python script[edit source]

If you're ever answering requests on Intangir Bot that involve tagging you should run this script first (put it in the same folder as user-fixes.py):

import re
import string

base = raw_input("Base page: ")
tag = raw_input("Tag: ")

capsgex = '[' + base[0].upper() + base[0].lower() + ']' + base[1:]

output = """fixes['tagging'] = {
    'regex': True,
    'msg': {
        '_default': u'Relinking to [[""" + base + " (" + tag + """)]]',
    },
    'replacements': [
        (r'\[\[[""" + capsgex + "\]\]', u'[[" + base + " (" + tag + """)|]]'),
        (r'\[\[[""" + capsgex + "\|', u'[[" + base + " (" + tag + """)|'),  
        (r'\[\[[""" + capsgex + "\#', u'[[" + base + " (" + tag + """)#'), 
        (r'\{\{[Ss]L\|[""" + capsgex + "\|^(?!color).*$', u'{{SL|" + base + " (" + tag + """)|'),
        (r'\{\{[Ss]L\|[""" + capsgex + "\|color', u'{{SL|" + base + " (" + tag + ")|" + base + """|'),
        (r'\{\{[Ss]L\|[""" + capsgex + "\#', u'{{SL|" + base + " (" + tag + """)#'),
        (r'\{\{[Ll]A\|[""" + capsgex + "\|', u'{{LA|" + base + " (" + tag + """)|'),
        (r'\{\{[Ll]A\|[""" + capsgex + "\|', u'{{LA|" + base + " (" + tag + """)|'),
        (r'\{\{[Ll]A\|[""" + capsgex + "\#', u'{{LA|" + base + " (" + tag + """)#'),
        (r'\{\{[Ll]A\|[""" + capsgex + "\}\}', u'{{LA|" + base + " (" + tag + ")|" + base + """}}'),
        (r'\{\{[Mm]ain\|[""" + capsgex + "\}\}', u'{{Main|" + base + " (" + tag + ")|" + base + """}}'),
        (r'\{\{[Mm]ain\|[""" + capsgex + "\|t', u'{{Main|" + base + " (" + tag + """)|t'),
        (r'\{\{[Mm]ain\|[""" + capsgex + "\#', u'{{Main|" + base + " (" + tag + """)#'),
        (r'\{\{[Ss]ee Also\|[""" + capsgex + "\}\}', u'{{See Also|" + base + " (" + tag + """)}}'),
        (r'\{\{[Ss]eeEnemy\|[""" + capsgex + "\}\}', u'{{SeeEnemy|" + base + " (" + tag + """)}}'),
        (r'\{\{[Ss]ee Also\|[""" + capsgex + "\#', u'{{See Also|" + base + " (" + tag + """)#'),
        (r'\{\{[Ss]eeEnemy\|[""" + capsgex + "\#', u'{{SeeEnemy|" + base + " (" + tag + """)#'),
        (r'prev\s*\=\s*[""" + capsgex + "', u'prev = " + base + " (" + tag + """)'),
        (r'next\s*\=\s*[""" + capsgex + "', u'next = " + base + " (" + tag + """)'),
    ]
}
"""

print output

with open('user-fixes.py', 'ab') as f:
	f.write(output)

Then run

python pwb.py replace -ref:"PageYoureRelinking" -fix:tagging

to tag the pages.

Loosely based on a script JBed dumped on my talk page a year ago and I never had a use for but found today while I was digging through my user talk for something else. Cat (meowhunt) 06:13, July 31, 2016 (UTC)

Super late reply...this is a pretty awesome fix. Should throw this on an Intangir Bot user subpage somewhere? We really need a better place to put these scripts, hahaha.--Magicite-ffvi-ios.png Technobliterator TC 21:45, August 16, 2016 (UTC)

Some consideration[edit source]

Good morning Technobliterator. I would like to rise a small request, is it possible to have the old gallery code once again active? It was better looking than the new one and surely more flexible than a table. So I would like to benefit of its versatility for the Triple Triad (Portal App) tutorial cards mainly. To have those cards incompletely displayed and only up to the first eight do not serve any purpose for TT(PA)'s users. On top of this, the purpose of the new gallery code is already or almost over in my opinion, let me to explain how.

Mind a general example of a pretty standarzied non-generic topic article. It may be splitted in four main section: the proper body article with information about the non-generic topic; then a Other Appearance section; then a Gallery section; and then NavBoxes, categories and other technical stuffs. In the beginning Intangir Bot replaced the old gallery code with the new one, obtaining the immediate effect to reduce considerably the loading time of article pages. It perfectly reached its own purpose but generated some other side-effects. I will list some below.

After this both the Other Appearance section and the Gallery section were moved to subpages, reducing even more the loading time of articles pages. But this second edit is it not overlapping with the first one? In the moment you have galleries out of the main article page is not a real issue anymore their loading time, isn't? With this I do not intend to suggest to revert the first edit and to go back globally to the old gallery code. The new gallery code may remain in place but having the old one too will allow editors to manually revert those galleries that are accounting for up to ten images. They will looks surely better than how they are now, especially where there are two or three images only, don't you agree? I believe that the loading time won't be affected at all if we consider to replace only the small galleries.

Now, go with the issues of the new gallery code. In the very beginning Intangir Bot replaced or removed part of code and in doing this the result was not always a success. It was looking for |File:image.png and to reduce it to image.png only, but in some cases the original code was just |image.png thus Intangir Bot did nothing at all. And this lead to a bug because the new gallery code recognized the | (pipe) as part of the image name, but no image with such a name actually exists. And this lead to another bug, the new gallery code do not output anything in the case an image is not found, nothing. You can check the Chocobo article under Appearance for Final Fantasy Dimensions and the edit I did there. Was a gallery with two images but when I opened the source code I noticed that were listed three images. The latter one had the image name written lowercased while the real image have it uppercased. And this is just one example because there are even galleries in which all of the images are miswritten with the result that in visual space the gallery do not appear at all, while in code space is still there.

Another mistake that Intangir Bot did in the beginning is to replace the }} that was supposed to end the old gallery code with the newest </gallery>, but when inside the old gallery code were present anchors, the replacing stuff ended the new gallery code a lots before of where it was supposed to be. And you can see this one if you look at the history of the Tutorial cards article pointed above. I'm pretty sure that those and more issues are still around. You can even reply that there are almost 20,000 pages for maybe 200,000 galleries and what is done is done, but then I will reply that it is fine, give me a list and in the next four months I will take care of all of them, even alone. But need a clear plan, this job can be done in different ways, and of course a supervisor. That is, sorry for being long.
TTFan from JP (talk) 05:48, August 16, 2016 (UTC)

Wow. That's a really long message. I'm going to give you a shorter message.
  1. Make use of tables. For the kinds of pages you're working on, this is much better than using galleries in mostly all instances. Even the original Gallery template wasn't designed for what you're using them for. Try something like this format.
  2. The old Gallery template is not coming back. That is not negotiable at this point. As nice as some of its features were, it was not only slower, but it was a real pain for any non-desktop skin, which is to say, it was much worse for the mobile skin.
  3. Please stop using tabbers. Seriously, tabbers aren't just bad for the mobile skin, they're bad web design in general. Shoving lots of information into a small space is really a bad idea. You should think about splitting into subpages. See my link above for how to do that.
  4. Other appearances and gallery subpages could still change. I would prefer to move all galleries from /Other appearances subpages to /Gallery subpages as well, but others did not agree. If you want to discuss that with the broader community, feel free to do so. I cannot unilaterally make decisions.--Magicite-ffvi-ios.png Technobliterator TC 21:45, August 16, 2016 (UTC)
*sigh* :,) Anyway thank you for the answer, even if short it is pretty clear. About #1 you already suggested me that before and often, and finally I came out with something in my sandbox. By the way, those Artniks pages are not going to be edited anymore so may I clean the code there? Do you prefer game's numbers written as 3 or III? Nothing to say about #2. About #3 I cannot do differently. Long time ago another user showed me them (moving my tables into tabs) and I liked them a lots, users too like them, and from time to time I check those pages with an iPad and I notice no difference from the desktop version. Splitting is not a good solution for TT(PA) pages. Last, #4, I hate forums, to stay up to date with it is already a job by itself and I have not so much time. But I was thinking almost like you, to move all of the Other Appearance images into a single gallery at the bottom of the Other Appearance section itself. The subpage Gallery should retain "original" material related to the article only like screenshots, artworks and the likes. I will drop you a notice when TT(PA) is ready and for Artniks too, see you in few days.
TTFan from JP (talk) 03:05, August 17, 2016 (UTC)
  • You're perfectly free to just clean code literally anywhere on the wiki. :P So the Artniks pages are no different.
  • The iPad skin is not different from the desktop skin, it's the mobile phone skin that's different. That's the worrying one. Furthermore, even on iPad, the tabs used in tabbers are so small and hard to use for a touchscreen that it's not a great solution at all.
  • You don't need to stay up to date with every forum on the wiki! Just check a few that are relevant to you. Simply make a new post about the change you want and it can be discussed on there.
  • Out of curiosity, why do you say splitting is not a good solution for TT(PA) pages? If you're worried about readers needing to click on more than one page, don't - you're serving readers much better by giving them faster loading, more focused pages with content directly relevant to their needs than giving them one page overloaded with information and making them scroll through a lot of it. You don't need to take my word for this, this is the generally accepted norm in web development.--Magicite-ffvi-ios.png Technobliterator TC 03:14, August 17, 2016 (UTC)
TT(PA) have two main pages, the card list and the deck list, and both are big and getting bigger almost every month. To split them in subpages means to create 25 new ones for cards (each series) and 42 new ones for decks (each opponent/difficulty mode). Internal links from cards to decks will increase of about five times and while I'm not still sure of every detail, I'm already thinking of it. At the moment I have barely a single user that from time to time give me some feedbacks, and another user that is helping with edits. Both like how it became with the only exception of those new galleries. We already did a lots to keep the user-friendly displayment of data at an acceptable loading time. So for now I will turn galleries into tables, while leaving tabs, and see the result. After discussing with the other editor, about what should be better to do in order to remove tabs and keep everything light, I will be back here. My worry is not to lose editors in the first place, and I bet they don't use a mobile phone for editing...
TTFan from JP (talk) 12:16, August 17, 2016 (UTC)
Are you absolutely sure you need to create 25 new subpages? You should only need to create about 3, 5 or so subpages for both of them. You don't need to create a new subpage for each series, you could create one subpage for series 1-5, one for series 6-10, one for 11-15, etc.
Anyway. I will still say again, please try not to use tabs, and if you have to stretch too far to retain user-friendly display and acceptable load times, it might not be as user-friendly as you think. While it's very easy for you, the guy who coded it, to understand, it probably isn't easy for an average mobile user. Also, editors aren't what we're worried about, it's readers. No one uses a mobile phone to edit, but lots of people use a mobile phone to browse, and when Triple Triad on Portal App is a phone game, they should have the wiki easy to use. Definitely do change galleries to tables, but I would strongly suggest thinking of ways to create subpages.--Magicite-ffvi-ios.png Technobliterator TC 12:38, August 17, 2016 (UTC)

A bit late but I'm back, maybe in a busy moment for you. TT(PA) pages are updated, now is left only one gallery and were was already possible tabs are removed, give them a look if you have time. Now, we are going a bit away from the topic of this section so, in a try to keep it short, I have one more question: is it a problem to have so many subpages and why? For Wikia's servers should change nothing I think.
TTFan from JP (talk) 07:43, September 5, 2016 (UTC)

Not at all. We have far more serverspace than we would need.--Magicite-ffvi-ios.png Technobliterator TC 09:57, September 5, 2016 (UTC)
Very well then, next time I will be back with a prototype then : )
TTFan from JP (talk) 11:23, September 5, 2016 (UTC)
It's done, you can take a look at it in my Sandbox, the Card and Deck lists with few collapsed tables. The idea is to leave as few as needed info using text only and leave links for subpages with images. Now I'm going to create subpages. When all of them will be ready, coded and tested TT(PA)'s tabs will decrease a lots more.
TTFan from JP (talk) 08:32, September 7, 2016 (UTC)

Hello Techno. TT(PA) restyle is now complete but in the process I found a possible issue. On iPad collapsed tables are not visible at all, there is a way to fix it or is it fine to leave it as it is?
TTFan from JP (talk) 06:39, September 13, 2016 (UTC)

It's alright to leave it as it is for the time being. Tables not being collapsible aren't the end of the world, it just means more scrolling.--Magicite-ffvi-ios.png Technobliterator TC 06:41, September 13, 2016 (UTC)
So do you suggest to leave tables not collapsed? At the moment on desktop are correctly displayed collapsed with the [show] button. Is on iPad that there are even no hints that there is a table on the page.
TTFan from JP (talk) 06:48, September 13, 2016 (UTC)
Can you link me to where that's happening? I'll check.--Magicite-ffvi-ios.png Technobliterator TC 06:50, September 13, 2016 (UTC)
Triple Triad (Portal App) cards and Triple Triad (Portal App) decks. Toward the bottom, below FF14 cards series there is one table, and below Y'shtola decks there are three tables, respectively.
TTFan from JP (talk) 06:56, September 13, 2016 (UTC)
Both look totally fine on my end, checked on tablet and phone. There's no reason why this should be an issue. So I'd say it's fine to leave it as it is at the moment. The tables look really nice, btw.--Magicite-ffvi-ios.png Technobliterator TC 07:04, September 13, 2016 (UTC)
Thank you very much, merit of the black background anyway, it helps really a lots. So that should be a problem on my iPad only, most likely is too old by now. End of transmissions for now.
TTFan from JP (talk) 07:27, September 13, 2016 (UTC)

The nightmare of tabbers[edit source]

Wow, looks like you need to clean house here, chief. Some of these threads are so long that you're the needle in the haystack, but anyway...

I spotted your comment above re: tabbers, and it's pretty clear to me that one group of pages needs help fast. We're now getting so many reissues of Record Keeper characters that the whole thing is an absolute nightmare to code, and it looks way worse on mobile phones because it all stacks together without adding the numbers in. Those are needed for the charts to have an impact. So, I was wondering whether you had any ideas to solve this mess? Swordzmanp236 (talk) 03:41, August 17, 2016 (UTC)

Yup, I know all about those. :P I've already been working on a mass-purge of tabbers. Broadly speaking for most pages, simply replacing them with flexbox columns code works. However, for the FFRK characters, what will probably be needed is a new template for them, like Template:FFRK Dungeon Info. That should be the best way to display information. Speaking of which, I've been on holiday for three weeks of the past six or so, but do you still need the bot relinking to the /Other appearances#Final Fantasy Record Keeper sections? Sorry if that hasn't been done yet.--Magicite-ffvi-ios.png Technobliterator TC 03:48, August 17, 2016 (UTC)
Shantotto needs a little relinking at the head page (see far above this thread), and FF V characters need to be looked at. Everything else looks OK for now. Swordzmanp236 (talk) 03:58, August 17, 2016 (UTC)
Given another pass over the Challenge Event lists, looks like we need to redirect character links to "/Other appearances" pages for events prior to Memorial Day '16. I'll keep fixing the character profile stuff as needed (I've fixed it through FF IX as of this writing). Pre-May '16 event blurbs need reformatting unless any link contains an apostrophe (') or a percent sign (%); Xeno identified the latter as another bugged character in galleries. Everything is coming so rapid-fire these days that few are wont to look back. Giving it my best shot. Swordzmanp236 (talk) 03:55, August 18, 2016 (UTC)

Request for skin redesign[edit source]

Hi Technoliberator. I spoke with CzechOut about your request. His schedule is full for the next several weeks. If you're wanting to work with him specifically, he should be available to start working with you around late September or early October, which would be two months (or close to it) before the new game's release date that you mentioned.

If you don't want to wait for him to be available, I'm happy to help. If you choose to have me help, please share with me details about what you have in mind for the redesign and/or how you want to get started. JoePlay WikiaStaff2.png (talk) 20:29, August 17, 2016 (UTC)

Heya! I don't mind who specifically, I'm just more familiar with CzechOut's CSS skin design work and don't feel comfortable redoing skins on my own. So while I'm fine with waiting for him, it'd be slightly easier for me if I could have your help sooner, since late September is when I go back to university. I was thinking that I'd lay out the design ideas I had, probably code up the CSS I can on my own on a sandbox wiki or somewhere, and then we can go over it to get to a final version. Does that work for you?--Magicite-ffvi-ios.png Technobliterator TC 21:00, August 17, 2016 (UTC)
Yep, that works for me! If you don't mind, leave a message on my talk page when your sandbox is ready, so that I'll be guaranteed to see your message ASAP. JoePlay WikiaStaff2.png (talk) 14:09, August 18, 2016 (UTC)
I looked at the page containing the outline for the redesign. It looks like you have a solid plan, and everything you listed should be very doable! Feel free to message me again when you want me to take a new look or help with anything. JoePlay WikiaStaff2.png (talk) 18:14, August 22, 2016 (UTC)
Actually, I was wondering if you could help me out with a few things I'm stuck on before I move onto some other parts of the skin. I'll let you know on your talk page - and actually, we could probably move the discussion there so it's easier to keep track of. :P--Magicite-ffvi-ios.png Technobliterator TC 19:13, August 22, 2016 (UTC)

brb[edit source]

my uni internet blocks a lot of ports that aren't HTTP, including 6667 (IRC), so I'll be missing for an indefinite amount of time until I can get that sorted. Discord doesn't work but Intangir seems to use HTTP so I can still make bot edits. If something needs to be done immediately you can make a new section on my talk page for it. Otherwise, I'll see you when IRC isn't kill. Cat (meowhunt) 16:09, August 21, 2016 (UTC)

Oh geez, that sounds annoying, mine let me access basically anything. Nothing needs doing immediately, I'm just working on the skin redesign and a few other things. Preferably sometime in September would be good to finish off the module work.--Magicite-ffvi-ios.png Technobliterator TC 16:14, August 21, 2016 (UTC)

A request.[edit source]

(Sigh) Another day, another coding question:

So I've got this entry up for the divided gauntlet FFRK Challenge Event that is Discord and Harmony. What we have is a situation where there will be two events, both with the same set of rules and each being half of the whole thing. There's really not much I can write about either without the other; nor do I have much background on Dissidia as a source.

My original plan was to incorporate two instances of Template:FFRK Event, one per section. I think I can make it look presentable on desktop; but for mobile, looks like only one of the two will be shown. I've talked to Kaimi as he's the inventor, but he doesn't seem to have any ideas as to how to deal with this situation. You were recommended for the task. Can you offer help/advice? Swordzmanp236 (talk) 18:54, August 22, 2016 (UTC)

Ok, any infobox is designed to be only one per page, so FFRK Event as it exists won't work for what you want. I'm familiar with Discord and Harmony, so I imagine you want it to list Cosmos and Chaos info separately, yeah? That can can be done, and there are three ways we can do it:
  1. Use the current infobox the same way, with Chaos: etc and Cosmos: on each parameter. That's the lazy way, and I'd honestly avoid it.
  2. Edit the infobox to allow with collapsible headers for the two different ones - like how Template:infobox location works. Where 1 is Chaos and 2 is Cosmos, it would be "1 japan", "2 japan", "1 global", "2 global", etc. This is the best way, probably.
  3. Same as the above, except we make a new infobox called "Template:FFRK Multi-Event", or "Template:FFRK Event/multi" to do it. I find that pointless, personally, but it's an option.
Up to you? Also partly related, but please check out Forum:New Character Infobox.--Magicite-ffvi-ios.png Technobliterator TC 19:13, August 22, 2016 (UTC)
"Two...Number two?" -Don Corneo, Final Fantasy VII
That would probably work. You set the code and import what's there, we'll handle the rest. Swordzmanp236 (talk) 19:36, August 22, 2016 (UTC)
Done! Hopefully that works for you.--Magicite-ffvi-ios.png Technobliterator TC 19:44, August 22, 2016 (UTC)

thanks[edit source]

I'm rarely around here anymore, but I do pop by every once in a while. I just want to say thank you for pushing ahead with the character subpages overhaul.. something that I saw being a problem about a year ago. The character pages are so much cleaner and easier to use now.

if I may make another suggestion.. on how to deal with the list of appearances which still remain on the main page, I'd say it may be a better idea to break the lists down into smaller categorizations, and then display them with a tabber. the tabs will be based on the broader categories of the games which appear in the series navbox and you can take out any tab which the character has no appearance in

something like this.. say for Cloud.

  • Final Fantasy V in loading screen as a 2D sprite.
  • Final Fantasy VII technical demo in a cutscene. (random note: i moved this from lower in the hierarchy because a tech demo of ff7 is still set in the ff7 universe lol)
  • Final Fantasy VII: Snowboarding as the playable character.
  • Final Fantasy VII G-Bike as the playable character.
  • Lightning Returns: Final Fantasy XIII as a garb for Lightning.
  • Final Fantasy XIV as an outfit and a Triple Triad card.

  • Final Fantasy Tactics as a playable character.

  • bla bla

  • bla bla

  • (most will be here lol)
  • Pictlogica Final Fantasy as a playable character.
  • Final Fantasy Airborne Brigade as a summonable Legend.
  • Final Fantasy Artniks as a series of cards.
  • Final Fantasy All the Bravest as a playable character.
  • Final Fantasy Record Keeper as a playable character.
  • Final Fantasy Explorers as a Trance.
  • Final Fantasy World Wide Words.
  • Mobius Final Fantasy as a uniform for Wol.
  • World of Final Fantasy as a guest character.
  • Chocobo Racing as a secret character.
  • Final Fantasy Trading Card Game as a series of cards.
  • World of Final Fantasy as a playable character.
  • Triple Triad as an opponent.

  • and so on

just a suggestion. personally that would be how i'd prefer to break up the sections in the Other appearances pages as well. "series appearances" would seem a bit too broad because most of the characters with such pages only have series appearances.. only superstars like Cloud, Lightning and the like have ever made other appearances. 2gil--Arciele Spira (talk) 05:54, August 23, 2016 (UTC)

All well and good, Spira, but I, for one, am almost positive that we're trying to eliminate legacy tabs for the simple reason that the code no longer renders correctly on mobile devices and thus does not provide a usable experience to all. I'm sure Techno will chime in when he returns from his break, but that's my take on it. Swordzmanp236 (talk) 06:32, August 23, 2016 (UTC)
well im sure techno will have his own considerations for which kind of code will work better or not based on his knowledge. i'm generally more of a visual person and it doesnt really matter to me how something is done if the outcome is visually similar lol. the other consideration i suppose is what our target audience is. if it can't be done in another way without affecting users on mobile then one has to weigh how much of the userbase is affected by stuff like that. To what i understand quite a number of users access the wiki by mobile.. so idk. Then again, I do question the practical value of the list itself because all it does is link you to all the stuff that is already on the link above it, so anyone mildly interested in Other Appearances should already have clicked on it and seen everything from there. in other words, the list adds no value to the UX at all.--Arciele Spira (talk) 07:29, August 23, 2016 (UTC)

No problem. I wanted to do something about the increasingly bloated page sizes, it was Drake who came up with a basic idea and I pushed ahead with making the split final. I do think that the current list for the other appearances section is pretty dull looking, but I went for something basic because it was the easiest thing to do knowing we could change it at any point.

Swordzman is right; tabbers are going to be phased out. They don't display at all on any non-desktop skin, which is currently important for the mobile skin. Views on the mobile skin make up well over 50% of all viewers in general so it's important to improve that experience while preparing for the launch of FFXV.

The list is used basically to tell people what different appearances the character made and give them a link if they're curious for more info, without going into detail and taking up too much space on the page. I'm not opposed to dividing the appearances in the list up by categories like the one you suggested here, but if they should be displayed, it should be by flexbox, sub bullet points or through use of another template. Preferably not something that has to take up too much horizontal space.--Magicite-ffvi-ios.png Technobliterator TC 20:29, August 25, 2016 (UTC)

Marked image issues[edit source]

Per an earlier talk thread on another user page/some list somewhere, you suggested that pages with image issues use Template:Bad Name or something similar. I've marked quite a few with that tag. Is it possible that you or someone else can help resolve these pages so marked? Swordzmanp236 (talk) 23:06, September 9, 2016 (UTC)

Anyone with Moderator privileges can do that, and if you remind me, I'll look into getting those for you. In the meantime, you might want to ask someone else with them such as Kaimi or Kelt, I'm currently too burnt out with this infobox and redesign stuff to really help.--Magicite-ffvi-ios.png Technobliterator TC 23:08, September 9, 2016 (UTC)
I can't be a Mod yet, but I have shot the request over to Kelta as advised. Much obliged, chief. Swordzmanp236 (talk) 23:40, September 9, 2016 (UTC)

Hidden text??[edit source]

ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG

Image with transparent background[edit source]

Hello again, I did fast to be back. By chance I found this image File:PFF Lightning XIII-2 Illust.png that with a white background and in preview mode looks fine but on black background is "holed". The reason is that the transparency is inside the sprite too and not only around it. By the way, I would like to volunteer to reduce tabbers all around, any suggestions? I was thinking to turn FFAB tabbers into subheaders for example.
TTFan from JP (talk) 11:44, September 14, 2016 (UTC)
Edit: tabbers with text only, images only, a mix of both are all an issue or I can skip some of them?
TTFan from JP (talk) 13:07, September 14, 2016 (UTC)

I just checked, and it looks ok to me. I think it's intentional. EDIT: Oh wait, I was looking at the wrong image. I just checked, someone made the background transparent and then accidentally damaged the image; I reverted it to before when the background was not transparent and it's better now.
Awesome that you want reduce the use of tabbers. Tabbers with a mix of text and images are always a problem for the same reasons. Turning tabbers to subheaders would be a great start. Another way to convert tabbers to something else is to turn them into multicolumn divs, when you can get more space on the page, such as here. FFAB tabbers are a great place to do this, along with FFRK and some others.--Magicite-ffvi-ios.png Technobliterator TC 13:11, September 14, 2016 (UTC)
Understood, that shop in Vector is a nice example, I will try to apply it where possible.
TTFan from JP (talk) 13:24, September 14, 2016 (UTC)
Edit: what about this one I edited just now?
TTFan from JP (talk) 13:33, September 14, 2016 (UTC)
Looks great!--Magicite-ffvi-ios.png Technobliterator TC 16:24, September 14, 2016 (UTC)
Kaimi dropped a good suggestion, instead to use subheaders use semicolons, in order to avoid messing up the TOC. And while looking around I found the borderless table code that should be used instead of the multicolumn divs. I re-edited the few I did yesterday, so if you wanna take a look at them you can found them into my contributions from Abyssus Forest to Aeon (Final Fantasy X). The borderless table use {|width=100% as opening line and then |width=50% valign=top| for each column. It can be adapted to occupy less than the whole screen like in the case there are images on the right side, or divided in more than two columns.
TTFan from JP (talk) 03:05, September 15, 2016 (UTC)
Please don't use borderless table code, it should not be used instead and is very outdated code. The multicolumn divs are designed to be adaptable for different screen sizes - it will display as many columns on the screen as there is space for them. The borderless tables will display two columns no matter what, which can be extremely crowded on some screens.--Magicite-ffvi-ios.png Technobliterator TC 12:04, September 15, 2016 (UTC)
Well, tomorrow I will start over again then. Luckily I didn't go so much forward. Anyway there are some situations that I cannot handle, until now one is "Aero Combatant" and another one is "Air Elemental (Vagrant Story)", this last one you maybe didn't update it yet with a new template.
TTFan from JP (talk) 12:17, September 15, 2016 (UTC)
That's fine; I'll fix the ones you've already done, and I'll try and look into those. Other than that, keep up the great work.--Magicite-ffvi-ios.png Technobliterator TC 12:25, September 15, 2016 (UTC)
Wait, wait, wait. I will fix them first, with Adrammelech some part of the original info are now missing. One I can submit to you immediately is "Adamant Isle Grotto" that have an image on the right side. How to handle it? If outside of multicolumns will move everything else below, if inside... do it looks fine?
TTFan from JP (talk) 12:33, September 15, 2016 (UTC)
In that case, just move the image on the right to be above the multicolumns.--Magicite-ffvi-ios.png Technobliterator TC 12:37, September 15, 2016 (UTC)
Will generate an empty space the eight of the image itself, is it fine? I have the same issue with "Agart" just now.
TTFan from JP (talk) 12:48, September 15, 2016 (UTC)

So, which solution do you prefer between "Adamant Isle Grotto" (image inside divs), and "Agart" (image above divs)?
TTFan from JP (talk) 13:01, September 15, 2016 (UTC)

"Adamant Isle Grotto" might be the best choice.--Magicite-ffvi-ios.png Technobliterator TC 14:42, September 15, 2016 (UTC)
Done. Since tomorrow I will go forward and if I meet something strange I will report it here. Time to sleep for me, bye.
TTFan from JP (talk) 15:06, September 15, 2016 (UTC)
Today's dose is done, I'm waiting for feedbacks now. If you looks at my contributions list there are some labeled for a check. I'm keeping a record in my sandbox too, I will update it daily.
TTFan from JP (talk) 09:44, September 16, 2016 (UTC)
Looks great! Keep up the good work.--Magicite-ffvi-ios.png Technobliterator TC 11:28, September 16, 2016 (UTC)
The main point are those three FFXII's locations. There I found a lots of tabbers used to separate info between the original release and the International Zodiac Jobs System one. Because tables were compact enough to be placed sideways, I replaced tabbers with divs. But all together were wrapped into a cellpadding code and because I don't know how to handle it I simply removed it. It is still in place where tabbers were not involved anyway. Did I do wrong?
TTFan from JP (talk) 12:38, September 16, 2016 (UTC)
Nope, you did it totally right. Again, keep up the great work, it's fantastic that you're helping with this.--Magicite-ffvi-ios.png Technobliterator TC 14:14, September 16, 2016 (UTC)

Back to this topic, File:PFF Caius Illust.png have the same issue. The HGX is not around anymore?
TTFan from JP (talk) 12:56, September 17, 2016 (UTC)
Edit: reverted it to the previous version.
TTFan from JP (talk) 02:29, September 19, 2016 (UTC)

Found File:PFF Cloud of Darkness Illust.png but it cannot be reverted, exists only with transparency. By the way, I found the Confessions of the Creator article (and its subpages). Before to edit it is better if you look at it a bit because this time the edit will be maybe worse. EDIT: D's Journal/People too, the page is already long, without tabbers will be extremely long, but is all text at least.
TTFan from JP (talk) 14:08, September 22, 2016 (UTC)
Found File:PFF Curilla Illust.png too, same situation.
TTFan from JP (talk) 14:31, September 22, 2016 (UTC)
May I add "Images with wrong transparency" category to images I find around? Is a transparent edit because is done directly on each image page and can be removed easily; on top of that will keep together in the same place images with the same issue, in the case someone will like to fix them.
TTFan from JP (talk) 08:27, September 23, 2016 (UTC)
Can't say I see the use of that, you're better off coming up with some kind of maintenance template to put on those pages. In cases where only the transparent versions exist, the only thing that can be done is just uploading a different version of them, and I can't really get PFF images, so I'm not who you should ask about this.--Magicite-ffvi-ios.png Technobliterator TC 10:52, September 23, 2016 (UTC)

FFRK character list redesign[edit source]

So, here we are again. I'm looking for someone who can code up a redesign of the FFRK character grids sans tabbers. Those most in need are marked in cleanup. If you would like to push this out to Kaimi, Xeno, et al. as well, any help much appreciated. Swordzmanp236 (talk) 21:51, September 15, 2016 (UTC)

I'd love to help, but I don't really have the time to work on it right now. Once preparing the wiki for FFXV's launch is over, and my life is less busy, I'll be happy to lend time to projects like this again.--Magicite-ffvi-ios.png Technobliterator TC 21:56, September 15, 2016 (UTC)
Techno, do you have already some ideas under your hat for FFRK and we should wait for you, or we can go forward alone? With collaboration of Kaimi and Arciele the situation is moving on but so far we are still a bit afraid to procede. Regardless of the code used, there are always some issues, even the divs code I'm using to replace tabbers around doesn't seem to be the right cure. So the first question is "What will work?/What we should use?", and then "How to replace so many entries?/Who is available for it?" From my side I have two extra questions, do I have to skip FFAB section from de-tabberring as Xeno's concerns? Do wikia will be back to a white background first or later? The second question is related to images with wrong transparency, if wikia will be back to white background soon then I think it should be fine to leave them as they are.
TTFan from JP (talk) 07:10, September 20, 2016 (UTC)
So you may need to give me more context than what you've given here.
No, I have no ideas for FFRK, I don't really know anything about the situation but I assumed you people were doing fine on your own. Neither of you need my permission, from what I could tell you were doing fine on your own, otherwise I would've stepped in and offered some ideas.
With regards to FFAB, I'd say there's no reason to skip it, but I don't know what Xeno's concerns are. The wiki won't have a white background again until a few months after FFXV's release - so early next year - and when it will, it'll probably go back to a dark background for FFVII Remake's launch. So I wouldn't plan edits around the background. The only idea I ever came up with for that game was using tables and turning it into a template, which is probably still not a great idea.
If replacing lots of entries is tiring, or you want to move onto something else quicker, then you can just take a break from it. It's a lot of work, and it's awesome you're doing it, but we don't need them done immediately.--Magicite-ffvi-ios.png Technobliterator TC 07:45, September 20, 2016 (UTC)
Understood. We will go forward with FFRK then, and I will keep reverting those images with odd transparency. In case you succeed with that Template test I'm keeping track of my edits so we can "quickly" fix them. About my stamina it is still fine, anyway at this pace I will be busy again with TT(PA) before to finish. Nothing else for now, keep in touch.
TTFan from JP (talk) 11:15, September 20, 2016 (UTC)

Hello Techno, me and Man went a bit forward into "List of FFRK characters" talk page. If you please to take a look at there and into my SandBox too, we are in need of technical/style feedbacks.
TTFan from JP (talk) 09:42, September 22, 2016 (UTC)

Here again. About your template, I tried to work it out with different number of images, the result is in my SandBox (Gallery). I tried to make it looks good for small galleries too but cannot find a good compromise. Maybe you can mind something more out of it.
TTFan from JP (talk) 11:42, September 26, 2016 (UTC)

More Unused Images Requesting[edit source]

ACRudeBox.PNG
Technobliterator.png
Technobliterator.png
RedWizard-ff1-psp.png
Some Color Mage / Talk Contribs / Let's Stream Random PS4 Crap. / 11:35, September 23, 2016 (UTC)
I believe the reason a few of the logos are like that is because Spira uploaded new copies of the main series logos that have transparency from the 30th anniversary website but only updated the game pages, not the logo page.
FFRK Shantotto.png
PFF PuPu.png
Technobliterator.png
PFF PuPu.png
Technobliterator.png
FFRK Shantotto.png
RedWizard-ff1-psp.png
Some Color Mage / Talk Contribs / Let's Stream Random PS4 Crap. / 03:43, September 24, 2016 (UTC)
None of our infoboxes used black backgrounds before the theme change, so unless you've been playing around with them more since then I can't imagine that would cause any problems.
Technobliterator.png

Image galleries in infoboxes[edit source]

I think that incorporating multiple images in infoboxes would make sense if certain characters are playable in multiple games or have multiple designs, such as Rikku, Lightning, and Yuna. This could help save space by not having to place any needless images in the Profile section of their pages.

Take this mockup of Lightning's infobox as an example:

{{FFXIII Character
|name=Lightning
|japanese=ライトニング
|romaji=Raitoningu
|image=<gallery>
FFXIII-Lightning CG.png|Ex-Soldier
Lightning FFXIII-2.png|Etro's Champion
Lightning - LRFFXIII.png|Savior
</gallery>
|home=[[Bodhum]]; [[Valhalla (Fabula Nova Crystallis)|Valhalla]]; [[Nova Chrysalia]]; [[New world (Lightning Returns)|New World]]
|age=20, 21 (''Episode Zero -Promise-'')<br/>21{{foot|Physically}} (''Final Fantasy XIII''<ref name="ffxiiiscenulti10">{{Refbook|[[Final Fantasy XIII Scenario Ultimania]]|010}}</ref>, ''Final Fantasy XIII-2'', ''Lightning Returns''<!-- Lightning was taken to Valhalla right after FFXIII's ending, and time in Valhalla doesn't flow like it should: TIME DOES NOT EXIST IN VALHALLA. After that, she is in crystal stasis; thus, like Fang and Vanille, she does not age physically, only chronologically. -->)<br/>521{{foot|Chronologically}} (''Lightning Returns'')<!-- Lightning awakens 500 years AFTER the events of XIII-2, thus making her 521 years old chronologically. See first note for explanation as to why she has not aged five hundred years. -->
|race=[[Human]], [[l'Cie]] (formerly)
|gender=Female
|height=171cm (5'7")<!--DO NOT CHANGE HEIGHTS WITHOUT PROOF. Always cite your reference(s).--><ref name="ffxiiiscenulti10"></ref>
|laterality=Right-handed
|ffxiii type=playable
|ffxiii primaryroles=[[Commando (Final Fantasy XIII)|Commando]], [[Ravager (Final Fantasy XIII)|Ravager]], [[Medic (Final Fantasy XIII)|Medic]]
|ffxiii limitbreak=[[Army of One]]; [[Army of One|Legion of One]]
|ffxiii summon=Odin
|ffxiii weapon=[[Final Fantasy XIII weapons#Blazefire Saber|Blazefire Saber]] gunblade (''Final Fantasy XIII'')<br/>[[Zantetsuken (Final Fantasy XIII weapon)|Zantetsuken]] (during Odin's Gestalt mode)
|ffxiii ultimateweapon=Omega Weapon
|xiii2 type=paradigmpack
|xiii2 weapon=[[Final Fantasy XIII-2 weapons#Overture|Overture]]
|lr type=playable
|lr weapon=[[Lightning Returns: Final Fantasy XIII weapons#Crimson Blitz|Crimson Blitz]]
|designer=[[Tetsuya Nomura]]
|japaneseva=[[Maaya Sakamoto]]
|englishva=[[Ali Hillis]]
|motioncapture=Naho Nakashima
|gameplay=true
|quotes=true
|crystarium=true
|boss page=Lightning (Final Fantasy XIII-2 boss)
|other appearances=true
|dissidia=true
|gallery=true
}}

This might also be useful for locations that appear in more than one game or have multiple areas. --FFfangirl (talk) 19:17, September 23, 2016 (UTC)

Hey! Thanks for the suggestion. I completely agree with you, I think it'd be really neat and I know lots of wikis that already do this. Portable Infoboxes make it extremely easy as well. I think it'd be worth bringing it up here, where I'm going to start discussing new character infobox features anyway (now that most character infoboxes are converted).--Magicite-ffvi-ios.png Technobliterator TC 19:21, September 23, 2016 (UTC)

You're welcome! I'll place my suggestion on the forum and expand on it a little! --FFfangirl (talk) 20:57, September 23, 2016 (UTC)

More about tabbers[edit source]

Looks like some users are replacing tabbers with tables and this is good. But while this is not possible for every article, even for a small percentage of them will require time. With about 600 more articles to check and the FFRK articles to restyle, I don't have such time. Now, even you were trying the table way so what should I do? Change edit pattern or stop (now the pattern is "do-as-many-as-possible")?
TTFan from JP (talk) 13:49, September 28, 2016 (UTC)

Don't worry about checking every single one. A lot of them are enemy pages and I'm getting to those on my own - that'll reduce the number of articles with tabbers by a massive amount. At this point, I'd say you can take a break. You've done a fantastic job so far.--Magicite-ffvi-ios.png Technobliterator TC 14:10, September 28, 2016 (UTC)
Thank you very much. Anyway I don't like to leave a job unfinished, but for a while I may stay focused on FFRK. By the way, there are known issues about the "cellpadding" code? Today I replaced one used to create a table with the table code. It is on "Aquapolis" article.
TTFan from JP (talk) 14:23, September 28, 2016 (UTC)
Your edit on that page was good. And don't worry, again, the job will be mostly finished once I've sorted out tabbers for enemy templates.--Magicite-ffvi-ios.png Technobliterator TC 14:35, September 28, 2016 (UTC)
I would not use Intangir Bot in this situation, by now I met several different way of coding tabbers, all working of course. And Intangir Bot cannot discriminate between cases where to use divs or semicolons, or do it can? o_O Now I'm going to sleep, next time, if there is the chance, I would like to drop you an idea about a subject like 0-Images, creepy isn't it? Just in time for Halloween ; )
TTFan from JP (talk)
Intangir Bot can do it fine if programmed properly, and the enemy pages are way different than the ones you've come across.--Magicite-ffvi-ios.png Technobliterator TC 14:59, September 28, 2016 (UTC)

A bit out of topic, is about galleries. I already wrote you to take a look into my SandBox under the section Gallery a bit before, but today I updated it. This time bare galleries are wrapped into bare divs. What do you think of the result? Is it the same on mobiles?
TTFan from JP (talk) 14:12, September 29, 2016 (UTC)

Hello Techno. A bit late but I prepared a report about tabbers and what is left around on my SandBox. Please take a look at what I'm going to do by myself because are some heavy edits. First the two endless list of entries from D's Journal/People and Personae. Both are already long articles and will become a lots longer; on the other hand to me looks useless to subpage those even more so we will just stay with it. Then I will be back on FFRK to update table layouts with Man's help; there are two main categories of tables on several subpaged articles that I want to work on them. Lastly, List of Final Fantasy XIII/Emblems and the other five articles; I dropped an example into "Emblems" and already got complaints from the original editor but still didn't get a different propose back. I will leave this one last just in case, then I will proceed as for the example. Other than these, there are 22 enemy infoboxes, 49 articles related to Dissidia tabbed tables and two articles (Mognet (Dissidia) and Mognet (Dissidia 012)) that I don't know how to handle them. About infoboxes I suppose you can fix those or mark them as not relevant or not related to the tabber code. For Dissidia ones Catuse is looking after a template. I'm waiting for a word from you and not only about this, there are some sections still open in here.
TTFan from JP (talk) 10:09, November 3, 2016 (UTC)

Oh boy. Looking at D's Journal, it needs splitting somehow before anything is done about it. That is a longass page and I would recommend asking any Bravely Default player any way it can be split. SCM and Hexed played it and have good memory, I would ask one of them.
If the original editor complains and doesn't offer anything, then yes, just keep going how you were. Some of them just oppose change for the sake of opposing change. Everything else sounds good. Nice progress so far, but you don't need to wait for my permission for any edit.--Magicite-ffvi-ios.png Technobliterator TC 11:39, November 3, 2016 (UTC)

Redirect maker[edit source]

import re
regex = re.compile(r"{{A\|[^}]+}}")
with open('redirects-source.txt') as f:
    lines = f.readlines()
redirects = ""
for l in lines:
    s = regex.search(l)
    if s:
        anchor = s.group()[4:-2]
        redirects += """
{{-start-}}
'''""" + anchor + """'''
#getridofthisREDIRECT [[NAME OF PAGE HERE#""" + anchor + """]]
{{-stop-}}
"""
with open('redirects-tomake.txt', 'w') as f:
    f.write(redirects)

Store this script in the same folder as pwb.py (for me that's ~/wiki/intangir so I saved it as ~/wiki/intangir/redirects-generator.py). The string in the middle of the redirect is because otherwise this thing redirects your talk page, even though it's in a source tag. MediaWiki why are you so shit.

Before running for the first time:

cd ~/wiki/intangir
touch redirects-source.txt
touch redirects-tomake.txt

and then fill redirects-source.txt with the text from the page you're redirecting. Obviously if it's not based on {{A}} you'll have to change the regex (courtesy of SCM) but be wary of {{LA}}, since that usually means there's a disambig/parent where you're trying to write the redirect. If you're changing the regex you'll also have to change this line:

        anchor = s.group()[4:-2]

appropriately, it currently grabs all characters inside

|{{A|adsfadfasdfadf}}

but a single character off and it'll start grabbing the pipes and curly braces. That's bad.

Anyways, to execute:

python redirects-generator.py
python pwb.py pagefromfile -file:redirects-tomake.txt -notitle -safe

Safe prevents it from overwriting any previously existing pages with redirects (mandatory if you're using {{LA}}) while notitle prevents it from starting each page with anchor where anchor is the anchor it's being redirected to. Cat (meowhunt) 17:57, October 1, 2016 (UTC)


A beer for you![edit source]

L'chaim!

I have no idea how you did it, or how it can possibly have been as easy as you claim it was, but I salute you. Great job moving all those files! --CrappyScrap 23:22, October 2, 2016 (UTC)

Haha, that's bot magic for ya! It really wasn't difficult, there's loads of stuff I can do with it, and it's just going to keep making our lives easier.--Magicite-ffvi-ios.png Technobliterator TC 00:27, October 3, 2016 (UTC)

Wikihistory[edit source]

If you have a free moment you think you could add something on the making of the new skin for the Final Fantasy Wiki:A history? :) You'd probably be the best to write it.Keltainentoukokuu (talk) 18:49, October 9, 2016 (UTC)

Yeah, absolutely, I'll get to it tomorrow, thanks for reminding me. Sorry I haven't been doing much this past week, been busy with things such as cleaning up the R&C wiki. Hopefully this week is less hectic and I'll be able to properly start on that massive enemy template project!--Magicite-ffvi-ios.png Technobliterator TC 21:22, October 9, 2016 (UTC)
Cool. :) And hey, wiki-work should be more like, if you have free time thing, than an obligation. But I know you want it all nice and done before FFXV hits.Keltainentoukokuu (talk) 08:38, October 10, 2016 (UTC)
Added! Just needs a screenshot or something of the skin. And yeah, I agree normally, but like you said, I just want to have most things fixed for FFXV's launch to make it easier to sort the content out. We currently have around 2 million page views weekly, I don't know how many we'll get when FFXV launches, but if I were to guess: exponentially more. Would rather code is cleaner and works, and the new editors who will show up have a better structure to go on.--Magicite-ffvi-ios.png Technobliterator TC 11:35, October 10, 2016 (UTC)
Yeah it might be big. I wasn't around for FFXIII release (I joined to edit stuff for that game actually after I had played it) and the original FFXIV was a bit of a failure to say the least...and I think people were going for FFXIV-exclusive wikis for that one too, at the time. Going to be so annoying for spoilers but what can you do. I'm just not going to go to Recent Changes!Keltainentoukokuu (talk) 17:01, October 10, 2016 (UTC)
Yup, I wasn't around for either of them either, but the stats show that was apparently when the wiki peaked. It'll probably do even better now mobiles exist, and if it's really good, the wiki's page views will probably remain higher for a good while. That, and lots of new editors that I want to be able to turn into permanent contributors. I probably won't look at it either, luckily the AbuseFilter is good enough that it'll catch most vandalism we end up getting.--Magicite-ffvi-ios.png Technobliterator TC 19:04, October 10, 2016 (UTC)
That's our peak? Would not have guessed. The wiki is sooo much better now than when I first joined too. Guess I joined for the FFXIII peak...didn't really get the story so I wanted it explained, and then thought I could improve on it. Since then always tried to have story sections that explain properly what happens because that's what I wanted out of the wiki originally.
You sure got your work cut out for you for the next 50 days if you want to get the infoboxes done before that. It's going to be a huge improvement though!Keltainentoukokuu (talk) 21:06, October 10, 2016 (UTC)
Absolutely, it's improved a lot even since I've been here. I think you're definitely responsible for a lot of the big improvements in article writing quality, so I give you props for that!
And yep, I do. Which is why I'm trying to get a bot to automate it. If I can't, well, I'll just do about 3-4 game's enemy infoboxes manually, and then it won't be so weird when I set it up for FFXV. Then I can automate the process for the other games later.--Magicite-ffvi-ios.png Technobliterator TC 21:13, October 10, 2016 (UTC)
ACRudeBox.PNG
Technobliterator.png

Create stats template[edit source]

(function(){
  var wikitext = "\n" + editform.value;

  var codename = "";
  var infoboxfirstline = "";
  var infoboxlastline = "\n}}\n";
  for(var x in rel) {
    infoboxfirstline = "\n{{" + x + " Enemy\n";
    if(wikitext.indexOf(infoboxfirstline)!=-1) {
      codename = x;
      break;
    }
  }
  if(codename=="") return;


  var infoboxSplit = wikitext.split(infoboxfirstline);
  var beforeInfobox = infoboxSplit.shift() + "\n{{Enemy";

  var infoboxSplit = infoboxSplit.join(infoboxfirstline).split(infoboxlastline);
  var infobox = "\n" + infoboxSplit.shift();
  var afterInfobox = infoboxlastline + infoboxSplit.join(infoboxlastline);

  var firstheaderline = "\n==";
  var articleSplit = afterInfobox.split(firstheaderline);
  var intro = articleSplit.shift();
  var article = firstheaderline + articleSplit.join("firstheaderline");
  
  var newSection = "\n==Stats==\n";

  
  var fieldstokeep = [ "japanese", "romaji", "lit", "image" ];
  
  var fieldstorename = { enemy: "type" }
    
  var infoboxlinestart = "\n|";
  var infoboxlines = infobox.split(infoboxlinestart);
  var newinfoboxlines = [];

  for(var i = infoboxlines.length-1; i >= 0; i--) {
    var keyvalue = infoboxlines[i].split("=");
    var key = keyvalue.shift().trim();
    var value = keyvalue.join("=").trim();
    if(fieldstokeep.indexOf(key)!="-1") {
       newinfoboxlines.unshift(infoboxlines.splice(i, 1)[0]);
    }
    if(fieldstorename[key]) {
      infoboxlines.splice(i, 1);
       newinfoboxlines.unshift(fieldstorename[key] + " = " + value);
    }
    if(key.indexOf("location")!="-1") {
     newinfoboxlines.unshift(key + " = " + value);
    }//I decided I'm too lazy to do this properly*/
  }
  
  newinfoboxlines.unshift("release = " + codename);
  if(wikitext.indexOf("| enemy =")==-1) {
    var typename = document.getElementById("CategorySelect").getElementsByTagName("li")[0].getAttribute("data-name").split(rel[codename].full + " ")[1];
    if(typename!="Enemies") {
      if(typename=="Bosses") typename = "Boss";
      newinfoboxlines.push("type = " + typename);
    }
  }
  if(article.indexOf("\n==Formations")) newinfoboxlines.push("formations = true");
  if(article.indexOf("\n==AI")) newinfoboxlines.push("aiscript = true");

  infobox = infoboxlinestart + " " + newinfoboxlines.join(infoboxlinestart);
  
  newSection += "{{" + codename + " Enemy Stats" +  infoboxlines.join(infoboxlinestart) + "\n}}\n";
  
  editform.value = beforeInfobox.slice(1) + infobox + intro + newSection.split("| tab ").join("| sec ") + article;

})();

This doesn't convert completely. You'll have to sort out Locations, and maybe a few other things. JBed (talk) 22:42, October 11, 2016 (UTC)

This is perfect, thanks! Should be super helpful for converting, will still have to do Locations and probably also sort out images. Looking at it, I don't know if there's an easy way to rewrite it in python to make it compatible with pywikibot, but it's easily the best way to go.--Magicite-ffvi-ios.png Technobliterator TC 22:48, October 11, 2016 (UTC)

New enemy template??[edit source]

ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
Technobliterator.png
ACRudeBox.PNG
ACRudeBox.PNG
Technobliterator.png

Another weird bug?[edit source]

I just added some info to Final Fantasy Record Keeper characters/Final Fantasy IX, and now it's got a rendering issue. I can't find where things got fouled up, but I've seen this happen when things get over-long or an unsupported piece of code somehow gets into something. Can you help find the error, please? Swordzmanp236 (talk) 07:23, October 16, 2016 (UTC)

...Where is the rendering issue, exactly?--Magicite-ffvi-ios.png Technobliterator TC 09:50, October 16, 2016 (UTC)
Is already fixed. By mistake I left a div opened twice (or not closed if you prefer). Strange that the issue didn't become visible immediately.
TTFan from JP (talk) 09:53, October 16, 2016 (UTC)
Oh. Thanks, TTFan!--Magicite-ffvi-ios.png Technobliterator TC 09:55, October 16, 2016 (UTC)
You are welcome : ) As Man left written inside the page's code, banners on the right side got moved at the bottom of the page, below anything else. From history I found that the issue appeared when I restyled the page in order to remove tabbers, so I focused on that and in the end an open div section was causing the problem. One byte fix ^_^"
TTFan from JP (talk) 10:36, October 16, 2016 (UTC)

Possible phishing[edit source]

Today I received a strange Wikia's notification, in which was written that you had edited Intangir Bot's page. Before to click on any link in there I checked Intangir Bot's page by myself and were absolutely no edits from you. Reported edit's time and comment too were not matching anything in there. I can just note that before Wikia had changed the notification e-mails with that Fandom-related header, nothing like this happened to me. Just for your knowledge.
TTFan from JP (talk) 08:45, October 18, 2016 (UTC)

Next gen hardware article[edit source]

You were mighty quick to delete the Nintendo Switch despite the fact that info may still come in regarding this hardware.

Has it always been that "if no games announced yet, then we don't need xyz hardware"? I don't think it's going to be anything like that PlayStation program where they tried to get developers to write for any platform. From what information is out there, looks like it will be reliant on digital distribution (Virtual Console, etc).

If it's not yet worthy of a full article, how has the Wiki as a whole handled "coming attractions" pre-2015? Swordzmanp236 (talk) 20:02, October 22, 2016 (UTC)

There are no games released for the Nintendo Switch. That means it's not related to to the Final Fantasy series - which in turn means it doesn't belong on the Final Fantasy wiki.
When a game is announced for it, you can make the article.--Magicite-ffvi-ios.png Technobliterator TC 20:03, October 22, 2016 (UTC)
A little bit of follow-up here: Some bottom-feeding blog was reporting that Square Enix will not commit to the Switch platform until an installed base is established. Another source was saying that a Dragon Quest title may be coming. And a third source claims to have heard commentary that Final Fantasy XV is "unlikely" for the Switch. I don't like losing info here, so where could it go? Swordzmanp236 (talk) 22:57, October 22, 2016 (UTC)
Just put it in a user sandbox, there's no reason to put it in articles until we know it's related to the series.--Magicite-ffvi-ios.png Technobliterator TC 23:02, October 22, 2016 (UTC)
OK. I have a "Beta articles" folder under my personal sandbox (no direct links yet). Would you be able to recover that which was written and place it there? Swordzmanp236 (talk) 00:33, October 23, 2016 (UTC)
Done. One of these days, I think we need a better layout for platform pages, and probably an infobox for them. That said, we need that for all out-of-universe pages, honestly...--Magicite-ffvi-ios.png Technobliterator TC 00:36, October 23, 2016 (UTC)
Agreed. What do you think said box should include, and where should we open the dialogue so we can get good feedback? Swordzmanp236 (talk) 00:49, October 23, 2016 (UTC)
I intend to make a forum at Rin's Travel Agency about it, maybe sometime before the FFXV thing if I get chance. As for what the infobox could include, I imagine the parameters could be: Type (console/operating system/network), Developer, Release date, Media, First Final Fantasy title. For page layout, we have lots of options, but you might be able to come up with a better one for platforms than me.--Magicite-ffvi-ios.png Technobliterator TC 00:56, October 23, 2016 (UTC)

???[edit source]

ACRudeBox.PNG
Technobliterator.png

I've disabled sideicons in Monobook until I know why they look so awful. Admittedly fixing them in Monobook isn't a huge priority but if I knew why styles weren't working properly it would be an easy fix. Cat (meowhunt) 21:32, October 23, 2016 (UTC)

In between all of this, can someone run Intangir Bot to replace {{sideicon|Dissidia}} with {{sideicon|DFF2008}}? Even the template at the bottom of articles is sometimes outdated it too.
TTFan from JP (talk) 13:13, October 24, 2016 (UTC)
Running it now. In future, please use User:Intangir Bot page to make requests. Thanks!--Magicite-ffvi-ios.png Technobliterator TC 14:42, October 24, 2016 (UTC)
Need to get a bit more familiar with it. Anyway, did someone noticed that the [[Category:Pages with script errors]] yesterday was with more than 1,300 entries and today have just a bit more than 300 entries? Like for the new Gallery code, the Article Information box too doesn't display error messages, isn't it?
TTFan from JP (talk) 02:58, October 25, 2016 (UTC)
mmm... I'm looking in that category page a bit and maybe I can come out with more requests like the one above, but should I include even those that are very close to a typo too? For example "CCMLaak" that should be "CCMLaaK". And is it fine to drop all of them into Intangir Bot To-do list section?
TTFan from JP (talk) 10:13, October 25, 2016 (UTC)

Update[edit source]

I've put up a thread in RTA re: the hardware infobox. You're also quite welcome to check out the updates to that beta article I'm writing. Let me know what you think. Swordzmanp236 (talk) 22:40, October 23, 2016 (UTC)

I posted there just now, good that you made a thread. Just so you know in future, when making threads, it's normally best to post with solid proposals and examples so people know what they're getting, and have people discuss what they'd add/remove. It tends to get a better response that way if you start off decisive.--Magicite-ffvi-ios.png Technobliterator TC 22:46, October 23, 2016 (UTC).

I've got a template called Template:Infobox HW up in mainspace for you to look at. I need help adding the theatric elements (banner image, banner title, etc). Dammit, man; I'm a writer, not a programmer! Swordzmanp236 (talk) 02:13, October 24, 2016 (UTC)

Done, other than a couple changes I made, good job so far. I think it should be renamed to Template:Platform, but I would say the same about templates like "Infobox CVG"...so maybe I should move them all at once.--Magicite-ffvi-ios.png Technobliterator TC 07:48, October 24, 2016 (UTC)
Looks like we need a bit of image size control for these pages. The PlayStation image could be reduced to 50% of its size and still look good. Swordzmanp236 (talk) 16:59, October 24, 2016 (UTC)
Better idea would be to just split it into two images and separate using a gallery.--Magicite-ffvi-ios.png Technobliterator TC 18:43, October 24, 2016 (UTC)
Sounds good. Go ahead. And while we're at it, shrink the PocketStation, please. Swordzmanp236 (talk) 18:52, October 24, 2016 (UTC)
I have no idea what to do about that one, unless you want to just shrink the pixel size in GIMP or something.--Magicite-ffvi-ios.png Technobliterator TC 18:55, October 24, 2016 (UTC)
Don't know what happened there, either. Takes up a chunk of the desktop view. Shrinking the image to 50% of its native size should fix things. Swordzmanp236 (talk) 19:07, October 24, 2016 (UTC)
Even if I change or remove the pixel size attribute the image remain scaled to fit the horizontal width of its template, and because the original image is in portrait form it looks wildly enlarged. Is this a temporary bug or the only solution is to edit the original image adding more empty spaces on both sides?
TTFan from JP (talk) 02:27, October 25, 2016 (UTC)

RE: Project Page Proposal[edit source]

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