User:Supermariofan67

I am , a User of the Super Mario Wiki. I have a Wii U and Switch with the games listed at the bottom of this page. I am a fan of the Super Mario series and Mario Kart series. You will most likely find me doing various file and page maintenance, adding/replacing images, and sometimes rewriting/expanding articles. I often make shell scripts or use command line utilities to automate some of this work, such as optimizing or cropping images, or sorting stuff. I share some of these tips below for anyone who is interested. If you also do this type of work, I encourage you to become familiar with some basic and how to use them with your favorite text editor, such as, , , or even the wiki's built-in editor. I also recommend learning the basics of your operating system's shell scripting language, as well as some utilities like, , and.

I also edit on WiiBrew Wiki (so far just to clean up after a vandal) and ArchWiki, though I'm not nearly as active on those wikis as I am here.


 * }

Getting Screenshots from Wii U
In the past, it was possible to get screenshots from Wii U games by accessing the Wii U's internet browser during gameplay and uploading images to Dropbox or a site like Imgur or Postimg. However, these sites now use newer web standards that are not supported by the Wii U's browser, so they no longer work on the Wii U. However, after reading through Reddit posts about it I found a way to get screenshots to your computer using this HTTP file server software. You must run the program, set a target directory for files as described in its instructions, find your computer's internal IP on your network, and access that IP from your Wii U browser, where you can upload the images straight to your computer. It uses older web standards (for now at least) that are supported by the Wii U, and it can run on Wine on Linux/MacOS.

In addition, it is still possible to upload straight to MarioWiki from the Wii U if no cropping is required on the computer.

Some common confusion about SMG/2 images
To clarify some definitions: upscaling isn't the same as rendering above native resolution. An image is upscaled when the file's resolution is higher than the resolution of its content (for example, when a game is rendered at 1x native resolution but screenshot in Dolphin's full screen mode, or if the image is artificially resized with an image editor.) This causes unnecessary file bloat and should usually be discouraged. However, this is not the same as setting the emulator to render above native resolution (in multiples of the native resolution via the Auto setting in Dolphin.) This produces images whose actual content is in high resolution, and thus does not waste file size. According to 's screenshot guide, it is acceptable to capture Wii screenshots above 1x native resolution due to Dolphin's inconsistencies with producing native resolution screenshots without upscaling or stretching (read that guide for more info). For SMG/2, I follow that guide to produce 1920x1048, above native screenshots.

I usually replace an SMG/2 image if:
 * Its aspect ratio is not a multiple of the game's normal widescreen aspect ratio, such as 1920x1054.
 * Its unnecessarily upscaled (e.g., rendered at 1x native but taken in full screen mode).
 * Its not an emulator screenshot (e.g., from a YouTube video).
 * I can get a better view of the subject

Moving Images

 * I follow Trig Jegman's guidelines and abbreviations when moving images. However, I additionally may use the abbreviation UTS, meaning "underscore to space." Within articles, MediaWiki usually treats spaces and underscores the same, but generally images should be linked with spaces, such as if "File:Image Name.png" were linked in an article as "File:Image_Name.png," similar to how File: is preferred over Image:, or how File: is unnecessary in galleries. So I will often quickly fix those (RIF and UTS) when passing through a page to change filenames. Both of these can easily be done with the wiki's find and replace function (the button in the top-right corner of the editing box).
 * Here is a tip to find images with special characters that may need to be renamed. With a list of image names in a text editor such as Notepad++ or VScode, search for the regex . This will highlight any characters other than letters, numbers, wiki syntax, hyphens, and apostrophies, making it easier to identify images that may need technical renaming, such as File:YWW ★-S Shiny Platinum Yoshi.jpg.

Sort galleries alphabetically
To sort a gallery alphabetically, put the code contents in a text file and run the command  on it. This sorts alphabetically by the contents of the last text field, with text fields, in this case, separated by "|", therefore grabbing the display names of links. By default, this will ignore special characters, such as, which is generally desired. If you want to sort all characters literally, run  first. Note that if a gallery has multiple entries for a particular subject, this will sort the bare text, such as  above the linked text, such as , so that should be manually checked.

Tricks with imagemagick

 * Using, it is easy to stack two or more images vertically using the command . See left side for example.
 * It is easy to crop images (such as artworks) to their content (removing the surrounding solid color or alpha space) with . If there is any slight shading that needs to be cropped over, use the   option, where x is a low number (try 3 or 6 first). See below for a script to bulk trim and compress all images in a folder.
 * Similarly, it is easy to apply transparency to simple graphics, such as sprites, with, where color is the name of a color (e.g., white) or a color's hex code, enclosed in single quotes. However, more complex graphics with fuzzy edges, such as artwork, might look choppy, requiring the use of the   option or not at all. Don't apply transparency to these types of images unless it is very clean.
 * Crop black border on 1920x1048 SMG/2 screenshots with
 * Re-encoding JPGs all the way at the 100 quality mode can severely bloat file size, while using low quality modes can cause visible artifacts. When processing JPGs, consider adding the  option, providing a better balance between quality and size. Also, consider the   option for PNGs, which removes unnecessary metadata/gamma/color profiles. However, applying PNG Monstrous or another optimizer should do this anyway.
 * How to use ImageMagick
 * ImageMagick functions
 * A video by Luke Smith explaining ImageMagick.

A script to automatically optimize all PNGs in a folder
This should be equivalent to running PNG Monstrous with the pngout and zopflipng options enabled. Additionally, it will convert BMPs to PNGs and uncapitalize file extensions. This script requires zopflipng, pngout, and GNU Parallel. It will run and  on all pngs, PNGs, bmps, and BMPs in the current directory and output the compressed images to the ./optimized directory with a lowercase .png filename. Zopfli uses the  (" ") and   (" ") options. It will compress multiple images in parallel, up to the number of CPU cores in your computer. This script is intended for Unix-like operating systems, such as Linux and MacOS. You will need to install Zopflipng and GNU Parallel with your package manager (for MacOS, use the Brew package manager). I'm not sure about Windows, but you can probably use this in the, or maybe find a way to port this to a native PowerShell script. You will probably need to download pngout manually and place it in in a directory in your PATH, such as ~/bin, as it is not available in most package repositories (though it is in the AUR). With the required programs installed, just put this code in a text file saved in ~/bin or in the folder where your PNGs are,  it, and it should work. If not, you can just manually run the two commands while in the folder with the PNGs. It's less convenient, but it would do the same thing.

Cropping to content and compressing with one script
This will crop all JPGs or PNGs in a folder to their content and optimize any PNGs, placing them in the  directory. If you have BMPs, convert them to PNG first with

Big projects I have completed

 * Rewrote part of the Peach's Castle article
 * Rewrote List of Super Mario Galaxy glitches
 * Rewrote List of Super Mario Galaxy 2 glitches
 * Rewrote List of Super Mario 3D World glitches
 * Replaced most of the low-quality screenshots for SM3DW, with the exception of some intro/credits images.
 * Uploaded images for Gallery:Semi-Solid Platform
 * Improved Super Mario 3D World to make it a featured article
 * Made easier to use and consistent with similar templates
 * Cropped to content and compressed many artwork images