User talk:SirKerfluffles

Adding png image links

We have a cool template that auto generates links for skill icons. That way, when Neople adds more skills, we do not have to change the skill table. For example,

{{ClassSkills|Male Spitfire}}
{{ClassSkills|General}}

Of course, it requires that all skills must use SkillPage template. Apparently, M. Spitfire has some extra skills so, I'm not entirely sure what do to about that. As for the armor mastery, you can put that in the JobDesc3, such as in Summoner.--Dfoplayer (talk) 12:09, 30 June 2015 (PDT)

Ok then, that sounds great. So if the template is used, does that mean the wiki automatically loads the png files as well? Because if so then I can just skip the ones I haven't gotten to yet and maybe go straight to that. (Sorry for the late reply. I got super busy moving and didn't get much a chance to get on. I'm just gonna assume if no reply you didn't get this and just experiment later. --SirKerfluffles (talk) 23:44, 5 July 2015 (PDT)

Well, the {{ClassSkills and {{IconLink just appends .png after the Skill name, like Giant Weapon Launcher becomes File:Giant Weapon Launcher.png. So, if you load the {{ClassSkills on to the classes pages, you will see red links and easily find the missing icons. Of course, someone still has to put {{Delete on to the gif/jpg. --Dfoplayer (talk) 07:36, 6 July 2015 (PDT)

Ah, yeah it makes sense that the wiki itself would still need the files to reference. Would have been pretty fancy though if the thing was ripping them from the game files. If I have some time I'll start working on that again tonight or tomorrow. I really want to get it done. I hate having projects hanging suspended in time like this. --SirKerfluffles (talk) 07:50, 6 July 2015 (PDT)

Awakening Skills

Awakening Skills are categorized in <Subclass> Awakening Skills and <Subclass> 2nd Awakening Skills. If need to be, I can add them to the Metastasis page so you can confirm they are in the right place. --Dfoplayer (talk) 19:35, 7 July 2015 (PDT)

Hmm, well it's up to you. Pretty much my plan was to try and finish up the image uploads of classes that are out (probably skipping F. Slayer for now) and head onto looking into the categorization so the auto load formats can be inserted into the class pages. It'll probably become more clear once I actually look at how the template works, but overall it would probably be nice to have the awakening skills on the metastasis page since the page now shows the difference between the Template/non template pages. It'd make it easier to keep track of what's needs to be done / show progress of the project to anyone who's interested.

Since this is related, how are the skills on the Metastasis page generated? I finally decided to go in on that M. Fighter section which I still kinda don't wanna touch, but it's just about the only section left to do. The naming schemes are looking super messy in there, with a lot of variations on how to reference the male version of the skill (like (M) at the start, but also at the end, and sometimes with spaces or none in between the (M) and the skill name...or also M. [Skill Name] or [Skill Name] (Male)...and for Brawlers it even goes [Skill Name] (Male Brawler). Some standardization would be nice. It'd make things easier if there was a clear way to sort out which skills should be where, because some skills in there are referenced several times or are loaded where they shouldn't be (like Knee Kick being in the grappler section when it's just a general M. Fighter skill). Additionally the female versions of the skills that share the same names are sometimes loaded as well as separate things, but sometimes they just straight up show a duplicate of the female version (with the image and page link). I might also figure all this out when I start categorizing, but some tips/guide couldn't hurt.--SirKerfluffles (talk) 20:32, 7 July 2015 (PDT)

According to Everspace we should probably use [Skill Name] (Male/Female) as the standard. As I explained here, DPL extension looks up categories to auto generate the list for skills. As long as Template:SkillPage correctly auto-categorizes, we should be fine on skill categories. Unfortunately, I do not know any auto categorize extension that can categorize those .png images. --Dfoplayer (talk) 22:40, 7 July 2015 (PDT)

Do you mind removing unused categories?

Hey, if you're going to use the new skill pages, would you mind removing any unused categories? Arrol (talk) 19:09, 7 August 2015 (PDT)

You mean like "Class2" and "Type3" and those ones? It's an option, sure. Is there a reason? --SirKerfluffles (talk) 19:16, 7 August 2015 (PDT)

Well, my mind is blown that you don't need to have the things like |Video2 to have the video tabs showing. Trade off of making the page text cleaner, but also slightly more difficult for people to just stuff in like the scenario I have in my head when this is all done. And just FYI, if it's bothering you that I tend to leave blank atrributes from the skill page template in, I'm doing it with the intention of making it easier to get more people to come in an just update info. Ask for elaboration if it's an issue and we can talk it out. --SirKerfluffles (talk) 20:13, 7 August 2015 (PDT)

So I've tried it out for a few, and I'm not really liking deleting the stuff. There's a lot of stuff I see becoming messy in the future when they're deleted. Like for one, I just keep thinking that if suddenly there was a skill change or something (say suddenly skills moved around and require prerequisite skills though they didn't before), it'd be more difficult to just make the change since you'd probably have to go pull up the skill template page again (or another page you KNOW has a prereq) to remember the syntax. Or, for someone who hasn't edited the pages before, maybe get confused and have to start asking around for info that should have been pretty obvious. Also, say someone adds a video2, and the naming tab. Since the attributes apparently don't have to be in order, they could end up adding the video at the bottom of the code part (below the skill table) or something. And in this case it'd be harder to find and change stuff since you'd have to go around searching for a particular attribute on every page. Overall I see deleting the blank attributes leading to huge work deterrents. So unless you can explain why it's beneficial to delete them, I'm just gonna leave them in. --SirKerfluffles (talk) 09:31, 8 August 2015 (PDT)

Doesn't the page for the template itself have a tutorial for new users? Arrol (talk) 10:58, 8 August 2015 (PDT)