Funkipedia Mods Wiki:Style Manual

The Funkipedia Mods Wiki's Style Manual is a guide on how to properly edit, format, and create pages so that poorly done edits may get reduced. It is expected that all users should read it and follow through, as it sets the base standards for page quality. If there is an edit or something similar on a page that violates these guidelines, don't be afraid to fix it.

It is important to note even if some editors don't know much about editing, we still suggest them to try it out, as long as they follow these standards and the basic wiki rules that are set in place. Assuming that edits were made in good faith, mistakes can always be reverted, undone and/or corrected.

Despite these not being listed in the rules, they will still be enforced as if they were rules, which means warnings and even blocks may occur if these are violated with malicious intent (i.e. vandalism).

If there is a gap in this style manual, refer to Wikipedia's style manual, but be aware that some guidelines here may contradict those shown on Wikipedia.

Warning For Mobile Users

A note for mobile users of Fandom is that the limitations of portable Fandom can make it awkward and troublesome for anyone to make some of the more complicated or generally larger edits. Downloading mods and getting assets could also be an issue. If any editor is a mobile user, use desktop view to ensure that all features are available and try to limit edits to simple ones, such as grammar/typo fixes. For the best experience, it is strongly recommended that edits are made on desktop platforms such as a PC or a laptop.

Style Manual

