Inkipedia:Ink Pump

The Ink Pump Welcome to the Ink Pump. Similar to Wikipedia's Village Pump, the Ink Pump serves as a general place for the Inkipedia community to discuss the wiki as a whole, whether it be ideas, proposals, technical issues, or notices.

Remember to put new discussion sections at the bottom of the page.

You may also wish to view recent talk page discussions.

Archives available here.

Automatically resetting the stage timer
The stage countdown timer on the front page currently requires you to reload the page every time the timer runs out. Perhaps we could fix this by putting the timer in an iframe, and then calling document.location.reload when the timer runs out. --Xenon (talk) 21:20, 9 June 2015 (UTC)
 * There's no need for that, a function can be written so the timer resets when it runs out. I do it if you want. AbelToy (talk) 10:11, 10 June 2015 (UTC)
 * If either of you want to give it a go and post results here, that would help a lot :) - Kjhf (Talk | Contribs) 10:43, 10 June 2015 (UTC)
 * Did it. You can see it here in action: https://jsfiddle.net/tsenazgw/7/ - in order to use it, copy the Javascript code (the text below) into Common.js, and the HTML code (the text above) wherever you want to use the countdown. This countdown is specific for the stages, and will countdown to the next stage change automatically without needing to refresh it. AbelToy (talk) 12:43, 10 June 2015 (UTC)

Templates Way Too Big!
I think the templates' box size is way too big. How 'bout resizing it?

--marikdff 02:38, 10 June 2015 (UTC)
 * I agree - did you have in specific ones in mind? Either way, they should definitely be shorter in height. ~Super Hamster  Talk 03:18, 10 June 2015 (UTC)

For example, the Deletion Template: http://splatoonwiki.org/wiki/Template:Delete There is some space at the top and bottom. How about like this? http://www.mariowiki.com/Template:Tobedeleted Oh and you could probably put a squid ghost that appears after they get inked at the right. --marikdff 03:29, 10 June 2015 (UTC)marikdff

Clean up Ink pump
The this is/was an excellent idea, but it is getting a bit large. Perhaps every couple of weeks an admin should clean up old, irrelevant discussions. Seeing them is nice, but gets a bit tedious when looking for new stuff. Einstien74 (talk) 03:36, 10 June 2015 (UTC)
 * Was planning on doing this soon-ish. Do we want to leave discussions up for, say, seven days before archiving? ~Super Hamster  Talk 03:39, 10 June 2015 (UTC)
 * Sounds good to me. you're the admins Einstien74 (talk) 05:29, 10 June 2015 (UTC)
 * Sounds good here. I suggest you start with a hub page at Inkipedia:Ink Pump/Archive and archive under Inkipedia:Ink Pump/Archive/1 or something similar, maybe with a date stamp. Kjhf (Talk | Contribs) 10:42, 10 June 2015 (UTC)
 * I say we archive stuff based on size, not so much time. For time, we'd have to keep track of when everything was posted. For size it's a lot easier. Stuff like "do we have 30 sections? Let's archive the oldest 25." – EspyoT 12:35, 10 June 2015 (UTC)
 * Maybe a mixed idea. At the worst, all sections with no replies in ten days can be archived until there are only five sections left.   A section with one reply could be in fifteen, two in twenty-five, etc.  Or at least something like that.  --SgvSth (talk) 01:12, 12 June 2015 (UTC)

Page was getting long, so I went ahead and created Inkipedia:Ink Pump/Archives, and archived the first 25 discussions to Inkipedia:Ink Pump/Archives/1. I randomly set the default number of discussions per page to 25, but that can be changed. ~Super Hamster  Talk 03:48, 22 June 2015 (UTC)

Speed Runs
The speed running community for Splatoon is already speeding ahead with interesting strats. I'm wanting to do a page on runs/strats/times but don't know where to put it - Pyrii (talk) 05:23, 10 June 2015 (UTC)
 * I assume Speed Runs of missions and tips for multiplayer stages will go in their respective pages. If there's something specific to speed runs such as TAS then perhaps make a separate article for that. - Kjhf (Talk | Contribs) 10:36, 10 June 2015 (UTC)
 * Sharding information which might seem useful seems counter-productive. Especially since strats used for speedruns won't neccessarily be used for normal playthroughs. There's also the need for a specific article to mention types of speedruns and current times or where to find them. (Currently speedrun.com) - Pyrii (talk) 18:30, 10 June 2015 (UTC)

