A useful python script Edit

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

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('', 'ab') as f:

Then run

python 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 Technobliterator TC 21:45, August 16, 2016 (UTC)

Some considerationEdit

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 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 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 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 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 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 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 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

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 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

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 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 Technobliterator TC 19:13, August 22, 2016 (UTC)


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 Technobliterator TC 16:14, August 21, 2016 (UTC)

A request. Edit

(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 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 Technobliterator TC 19:44, August 22, 2016 (UTC)

thanks Edit

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 Technobliterator TC 20:29, August 25, 2016 (UTC)

Marked image issues Edit

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 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


Image with transparent backgroundEdit

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 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 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 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 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 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 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 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 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 Technobliterator TC 10:52, September 23, 2016 (UTC)

FFRK character list redesign Edit

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 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 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 RequestingEdit

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
FFRK Shantotto
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.

Image galleries in infoboxesEdit

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
FFXIII-Lightning CG.png|Ex-Soldier
Lightning FFXIII-2.png|Etro's Champion
Lightning - LRFFXIII.png|Savior
|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)
|height=171cm (5'7")<!--DO NOT CHANGE HEIGHTS WITHOUT PROOF. Always cite your reference(s).--><ref name="ffxiiiscenulti10"></ref>
|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
|boss page=Lightning (Final Fantasy XIII-2 boss)
|other appearances=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 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 tabbersEdit

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 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 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 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 Technobliterator TC 11:39, November 3, 2016 (UTC)

Redirect maker Edit

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

Store this script in the same folder as (for me that's ~/wiki/intangir so I saved it as ~/wiki/intangir/ 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 =[4:-2]

appropriately, it currently grabs all characters inside


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

Anyways, to execute:

python 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

Beer FF7


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 Technobliterator TC 00:27, October 3, 2016 (UTC)


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 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 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 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 Technobliterator TC 21:13, October 10, 2016 (UTC)

Create stats templateEdit

  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;
  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 Technobliterator TC 22:48, October 11, 2016 (UTC)

New enemy template??Edit


Another weird bug? Edit

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 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 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 phishingEdit

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

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 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 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 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 Technobliterator TC 00:56, October 23, 2016 (UTC)



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 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

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 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" maybe I should move them all at once.--Magicite-ffvi-ios 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 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 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 ProposalEdit

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