Language, Grammar, & Dialect Formatting Disambiguation Pages Sprites Audio Programming Galleries Navboxes Categories Misc Gameplay This section concerns the common writing practices of the wiki. # Title Description Examples 1. Language All pages must be written following the style of American English (apologies to British English writers). Writing words in the style of British English out of habit will not be punished, but it will be fixed. This is to ensure that the writing on articles remain consistent. Users of other languages are encouraged to use translating tools such as translation software to read the pages, but do not copy machine-translated text from a foreign wiki to the English wiki or vice versa. If there is a mod that uses some foreign language (i.e. text/audio dialogue), then they should be translated to English as accurately as possible when writing an article page for that mod. English translations should always be written out in parenthesis. Favorite over Favourite Gray over Grey Paralyze over Paralyse Defense over Defence Color over Colour Canceled over Cancelled Si ese chico está haciendo esos rituales satánicos de nuevo, lo juro por Dios... (If that guy is doing those satanic rituals again, I swear to God...)[?] 2. Third Person Do not use 1st person pronouns like "I" or "me" or any words that give attention to the editors. This also includes writing hidden notices with their username. Do not use 2nd person words like "you" or "your" when referring to readers either. When referring to people who play the game, simply refer to them as "the player/players". This does not apply to quotes. Whitty faces toward us when doing his down singing pose. Whitty faces toward the player when doing his down singing pose. 3. Neutral Point of View All articles should be as neutral as possible. Do not inject personal opinions onto a page or state things in an opinionated manner, as this wiki is informational and is not meant to contain the personal opinions of one or more people. Also, do not state things that are subjective such as a song being difficult, or something being bad or good as these are unimportant and change with the eye of the beholder. After the cutscene, one of the hardest songs of the mod begins.[?] After the cutscene, the final song of the week begins.[?] 4. Lists Lists of three or more things do not require a serial comma (before and/or), though if omitting it causes ambiguity (e.g., Boyfriend raps against opponents like Whitty and Pico), include it or reorder the items. One, two and three[?] over One, two, and three. One and two, three and four, and five and six[?] over One and two, three and four and five and six. 5. Profanity/Swearing While yes, this wiki is for a mature audience, swearing constantly in an article when there is no reason to is just unneeded and looks unprofessional to the point where the edit may count as vandalism. The only exception when such vulgar language is permitted is if it is related to the page subject (i.e., in-game dialogue or cutscene dialogue). In these circumstances, profanities must be written uncensored. On the other hand, slurs must be written censored (e.g., c*** or r*****). "It was a shitty situation" "It was a bad situation" 6. Keep it Simple Strive to make the wiki understandable for everyone without having to refer to a dictionary every other sentence. Use simple descriptions, understandable vocabulary, and easy-to-follow structuring that smoothly leads one sentence to the next. This does not mean editors cannot be descriptive or use synonyms to avoid repeating the same word over and over but remember that word choice matters. Simplicity goes a long way to make reading through an article more enjoyable, but variety helps make it interesting too. Just don't use words that everyday people don't normally use. It's that simple. "Julian has no monetary banknotes." "Julian has no money." 7. Formal Writing In almost all situations, formal language is expected to be used when writing or describing things as the wiki aims to be informative. However, contractions are generally acceptable. Don't make sarcastic, joke, or generally satirical or informal edits either. However, some exceptions do apply, like character descriptions on the character page. This wiki is used by millions constantly and should keep its writing understandable and professional. We are not asking editors to speak like a scholar from the 1800s, however, we simply want them to speak as they would to their teacher or parents. Nitty Gritty is a goofy-looking version of Julian that was drawn as a response to some troll.[?] Nitty Gritty strongly resembles Julian because he was made as a coping mechanism for the leaks.[?] 8. Writing Numbers Numbers 0-9 should be spelled out, unless they involve decimals or if they are used within parameters of templates (e.g., bpm, scroll speed, etc.). Otherwise, they should be written in numeral form. Furthermore, commas should be used as thousand separators for numbers 1,000 and above. Periods should be used as decimal points. seven over 7 2.6 over two and six-tenths 180 over one hundred eighty 303,800 over three hundred three thousand eight hundred or 303800 9. Dates Dates, especially release dates listed in ModInfo infobox and Credits templates, are to be written in this format: [Month] [Day], [Year]. 16th February 2021 February 16th 2021 February 16th, 2021 February 16, 2021 10. Possessive Forms For possessive forms of words ending with a pronounced s, including plural nouns, do not add an s after the apostrophe ('). FNF Rivals's characters are Newgrounds-based. FNF Rivals' characters are Newgrounds-based. 11. Punctuation in Parenthesis When writing a sentence in parenthesis to add onto an existing sentence, the period is added outside. If a sentence in parenthesis stands by itself, add it inside. While KB (the robot hidden in QT) is a parasite connected to QT's body, they have a close relationship that is like an overprotective older brother and a younger sister.[?] Monster appears as a multi-armed, spider-like creature hanging from the ceiling above Boyfriend's bed. (He still retains his distinctive lemon-shaped head, however.)[?] 12. Punctuation in Quotations Commas and periods should be placed inside of quotation marks, while colons and semicolons are to be placed outside. Question marks and exclamation points are placed inside unless it applies to the whole sentence. Sunday's teaser quote, " one can only stay wealthy under the exploitation of the working class," is a reference to Karl Marx. Michael Jackson performs his alternate up pose whenever he utters sounds like "WOO!" or "OW!" during Lore (Lock-On Remix). 13. Avoid Improper Writing Writing pages in ways like this lowers the quality and makes it look incompetent, unless such writing is used in the form of in-game text/audio dialogue. Also, please do not use Zalgo text as it can be hard for readers to read the words clearly. The only exception is when it's used in-game in the form of TEXT dialogue, not audio. Writing in all caps when speaking normally: INNOCENCE DOESN'T GET YOU FAR! Using emoticons/emojis: :) :( >:) or :3 Overusing punctuation: like this!!! or this??? Abbreviations: srsly or u r n idiot Not starting with capitals: i am saster Capitalizing every word in a sentence: And Why He Ourple? w-wwwwow pibby-y-y text s-s-so cooOool over ẅ̵̞o̸̬͝w̵̪͐ ̵̘̚p̸̲̀ï̵ͅb̴͎͠b̵̕͜y̷̞̎ ̵̜̏t̶̟̂e̸͔̎x̵̫͝t̸͍̆ ̷̡̽s̴͖͋o̵̲̾ ̸̓ͅc̵̮̍o̶̙̔o̸̮̔l̷̅ͅ This section concerns the creation and structuring of article pages. # Title Description Example 1. Minimum Criteria In order for a Friday Night Funkin' mod page to be created, the mod needs to show proof that it exists or is in development. Normally this is usually in the form of a download link, including but not limited to GameBanana, GameJolt, Google Drive and MediaFire. These should be listed below the "Download Link(s)" section of the page. If there is an official social media link that is affiliated to the mod (i.e. YouTube or X (formerly known as Twitter)), then such links must be included into the mod's wiki page. An unreleased mod page may be created as long as there's an external link to show that the mod exists or is in active development. If the unreleased mod gets canceled and its mod page has little to no content provided, it will be marked for deletion, regardless of its page quality. The same can be said for mods that show no external link to prove of its existence. Furthermore, the page size must at least 1,000 bytes. The number of bytes can be checked by clicking the "HISTORY" button at the top-right corner of the page. If the page does not meet the minimum size requirement, it may get marked for deletion. Notice for creating Cover/BETADCIU (But Every Turn a Different Cover is Used) pages A cover/BETADCIU page can be created ONLY if it has a download link or proof that shows that it is a playable mod. If the cover is non-playable, then the page cannot be created regardless of its popularity. Any cover/BETADCIU page that doesn't have a download link or proof to show that it's playable will be deleted. However, non-playable (and playable) cover pages may be created on the unaffiliated Friday Night Coverpedia Wiki. A mod's official YouTube channel, Twitter account and/or GameBanana/Game Jolt work-in-progress link must be provided on its wiki page to ensure its existence. A mod's official invite link to its Discord server does not count as such links are not allowed on this wiki. 2. Page Structures Pages should be formatted in a specific way so that they can be consistent. If a mod consists of only one character, excluding Boyfriend's and Girlfriend's original appearances from the base game, create a page for that single character only. If a mod consists of multiple characters (again, excluding Boyfriend and Girlfriend), create a page for the mod. Special Notes: If there are multiple reskin/reanimation mods that are made under the same creator, then they may be combined into a single wiki page. If a mod containing a single character contains different designs for the Friday Night Funkin's characters used (e.g., Boyfriend), an exception is allowed and one can format it as a mod page rather than a character page. Ohagi[?] Date-Night Masses[?] BackDDuck's Skin Packs[?] Any page in the High Quality Pages category[?] 3. Page Titles Page titles are usually formatted in title case rather than sentence case. Only name a page with Vs. or the mod's title if it has 2 or more characters in it. If not, name it after the character's name only. If the title is taken, add the name of the developer in parentheses at the end of it. Make sure the first time the page is mentioned is in Bold. For pages that cover multiple reskin/reanimation mods under the same creator in a single page, name the page as either [CreatorName]'s Reskins or [CreatorName]'s Reanimations (where [CreatorName] is the name of the creator of the reskins/reanimations). Friday Night Funkin' Lullaby over Friday night funkin' lullaby Sans (Draco)[?] SugarRatio's Reanimations[?] 4. Section Headings All section headings should be consistent across mod/character pages. Furthermore, naming said section headings to make them overly complicated is unneeded when there are better and simpler ways to name them. Characters over Characters in the Mod[?] Music over Soundtrack/Audio/OST[?] 5. Use of Friday Night Funkin' Characters If a mod features characters from the base game (e.g., Boyfriend and Girlfriend), they are not to have their own tabbers in the "Characters" section and instead should be placed to their respective tabber in the "Gallery (General)" section. However, if their appearances, personalities, and/or lore/story are different compared to what is shown in the original Friday Night Funkin', then they may be placed in the "Characters" section. Examples for Characters: Funkin' Aside[?] and Mario's Madness[?] Examples for Gallery (General): Indie Cross[?] 6. Credits When creating a page for a mod, always credit the names of who made the mod in the ModInfo template. Documentation of how to fill out said template can be found here. If there is a character page with no main mod page linked to it, list the credits below the download link section by using the credits template. Note: If a mod developer has left their mod team, do not remove their name. Even if they left, it doesn't change the fact that they still made a contribution to the mod they were involved in. Instead, insert the text, "(Formerly)," beside their name. If a former mod developer requests their name to be discredited, then their name can be removed from the mod's credits. - 7. Trivia Each page on the wiki has its own trivia section. A trivia section includes minor or insignificant bits of information of a mod or character that may have little information for explaining. Trivia sections on this wiki are considered somewhat troublesome due to them having a high likelihood of containing misinformation from trolls or misunderstandings. It is crucial for editors on the wiki to understand how to properly include factual and objective information on pages to prevent future complaints from mod creators and developers. If a piece of trivia information comes from a public Tweet, YouTube community post, or another outside source of information given by the creator or developers of the mod, always provide a citation to it. If a tweet is deleted/account suspended, then it's suggested to either replace the ref with a WayBackMachine Archive or a screenshot of said tweet. If the source of information is in the form of a Twitter or Discord message from DMs or a server, then include permitted screenshots of them.[?] Do not add assumptions or uncertain pieces of trivia. This includes leitmotif assumptions[?], pose assumptions[?], and theories[?]. Should there be no trivia available for a character or an entire mod, the heading may be left out entirely. However, the chances of that happening are very rare. Skarlet can jump 7 times her height of 5.5ft, meaning that she can jump to around 38.5 feet into the air. Dave is actually 6ft tall. 8. Minor Formatting Italics should only be used for titles of major works (e.g., video games, films, shows and albums) and series of them. This includes Friday Night Funkin'; if italicizing Friday Night Funkin' results in formatting issues due to the apostrophe in the title, put a <nowiki> tag around the apostrophe (but don't put the tag around the wiki formatting for the italics). Titles of minor works (e.g., articles, episodes and songs) should have double quotation marks around them. However, it is generally not necessary to enclose the titles of Friday Night Funkin' songs in quotation marks. When mentioning Friday Night Funkin' songs and modded songs, always keep them in bold. - 9. Wiki Links Links are what brings multiple pages and articles together. They can be added by putting two brackets at the beginning and end of what gets to be linked while in source editor. To create a link to a mod page on this wiki, use double brackets on each end of the page name (i.e., [[Page Name]]). To make the link display under a different name, use [[Page Name|Name]], and it would come out as "Name." To make the link direct to a specific page section, use [[Page Name#Section]]. [[Vs. Void]][?] [[Julian T. Whitmore|Julian]][?] [[VS Shaggy#Red Shaggy]][?] 10. External Links To link to an external website, use one bracket on each end instead. For example, to link the GameBanana home page, use [https://gamebanana.com GameBanana], and that would come out as Gamebanana. (Include the "http(s)://" and put a space between the link and the desired text to be displayed.) To link a page on a wiki that lies within the FANDOM network, use [[w:c:communityname:page name]] and replace "communityname" with the wiki name provided at the beginning of the wiki URL. To make it display under a different name, use [[w:c:communityname:page name|Name]], and it would come out as "Name." Note: Links to official Twitter and YouTube accounts for Friday Night Funkin' mods are allowed to be placed on their respective mod pages, especially for pages that cover mods with unavailable download links. They should be listed under a page section titled "External Link(s)" or "External" under a "Links" section. [https://gamejolt.com Game Jolt][?] 11. Download Links All download links for a Friday Night Funkin' mod page should be placed under the "Download Link(s)" section. Do not insert unofficial links or links to fan-made mods under that page section in official mod pages (e.g. Linking High Effort Sky under the "Download Link(s)" section of NuSky + Skyverse or linking an unofficial downloadable cover of Unknown Suffering under the "Download Link(s)" section of Wednesday's Infidelity). Nonpublic and/or pay-to-access links or socials are not allowed to be added to pages. GameBanana, GameJolt, Google Drive and MediaFire[?] Newgrounds[?], Kofi[?] and other direct download links[?] Links to Discord Servers for Friday Night Funkin' mods and Patreon Links[?] 12. Templates Templates are pre-made pages that are designed to be included/inserted on other pages. They most often take the form of notices, such as the {{Stub}} template. Templates can serve a variety of purposes. To insert a template onto another page, put two curly brackets at the beginning and end of the template name while in source editor, as done above with the stub template (except the template would actually appear). If the template has fillable parameter(s), use {{TemplateName|param1}}, and the parameter would be filled out with whatever was typed in. A list of templates can be found here. Note: Refrain from creating templates without administrator approval. Otherwise, they will be deleted. {{Reflist}}[?] {{Outdated|New update is out}}[?] 13. Hidden Comments Hidden comments should only be used to briefly inform editors on a relevant page matter to prevent future edit wars or give necessary subject context. Such comments are invisible and only appear while editing in the Source Editor. Use "<!--comment-->" when writing them. Do not use hidden comments to make unnecessary comments on a page, to chat with editors or to mention other editors. Along with that, avoid making them with a hostile tone and/or signing them. Inappropriate use of a hidden comment will be considered as vandalism. <!--Please do not add any assets from leaked builds as doing so strongly opposes the mod developers' wishes.-->[?] <!--idk what else to do here for now-->[?] <!--Hey! don't remove/edit this! Or i WILL Kill you! -Username-->[?] 14. Separating Pages There are certain pages that have a numerous number of bytes due to the immense amount of content a mod has, surpassing even the original game itself. This is problematic because not only this many bytes can cause pages to lag, but it can also increase the likelihood of them crashing. Thus, making it more challenging to edit and save changes. If a page reaches at least 100,000 bytes (100k bytes), a subpage must be created immediately to ensure stability. Take a page like VS. Impostor which utilizes wikitables as navbars for separation. DO NOT transclude subpages into the main article where the separation is being done. That renders separating pages almost completely pointless because Fandom will still have to load everything even if transcluded and will cause lag. Do not create subpages for subpages. That will make articles excruciatingly boring to go through as readers would have to open multiple pages to look at content. Do not litter an article with too many subpages (maximum of 5-7 subpages depending on the article). If a subpage was made prematurely to where its size and its main article size don't add up to at least 100k bytes, then that subpage must be merged back to its main article page. This is how users should split pages if a single mod page has too much content: [MainPageName]/Characters [MainPageName]/Music [MainPageName]/Gallery Where [MainPageName] is the main article's page name. 15. Separating Subpages In the event that a subpage was to reach at least 100k bytes, then that subpage may be split to ensure stability. However, the split cannot result as a subpage for a subpage. (i.e. [MainPageName]/[SubpageName]/[SubpageName]) To know how to properly split subpages, refer to the following examples on the right. This is how users should split subpages if a single mod subpage has too much content: [MainPageName]/Story Mode Characters [MainPageName]/Freeplay Characters [MainPageName]/Unused Characters [MainPageName]/Unused Music Where [MainPageName] is the main article's page name. Subpage names may be adjusted depending on the article. 16. Moving Pages If there is a mistake in a page's title, then the page should be moved and renamed without leaving a redirect. A character page can be converted to a mod page if and only if a mod's update that includes more than one character is released. When moving a character page into a mod page, be sure to leave a page redirect when doing so. Renaming Siivagunner to SiIvaGunner Rips[?] Moving Kapi to VS. Kapi Arcade Showdown[?] 17. Page Redirects Certain pages may have redirects created, whether due to a page being moved from a character page to a mod page or an alternate title that is commonly searched for. However, linking the redirect page is highly discouraged and linking the page directly is always preferred. To create a redirect without moving to an existing page, use the following code below: #REDIRECT [[PageName]] Where [[PageName]] is the name of the redirected page. - 18. Origins Section (Optional) In the modding community, mods based off of preexisting media are prevalent. Such mods should always be categorized as "Based on media" to indicate as is. Furthermore, an "Origins" section is needed as well as a short video with audio, a GIF, and/or an iconic image/photo of what the mod was based on. Remember to always provide a source link on where the original content was found. If possible, include a link to a wiki page, primarily one from Fandom, on the origins of the character or the content that it was based on. Do not plagiarize information word for word from other wikis. If a mod is based on a meme, refer to KnowYourMeme, a meme database, in the description below the source. It's most likely that the meme that the mod was based on is there. However, if it's not available, then include a Fandom wiki page of the source. If there are multiple mods that are based on the same piece of content or media, use {{#lsth:Page Name|Origins}} below the "Origins" section to transclude an exact copy of the section (minus the "Origins" heading) from one of the mod pages. Origins section for Another Atrocity Fan Mod Origins section for IShowSpeed VS Ben This section concerns creating and formatting disambiguation pages[?]. # Title Description Example 1. Minimum Criteria At least three different ambiguous entries are required for a disambiguation page to be created. Furthermore, the page should be either a character disambiguation or a Friday Night Funkin' mod disambiguation. Avoid creating disambiguation pages based on media or a series (i.e. Undertale and Eddsworld). Matt (disambiguation)[?] Luna (disambiguation)[?] B-Sides (disambiguation)[?] 2. Notice Template All disambiguation pages must include the {{Disambiguation}} notice template at the very top. See Template:Disambiguation for documentation. 3. Disambiguation Titles The page title should be formatted as "[PageName] (disambiguation)" ("disambiguation" should always be in lowercase). Nene (disambiguation) 4. Introduction Each disambiguation page should start with a sentence or paragraph that explains what the disambiguation page is about. Do not break the 4th wall when writing them. Always remember to keep them in 3rd Person Point of View. Hank J. Wimbleton is the main protagonist of the Flash animation series Madness Combat. This disambiguation is intended to help readers and editors find a page that includes a different version of the conventional Hank.[?] This disambiguation is intended to help readers and editors find a page that includes a different version of the conventional Ron. Ron may refer to:[?] You may be referring to:[?] 5. Content Images of each version of the same entity should always include links to their respective pages. Do not include entries that have no article links, and avoid linking to the same page or section more than once. If a character from a mod page has more than one phase (ex., Whitty's normal and Ballistic phases), use only the first phase idle pose of the character. Do not including multiple phases of the same character that originate from the same mod page. If a character's idle animation has been updated in the mod (e.g., Red's idle updated from V3 to V4), replace the old idle pose with the newest version. - 6. Sorting List the characters/mods in alphabetical order. If the character name is exactly the same for multiple entries, add the mod name in front of the characters to distinguish them: [Mod Name][Character] (ex. Basement Show Girlfriend) If multiple entities fall under a similar category (i.e. Remix Mods, EXE, or even variants of a character), they can be sorted into page sections. However, if the page becomes long from the amounts of iterations, tabbers can be used to categorize them more compactly. If a user is unsure on how to sort them properly, they should ask a staff member. Special Note: Disambiguations for Friday Night Funkin' characters (Boyfriend, Girlfriend, Pico, etc.) should always list their original appearances from the base game first. Metal Sonic (disambiguation)[?] Girlfriend (disambiguation)[?] 7. Categories Avoid adding categories to Disambiguation pages, even if they apply to the characters or mods. The "Disambiguations" category is automatically included if and only if the {{Disambiguation}} template is already added to the top of the page. [[Category:Disambiguations]] This section concerns the editing practices of including sprite animations and assets to pages. # Title Description 1. GIF Accuracy GIFs should look as accurate as they do in-game, albeit in higher quality. When making GIFs, try to keep the frames still and consistent with each other to avoid the GIF looking disjointed (refer to bad example). To know how to properly create GIFs, refer to this tutorial. Note: Do not create GIFs for "animations" that consist of a single frame. Instead, extract the frame from its respective sprite sheet in the form of a PNG. (Refer to third example.) Good Example Bad Example Nikku Morioka, a character from Hotline 024, only has one frame in her idle animation from Armageddon. 2. Pixel Sprites Some mods have pixel art sprites that are usually small by default. Because of this, pixel GIFs can be resized by a percentage of 500-600 using either Lospec or ezgif via the Gifsicle resize method. When using ezgif's resize tool, avoid changing the aspect ratio when resizing. 3. Static Poses For every animation (idles, singing poses, etc.) a static image should be included respectively. If a reanimation uses the same sprites, simply keep the previous static image. Do not compile all static poses in one image for each character. Like character GIFs, upload them as separate images. 4. Crop Be sure to crop sprite images to remove any empty margins around it. 5. Flipping Images When Necessary There are some mods that contain character sprites that flip the opponent horizontally as if they are a playable character (i.e. Pico and Tankman). If they are not a playable character, then their GIFs and static images should be flipped horizontally. Otherwise, they should be kept in the direction they're facing as is. Character sprite sheets should never be flipped horizontally. 6. Placement Sprites are to be placed in their appropriate gallery sections. For example, character sprites should be placed in the "Gallery" section under their respective character sections, while menu and background assets are usually placed under the "Gallery (General)" section. This section concerns practices for proper use of the SongInfo and SongInfoGradient templates. # Title Description 1. Borders Border colors of songs should match with the color of character icons shown in each song. Gradient borders should only be used on songs with two or more singing characters that aren't Boyfriend. This is the only appropriate use for these gradients. 2. Icons Song icons should have a size of 80-100px. Custom icons are allowed to be used as placeholders or if there are two characters that go against each other, excluding Boyfriend. Do not make the icons larger than they have to be. 3. Titles All song titles and sound effect titles are to remain in their default formatting. There is no need to make them oversized or make them colorful using gradients. Gradient titles are unnecessary as it can both give a page an unneeded extra number of bytes and sometimes make it harder for users to read the text. However, the use of solid font colors is allowed. To apply use either of the following code: <font color="hexCodeColor"></font> <span style="color:hexCodeColor"></span> If the title color blends in with the background to where it's hard for viewers to read, use the following code to apply both a font color and a secondary color around the text: <span style="text-shadow: 0 0 10px hexCodeColor; color:hexCodeColor"></span> This is to ensure better text visibility where necessary. 4. File Quality Music and sounds should be ripped from the mod or from a good source at high quality. Songs should not have the "3, 2, 1, GO" or record scratch sound effect. Furthermore, it should also be at a normal volume and not be super loud or quiet. Lastly, all music and sound effects are to be uploaded as MP3s. This is because that file type is widely supported for many devices and systems, bringing great listening experiences for users at small file sizes. To know how to properly rip audio from a mod, refer to this Music Tutorial. 5. Placement All music and sounds are to be placed under the "Music" section of pages. Furthermore, they should be sorted into tabbers (i.e., Story Mode, Freeplay, Sound Effects, etc.). This section concerns the common practices and standards of editing via Source Code. # Title Description Example 1. Use Source Editor Source editing is highly recommended as visual editing takes longer to load, especially for long pages. - 2. Acceptable Coding Languages MediaWiki and HTML is what this wiki uses, so knowing other ways of coding most likely won't work here. - 3. Case Sensitivity Coding is case sensitive, so making sure it's upper or lowercase is important. - 4. Use of <nowiki> Tags The <nowiki> tag is used to disable wiki markup. If used incorrectly, it could break an entire page easily. <nowiki>content</nowiki> 5. Use of HTML tags HTML tags or any similar code have tags, which allow for changes in aspects of the text or page. When making a tag they need to have a start and closing tags. It's important to add the closing tag as not doing so will usually break the page, even on minor things. If the page is red or white, it means something was messed up (unless <gallery> is used). Additionally, it's highly suggested to not use deprecated elements. (For the following examples shown, "content" is a placeholder for any character or text.) <u>content</u> <span>content</span> <span>content</span> {{content}} [[content]] 6. Source Editor Lag If for any reason a user may be experiencing lag when using the source editor, it is recommended to turn off syntax highlighting before making any source edits. - 7. Tabbers When using a tabber, both {{#tag:tabber| and <tabber> are acceptable. However, more advanced techniques can be done with the former. Always make sure to use {{!}}-{{!}}TabName= when creating sections for a tabber. Furthermore, always close the group of tabbers with }}. (For the following example shown, "name1," "name2" and "name3" are placeholders for tabber names, while "content" is a placeholder for any content that is added, such as information, images, etc. ) Note: Avoid using tabbers beyond the second layer as doing so can get messy to work with, specifically the "Characters" section. Any tabbers that are in three layers or more must be changed to two layers. {{#tag:tabber| {{!}}-{{!}}name1= [content] {{!}}-{{!}}name2= [content] {{!}}-{{!}}name3= [content] }} 8. Citations When citing information, use the following format: <ref>[ReferenceLink]</ref> If a reference is cited multiple times, use the following code for the first reference: <ref name="[ReferenceName]">[ReferenceLink]</ref> And for subsequent references, use this format: <ref name="[ReferenceName]" /> Note: [ReferenceName] and [ReferenceLink] are placeholders for the reference name and reference link, respectively. - This section concerns gallery sections across mod and character pages. # Title Description 1. Relevant Images Galleries should only include images related to the page. This includes mod assets,[?] GIFs,[?] statics,[?] related sketches and concept artwork by the mod developers. They should also include hidden images that are found within the mod's files, unless if it's NSFW.[?] 2. Outside Source Relevant Images Relevant images from different sources like Twitter or Discord that connect to the page are allowed to be included in galleries as long as they come from the mod developers with their respective source links. 3. Image Captions All gallery images/GIFs are required to have a caption that briefly describes them. Do not leave any of them blank. 4. Caption Alignment All gallery image caption text should be centered. Use <gallery captionalign="center"> when centering them. 5. Organizing Images Gallery images must be organized under section headers or tabbers. Be sure that each asset, image and GIF is placed appropriately. If it is related to a character, it should be placed in that character's gallery section, while if its general mod or gameplay assets, it should be in the "Gallery (General)" section. This section concerns creating and formatting navbox templates[?]. # Title Description 1. Minimum Criteria Navboxes should only be used if there are at least 10 pages that are related to a major category. Take [[Category:Nintendo Characters]] or [[Category:SEGA Characters]]). Because both have a bunch of pages related to their respective categories, the Nintendo and SEGA navboxes were created and used across their relevant pages. Do not add unnecessary navboxes to a page. (Ex. Adding the Newgrounds navbox because a Newgrounds character appeared as a cameo in a mod, rather than a major role.) 2. No Sub-navboxing Sub-navboxing, the act of creating a navbox that is an extension of a main navbox, is not permitted. (Ex. There is no need to create separate navboxes for Mario mods and Kirby mods, since both of their entries can simply be added to the Nintendo Navbox.) 3. Naming Navboxes The Navbox template should be formatted as "[NavboxName] Navbox." To know more on how to create one, click here. 4. Links Each link within Navboxes should have at least one character icon before it, if applicable. The maximum number of icons a link can have is 6 character icons. 5. Colors Navbox colors should be chosen to provide sufficient contrast between text and background. The color of the link should match either the icon in question or the logo of the mod, however, adjustments to the colors may be required in order for the text to be visible![?] 6. Navbox Limits The maximum amount of navboxes a page can have is 6. However, it is preferred to keep the amount of navboxes concise and low if possible. 7. Placement Navboxes must be placed at the bottom of each article, specifically before the beginning of the categories list. 8. Order If a page has more than one navbox, they should be listed in alphabetical order. This section concerns creating categories. # Title Description Example 1. Minimum Criteria A category page can only be created if there are at least three entries that can be grouped together under a similar subject. Any category pages that do not meet this requirement should be marked for deletion using this template: {{delete|Category page does not meet the minimum criteria of three entries.}} - 2. Naming Categories The purpose of categories is to group up pages that follow a similar subject. Each category must directly distinguish from each other and hold very little similarities. Category names must be short, simplified, and objective. Use as few words as possible. If a category's name isn't up to these standards, it can be renamed by putting {{move|Category:New name}} on the page. Good Examples Category:Sarvente[?] Category:Animated Icons[?] Category:ENA series[?] Category:Newgrounds Characters[?] Category:Ito Saihara[?] Bad Examples Category:Characters that switch phases during the song[?] Category:List of Unique Mod Songs[?] 3. Unneeded categories Avoid creating categories that are considered vague, unrelated, or unneeded. The reason is because not only are they not related to Friday Night Funkin' mods, but they also clutter up pages and create unnecessary groups on the wiki. If a staff member discovers a category that is deemed unnecessary, they will delete it alongside with all the other same categories in every page that includes it. Category:Difficult Mods[?] Category:Characters with unique microphones[?] Category:CommunityGame[?] Category:Undertale/Deltarune[?] 4. Category Placement Most categories are usually placed only on article pages, specifically at the very bottom. Categories that appear on pages where they shouldn't, such as user pages and user subpages, will be removed. - 5. Category Page Sorting For pages with "Vs." at the beginning of their titles, place {{DEFAULTSORT:[page name without "Vs."]}} in them so the pages can be sorted properly in category pages. {{DEFAULTSORT:Zardy}} This section concerns other general standards of the wiki. # Title Description Example 1. "Funny" Edits Do not add "funny" or "troll" edits in any circumstance (including April Fools). Such edits can usually be seen as vandalism, along with just being unneeded and annoying for most editors. - 2. Unneeded Template Placement Please don't add templates on pages that don't need them. For example, the content and trigger warning templates don't need to be added pages that are slightly mature, as Friday Night Funkin' likely already does fall into these topics. - 3. Avoid Unneeded Repetition Try not to repeat any information on any given page unless absolutely needed. - 4. Header Colors and Gradient text Header colors of Character templates should match character icon colors respectively. Header font colors should not clash against the header color to where it becomes too hard to see. Text colors are only to be used for dialogue, if applicable. Gradient text is forbidden, unless if it is used for a mod title within a page's ModInfo template (only to a certain extent if the gradient reflects the mod's style, such as Antipathy's ModInfo template). - 5. Character Names Real Name/Full Name should only be used in the character infobox and introduction of the character, if applicable. Otherwise, use the nickname that is commonly used in the mod. Beta Mouse is called "Beta Mouse" throughout this page, not "Michael". 6. Character Idles Idle poses for characters should always be placed in character templates. However, only add idle animations based on major design changes. Minor design changes that are too subtle to notice and scrapped designs that aren't present in a version of a mod should be placed in the character gallery. - 7. Background/Foreground Characters If a background (or foreground) character from a mod is a major opponent or a playable character in the same mod, then place the background animations in the gallery of the character section. Otherwise, place it into the "Gallery (General)" section of the page. Note: If a well-known character appears in the background or foreground of other mods, do not enlist their cameo appearances in the wiki page of the mod they debuted from. Not only does such list provide an unnecessary number of bytes, but also almost all of their cameos are considered to be non-canon to the mod they came from. If the character's cameo is confirmed to be canon by the developers of the FNF mod they originated from, then such information can be included within the character's trivia section (with cited references). Pico appears as a foreground character and an opponent of Graffiti Groovin'. Thus, his foreground animation should be inserted into his character section. On the other hand, Nene only appears as a foreground character and not as an opponent of the mod. Thus, she must be inserted into the Gallery (General) section. 8. Invalid Reasons for Notice Templates Do not place invalid reasons in notice templates. If a user can't find a good reason to put for those notice templates, then either the reason may be left blank until there is one or remove the notice entirely. All notice reasons must be written in third person. "You know the drill" or "It's [insert thing here] what do you expect" [?] "Get to work"[?] 9. Hatnotes Hatnotes are normally used for adding links between articles where more context is important. Place hatnotes above all other visible content where applicable, or else they will appear in the link preview. - 10. Large Files Files must be 10 MB or below before uploading. This is due to Fandom's file upload limit. In the event that a file may be too large, use an online file compressor to reduce the file size. Image Compressor MP3 Compressor 11. Naming Files Files are to be named based on the mods they originate from and what they are. If a file has the same name of an already-existing file, do not replace the already-existing one. Instead, rename it to avoid accidental overwrite of the latter. HFManoAloeDOOG-idle.gif[?] Speakers.png[?] 1C967513-EFF4-45A3-8996-0A39D5449ACD.png[?] 12. Old Files If a new version of a file, sprite, etc. exists, DO NOT upload over the old one or delete it. Instead, upload it as a separate piece. This also goes for dialogue as well. However, if an image turns out to be lower quality, it can be overridden by uploading a higher quality version of said image. New idle pose Old idle pose Older idle pose - 13. Placeholders for Icons If there are characters that don't have any icons, be it in dialogue or songs, placeholder icons may be used until official icons are released. They can either be in the form of official dialogue portraits or they can be custom-made at high quality. When using custom-made icons as placeholders, users must give credit to the people who created them in the first place by stating them in the placeholder notice template. Tabi's official dialogue portrait Custom-made placeholder icon used for Tricky's Chicken Dance (Tsuraran Remix) (Alpha Mix) in SiIvaGunner Rips. 14. Cutscenes Certain mods will include animated cutscenes that include voice acting similar to Week 7's. Do not add cutscene video files within <gallery></gallery> tags as doing so will cause the file to not render properly. Instead, use the CutsceneInfo template. If a mod has more than five cutscenes, place them in a separate page section titled "Cutscenes." Otherwise, place them in a "Cutscenes" tabber under the "Gallery (General)" section. In the event that a cutscene video file can't be uploaded due to the 10MB file size limit, it can be compressed using this online video compressor. Preview of desired video compression settings before applying. 15. Removal Upon Request A mod creator/developer can request a wiki staff member to remove certain parts or an entire page of their mod with reasons on why. If a mod creator requests for a piece of trivia, an image in the gallery, or other things to be removed with valid reasons, they will be removed. - 16. Sandbox If a user is not confident in their abilities, it is highly recommended for them to start on a Sandbox to practice. User:​/Sandbox 17. When in Doubt, Just Ask There are times to where some users don't know exactly what to do when editing, even after reading the Style Manual. This can range from determining which navbox to use on a page or if a new one needs to be created, to figuring out how to properly sort and order disambiguation pages. If at any point a user is unsure in regard to edits, they should ask a content moderator, administrator, or bureaucrat for further guidance. A list of current staff can be found here. - This section concerns the standards of adding gameplay GIFs (optional).[?] # Title Description Example 1. Minimum Criteria Gameplay GIFs must be 3-8 seconds long, show both the opponent and player singing (ideally most of their poses visible and clear), the player having an FC (No SDCB allowed) while they are playing. If possible, include having the health bar show the transition between the opponents normal and losing icons. For GIF quality, the framerate must be around 20 frames per second (FPS). Good Example[?] Good Example[?] Good Example[?] Bad Example[?] 2. Solo Character If the song has only one character singing instead of the usual two characters, then only include a gif of the solo character singing. Like the previous standard, the GIF must show the player FC the section they're playing. While this example shows two "different" characters, Sonic and Fleetway Super Sonic, the player plays as both of them as if only one character is singing Phantasm. (In this case, two characters in one body.) 3. Multiple Characters If there are more than three characters singing in one song, then the GIF should show at least two of the characters singing. (However, it's optional to feature all of them singing in one gameplay GIF.) Gameplay GIF showcasing three characters, Edd, Tord, and Boyfriend, singing Challeng-Edd (END Mix) This gameplay GIF showcases multiple characters singing in Blantados' playable Nerves BETADCIU 4. Mechanics Gameplay GIFs of Mechanics, such as danger notes and health drain, are allowed. Gameplay GIF of Legacy Annie's health drain mechanic in Tone It Down. 5. Reskin/Skin Mods Gameplay GIFs that showcase playable reskin/skin mods are permitted, regardless of if they were made for the base game or for a different mod. A Gameplay GIF showcasing a skin mod. In this case, the Fun Sized Whitty mod.