Splatoon OST
Reddit user yocowthegreat ripped the entire Splatoon OST from the Squid Beatz minigame (unlocked with Amiibo challenges). Here's the YouTube playlist. "Music" page? Is there a way to embed YouTube videos? This website generates embedded player codes. If there is, maybe we could use the "Button + Volume" player type for the music page? --NefariousSquid (talk) 06:36, 10 June 2015 (UTC)
 * The uploader has disallowed embedding - Pyrii (talk) 16:12, 10 June 2015 (UTC)
 * Maybe we could link to the videos? ~I shall splat thee!~ KamuiKagerou77 (~ discussion ~) 23:58, 11 June 2015 (UTC)

Maintenance Page
I created a maintenance page as a hub of links useful for ongoing maintenance or not knowing what to do. -Kjhf (Talk | Contribs) 10:45, 10 June 2015 (UTC)

Some images
A reddit user made an album with a lot of images. We can use those on the wiki, if they aren't already here. – EspyoT 13:11, 12 June 2015 (UTC)
 * I think we have most/all of those already. We're displaying some of them on the Main Page ;) File:CallieArt.png - 13:53, 12 June 2015 (UTC)

The old Wikia site
I added this on ShrimpPin's talk page too, but just in case he doesn't see it, I'll post it here too: The edits to the main page on the old Wikia site, telling viewers to come here instead, seem to have been reverted. We should fix that! (Or even better, delete the entire site if possible?) The old site always shows up in google rather than Inkipedia. :( Thanks! --Eli (talk) 11:33, 14 June 2015 (UTC)

Audio player
I'm uploading compressed music from Splatoon. Admins, are you able to add a .ogg audio player extension to Inkipedia? --NefariousSquid (talk) 16:05, 14 June 2015 (UTC)
 * Admins can't add extensions but Prod can. Will prod him for you. I created a music page in response to this idea previously.
 * 16:30, 14 June 2015 (UTC)
 * This extension seems to have a lot of annoying dependencies. It'll take some time to get it working. -- Prod (talk) 18:24, 21 June 2015 (UTC)

Links
Is it possible to make a word link to a spot on the wiki without the word saying what page I want it to go to, like on the old Wiki site? (Ex. if something says "Blaster" and I want it to got to the blaster category page and not the Blaster weapon page and I don't want it to say Category:Blaster like on the weapons list page) --Jer455 (talk) 08:52, 16 June 2015 (UTC)
 * Of course. Blaster will result in Blaster. ZOMG NEW WEAPON will create ZOMG NEW WEAPON – EspyoT 09:08, 16 June 2015 (UTC)
 * It's the same markup as the old wiki site. In this case, Blaster results in Blaster. 11:33, 16 June 2015 (UTC)

Basics
Hold on, is there any page with basic game info/mechanics? (What button does what? When does my ink refill and when won't it? What does the sensitivity slider actually adjust?) --Tyroney (talk) 17:53, 16 June 2015 (UTC)
 * I did just find Options, but that's only part.--Tyroney (talk)

Naming and Template Conventions
While putting together Template:Ability, I had to jump through a very ugly hoop because there's no consistent naming convention on the Ability icons. A similar situation exists with all of the Gear imagery. I used some conditional evaluations like this:

[[File:

...
 * ]]

But let's say for a moment that all the Ability icon names followed the format of  so that, in this example, we'd be working with Ability_Damage_Up.png and Ability_Opening_Gambit.png. That being the case, since MediaWiki treats spaces and underscores the same in filenames, the 24-lines-of-conditional-code block can be condensed down to a single line:



That's a heck of a lot nicer, right? This is one reason naming conventions are important. This would also vastly simplify the markup of List of gear in Splatoon, since image filenames could be derived from the Gear name. (Also, that "Gear" oughtta be capitalized in the article title, but that's a different battle altogether.)

I noticed something similar happened with the brand templates. I suggested something along the lines of, which would allow for things like   and. What wound up getting implemented instead are nigh-identical templates for every brand, resulting in markup like  and. This is a problem for two reasons: 1) it unnecessarily bloats our template namespace (though that's largely a matter of taste), and 2) if any changes are desired, they have to be made to every brand template instead of just the one.

It's not my intention to barge into the wiki and start calling the shots, but I do want this wiki to be the best it can be, and right now I'm seeing some things going in a direction that I don't think is best.

--GuyPerfect (talk) 12:26, 17 June 2015 (UTC)


 * I'm inclined to agree on your points: we really should have consistent names for templates and images. Yes and yes.
 * However, the template usage, I don't agree so much because of four reasons:
 * 1. Editors are more likely to type what they mean.
 * Editors would not only have to know that the brands template exists but they also would have to look it up for its usage, for example is it or  or maybe even  ?
 * It's much more intuitive to have Skalop.
 * 2. The template code, though wasteful, is much more manageable and easy to edit by anyone.
 * For a violation of this, take a look at the switching template Navbar.
 * 3. Redirects only work to whole templates, not ones that switch on parameters.
 * This means could redirect to  but not the other way around.
 * 4. We discussed button templates before and decided ZR and the like is better than say
 * You raise a very good point on consistency of file names. It was my intention to copy-paste code for each template to be as identical as possible. When we can do that, we can make a template for all the templates and then only change that one when needed. Wasteful? You decide.
 * We don't have a style guide for this yet, it would be great if the commnity decides on this one.
 * 14:54, 17 June 2015 (UTC)


 * There, I just modified User:GuyPerfect/Sandbox to use some templates instead of hand-coding everything. Check the source markup--naming conventions made it easy! While I was working on that, I made an edit to Template:Ability to add the icononly parameter. While I ultimately opted to include the text in the Ability column, the fact remains that I was able to add the option for all 24 Abilities without going through and modifying 24 templates... So I'm really gonna have to stand by my earlier recommendation of using things like  and   over things like   and , respectively.
 * It also occurred to me while setting up my sample table that ambiguity could severely cripple the naming convention of templates if, in my specific example, something like  continues to be used. That template currently renders the amiibo brand, but there's no reason it couldn't also be meant to refer to something like the type of merchandise or the nature of unlockable content. Splitting it up as ,   or   would bypass that problem altogether. One alternative is to modify the offending templates on a case-by-case basis, such as  , but doing that suddenly breaks all content referencing the first template that happened to come along. Another might be to add new templates such as  , but then that potentially sacrifices consistency with other templates depending on the order they were implemented. If we can establish a convention at this point that sort of future-proofs this kind of problem (and we can), I really think that's an avenue we should go down.
 * On the topic of requiring editors to be familiar with the templates, that's how it is on every other wiki I've visited. What I can say from experience is that when I'm new on a wiki and want to be consistent with existing content, I just look at the existing content to see what it does. It took me a few edits on Bulbapedia before I realized that I was supposed to say  instead of  . We can easily educate new users with a simple style guide and list of common wiki-specific templates.
 * --GuyPerfect (talk) 17:37, 17 June 2015 (UTC)


 * I agree that naming conventions would definitely help to streamline future template possibilities and I would be in favor of establishing some guidelines over at Inkipedia:Policy (specifically at the to-be-written Inkipedia:Policy/Image_Guidelines). Of course, that's something to talk to the Admins about. I'm also in agreement that we should try to limit our template count (e.g.  vs  ), although I think that we need to be sure to include the proper use and documentation notes before implementation, otherwise it makes it even harder for new users to use (or if needed, modify) the more complex templates. --sunmarsh  ( talk )  00:48, 20 June 2015 (UTC)

Story details?
I think there should be a place where history, lore, and all spoiler-y Hero Mode details should go. Should we make a page called "Story" or "History?" Also, I feel like there should be a conjectural name for the Inklings' planet. When talking about the Great Turf War and rising sea levels, the entire planet should be discussed, and not just one city, Inkopolis. Should we make a page called "Earth," because the planet technically is Earth? Feedback is appreciated! -  Shrimp Pin  13:57, 20 June 2015 (UTC)
 * I was just thinking about something of the sort for Pikipedia. We have a page with the policy on the canon content, but it'd be best to have one about the policy, and one that explains the canon. Long story short, I'm putting this idea on the table: consider a page that describes what is canon and what is not. Perhaps combine it with or make it a sister of a page that describes the lore. Either way, if it doesn't go that deep, I say the story be put on the actual game's article. – EspyoT 08:16, 22 June 2015 (UTC)

Policy pages
We've got at least four new policy pages made in the last 24 hours.

Kjhf has done a great job creating the following pages (shoutout to him!), which should be reviewed by editors. Feel free to make comments for changes or suggestions on talk pages (I've already done so for the blocking policy):
 * Inkipedia:Policy/Signatures (talk)
 * Inkipedia:Policy/Blocking (talk)
 * Inkipedia:Policy/Rights (talk)

We've also had a few rumors and leaks going around the 'net about Splatoon. We do need to have a firm policy on how we cover these, which was discussed a bit on our Skype chat. I've drafted one together, so do also review it and comment if you have any thoughts: Inkipedia:Policy/Rumors and leaks (talk).

Thanks! ~Super Hamster  Talk 03:52, 22 June 2015 (UTC)

Leaked Information
New never-before-seen pictures and information that is on the Splatoon game disc were leaked. I was wondering if we could possibly add some of the pictures and information to some of the pages and put a thing at the top of a page or seciton (like if the page/section is a stub-type thing) if it deals with rumors or things that havent been revealed yet, or even make an entire page for rumors about possible new stages and weapons that haven't been confirmed yet. You can find the leaked pictures and information (Here) and (Here). --Jer455 (talk) 06:14, 22 June 2015 (UTC)
 * I was asking the same thing yesterday- unfortunately, this would violate Nintendo's copyright laws and that's something we really don't want to do. Even though Gamexplain and basically every other news source are covering the leaked content, we can't legally do it until is is officially confirmed by Nintendo. We probably wouldn't get in trouble, but it's just a good idea in general to stay within the law. -  Shrimp Pin  13:17, 22 June 2015 (UTC)
 * Splatoon of America did retweet info about the leak, and I remember someone in the chat mentioning it has since been confirmed - I take this as being acceptable at this point? ~Super Hamster  Talk 13:48, 22 June 2015 (UTC)
 * Kinda weird that they'd retweet it. But in this case, yes. I think it makes sense to add it. Oh, I'd recommend saving the tweet as well. I have a feeling it'll be removed soon enough... – EspyoT 16:41, 22 June 2015 (UTC)
 * *facepalm* I just realized it's a fan account. Nevermind on that, then. ~Super Hamster  Talk 16:43, 22 June 2015 (UTC)
 * According to the (new) leaks policy as it stands, leaks can be covered. But the discussion/problem we have is how the leaks are obtained. If it's done illegally (datamining) then Inkipedia might be accused of hacking. This is what the policy is aiming to protect: obviously we want to keep the wiki in good standing. That said, if we can write about the leaks by only using external references so as to not be portrayed as the people who did the leaking/hacking, then I can't see anything wrong with that. It would be akin to journalists being tried for the stories they report upon. 17:25, 22 June 2015 (UTC)
 * From the context of being respectful to Nintendo's wishes (meaning they can announce things on their own timetable), I feel we should still refrain from going into particular detail for information dug up through unauthorized means. For instance, I'm all for covering that information was discovered, but I really don't think the full details of that information (like all the weapons, details on Rainmaker, etc.) belong on this wiki. Someone can look it up if they want, but I don't want Inkipedia to be the source of spoilers or what-not. --GuyPerfect (talk) 17:29, 22 June 2015 (UTC)
 * I like this idea, and I think it's a fair one. Cover the fact that the leaks occurred, and what type of content was leaked, but avoid actually posting what was leaks (weapon details, images, etc.). ~Super Hamster  Talk 17:33, 22 June 2015 (UTC)

Inkfest?
Sorry if I'm missing something obvious, but what is Inkfest?