Help:Files — mopeio

This is an official Policy of the Mope.io Wiki.
It is an accepted practice that all editors of this wiki should follow. If you believe there should be changes made to this policy, consult an administrator.

This policy in a nutshell:
Rules and guidelines for image use

This page consists of the policies pertaining to files on the Mope.io Wiki. All images which are uploaded must follow the image rules, be named properly, and be categorized properly. Failure to adhere to these standards when uploading an image may result in the image being deleted without notice.

Rules

All files uploaded must not break the rules or the Terms of Use in any way. Files that contain NSFW, epileptic-inducing, or otherwise graphic content are prohibited.
All contributive images – this means images that are used on articles, predominantly images from the game files, as well as in-game screenshots used in galleries – must be properly categorized. See the file directory of categories below for more.
Non-contributive images – referring to images that are not used on articles, often uploaded by an individual to use on their user page – should be kept to a minimum; you cannot upload more than one non-contributive image per week to avoid clutter.

Personal images

All non-contributive images, also known as personal images, must be appropriately categorized as such.^[1]

Non-contributive images which are not being used anywhere on the wiki (indicated by if they are located in Special:UnusedFiles) will be deleted.
- Out of courtesy, if the user who uploaded the unused image is still active, an admin may wish to inform them prior to deletion, giving the opportunity to put the image onto one's user page to avoid deletion. However, this is not required: unused non-contributive images can be deleted without notice at any time.
If you upload a non-contributive image to this wiki for personal use, the image should be under a free license. Images under a Creative Commons (CC) license, or in the public domain, are preferred over copyrighted images, which will be deleted if they cannot be justified under fair use.
Images that you have created yourself and upload to this wiki for personal use also must be freely licensed.
When uploading an image, use the {{Self}} license to indicate that you created the image yourself.
- "Free licenses" include CC-BY, CC BY-SA, public domain, etc. If you do not wish to license a self-published image under a free license, do not upload it to this wiki.

Archiving assets

Main article: Help:Archiving assets

As a rule, all assets uploaded to the wiki from the game files must be archived, using the Wayback Machine.
For images that have been archived, use the archive parameter of the {{File}} template in the file description to list the original URL and the link to the archive.
Archived assets will have the Archived assets category added to them automatically when a user has used the {{File}} template in the file description and added a value for the archive parameter.
If assets have been lost to link rot (i.e. they cannot be accessed from the original link anymore), instead insert the {{LinkRot}} template into the file description.
If a user mass-uploads assets without archiving them, they will be expected to archive the images themselves and add in the expected file description format.

Renaming files

Due to the naming conventions for assets having been changed relatively recently, many old files which do not follow the naming conventions must be renamed/moved, which inevitably creates a lot of red links.

Be aware of any red links that are created when you rename a file.
When renaming a file, update the {{ImageLink}} template so that the file matches the corresponding article. This is important for future-proofing.
Generally, when renaming a file, there is no need to leave a redirect behind as file redirects are rarely used outside of specific cases. Make sure to un-tick the "Leave a redirect behind box" when you rename a file.

File description

All files without exception must use the {{File}} template in their file description, under a level 2 heading "Summary". Said template is used to display the file information in an organized way, except for the licensing which is in its own section.

Refer to {{File}} page for template documentation.

Assets

Assets from the game files of Mope.io should be formatted like this:

{{File
|desc = What the asset is
|type = asset
|designer = Original artist or designer (if known)
|source = The original asset URL (from game files)
|archive = An archived version of the asset URL (archive on the Wayback Machine)
}}

By adding "asset" as the type and entering a value for archive, it will automatically Category:Game files and Category:Archived assets, respectively, to the file.

If an asset has been lost to link rot (i.e. it appears as 404 error and/or cannot be viewed anymore), add "link rot" as the value in the archive parameter. This will add Category:Link rot to the file instead of the Archived assets category.

Gameplay screenshots

Screenshots of Mope.io gameplay should be formatted like this:

{{File
|desc = Description of the file
|type = screenshot
|uploader = Your username (or whoever took the screenshot originally)
|source = Mope.io (this autofills)
}}

By adding "screenshot" as the type, it will automatically add Category:Gameplay screenshots to the file.

Evidence

Files which are used as evidence, typically in the form of screenshots of Discord messages from the developers, should be formatted like this:

{{File
|desc = What the evidence is of
|type = evidence
|author = The person who has revealed the evidence
|uploader = Your username (or the person who took the screenshot)
|source = A URL linking to the evidence
}}

By adding "evidence" as the type, it will automatically add Category:Evidence as screenshots to the file.

Reconstruction

Reconstructed images, which are recreations of non-accessible assets made by local wiki users, should be formatted like this:

{{File
|desc = Reconstructed version of [asset]
|type = reconstructed
|designer = Your username (or whoever created the reconstructed version)
|source = Mope.io (this autofills)
}}

By adding "reconstructed" as the type, it will automatically add Category:Reconstructed assets to the file.

Licensing and copyright

See also: w:Help:File copyright tags on Community Central.

All images must have some form of licensing below the file summary to indicate the file's copyright status. Use a level 2 heading titled "Licensing" underneath the file summary to display this, using the relevant license templates. Alternatively, when uploading a file, select an option in the Licensing dropdown.

Screenshots of Mope.io gameplay, and assets uploaded from the game files are copyrighted, but they can be used under fair use. For such images, use one of the following templates: {{GameFiles}} (assets), {{Gameplay}} (screenshots), or {{Fairuse}} (other media) to invoke fair use.

Notably, reconstructed assets, which are recreations of non-accessible assets made by local wiki users, are considered derivative work, meaning they are still copyrighted by Mope.io, and permitted only under fair use.

If you are unsure of how a file should be licensed, insert the {{Nolicense}} template and message a Staff user for help. This is preferred to leaving the file blank without licensing as we can at least track files without proper licensing. Typically, the source of wherever you found the image should indicate some information about the licensing.

File format

Videos should be uploaded, preferably, as an MP4. MP4 file format is the currently the highest quality of video that Fandom is allowing. Images, again, preferably, should be in PNG format, to ensure uniformity across the wiki, and to make using files simpler for users. Mope.io always has image files in PNG format as well, so if it's an asset being uploaded, don't worry about that.

Naming conventions

All files need to be named appropriately or they will be renamed or deleted. As this is the English-language Mope.io Wiki, all file names should be in legible English using Latin script (no special or custom characters or text). The file type of the image should be written in lowercase, not all caps (for example, .png as opposed to .PNG) and should not include unnecessary characters (for example, .jpg as opposed to .jpeg).

The file name for assets from the game files should be in a title case format, where the first letter of a new word is capitalized, and with hyphens to distinguish the type of skin where required. File names for assets should never have spaces, either.

For example, the file for Cactus pear should be called "CactusPear.png" (note while article names are sentence case, file names must always be title case).

Animal assets

Assets have very specific requirements when being named. The most divergent naming conventions are for animal assets, whereas food and terrain are generally more consistent. The format for default skins is [Animal]-[Skin Type].png, replacing 'Skin Type' with the specific type of skin, which will be either Classic, S1 (Season 1), or S2 (Season 2). Take for example, the Mouse's Classic, Season 1, and Season 2 skins:

File:Mouse-Classic.png
File:Mouse-S1.png
File:Mouse-S2.png

For the animal's assets if it has any (assets referring to components of the skin such as head, body, wings, etc.). The general format is File:[Animal]-[Skin Type]-[Asset].png. For example, here are the names of the Snowy Owl's different skins; the full skin, the head, the body, and the wings:

File:SnowyOwl-S2.png
File:SnowyOwl-S2-Head.png
File:SnowyOwl-S2-Body.png
File:SnowyOwl-S2-Wing1.png
File:SnowyOwl-S2-Wing2.png

For the other Snowy Owl default skins, the "S2" would be replaced with "S1" or "Classic". Some animals have multiple assets, from special abilities or simply from animation frames. For example, the Armadillo has multiple assets for its "Roll" ability, which has five separate frames. The Armadillo files are named as follows:

File:Armadillo-S2-Roll0.png
File:Armadillo-S2-Roll1.png
File:Armadillo-S2-Roll2.png
File:Armadillo-S2-Roll3.png
File:Armadillo-S2-Roll4.png
File:Armadillo-S2-Roll5.png

... and so on. For the Armadillo's old skin, the "S2" will be replaced with "Classic", making its roll asset files begin with "File:Armadillo-Classic-Roll#.png"

For most custom skins, replace the animal's main name with its skin's name. Do not include spaces in the file name if a skin has a long name; make each word capitalized at the beginning For example, the Mouse's different skin files are named as follows:

File:Mouse-S2.png
File:Mouse-S1.png
File:Mouse-Classic.png
File:GoldenMouse.png
File:PurpleMouse.png
File:RoboMouse.png
File:LightPlagueRat.png
File:DarkPlagueRat.png
File:SuperMouse.png

There are certain other skins which follow the default skin naming convention rather than the custom skin convention. They are zombie skins, winter skins (classic and season 2), and Gold Trim skins. The Mouse's skins in these categories are once again displayed:

File:Mouse-Zombie.png
File:Mouse-Classic-Winter.png
File:Mouse-S2-Winter.png
File:Mouse-GoldTrim.png

Other important things to note:

For customized skins from the Store, replace [AnimalName] with the skin's name specifically, again ensuring that there are no spaces in the file name, capitalizing new words instead.
All animal assets should be uploaded directly from the game files, rather than any other source, to ensure full authenticity. This will also ensure that the asset can be properly archived.

Food & terrain assets

Food and terrain assets have a similar naming convention to animal assets, in that they should use either the "-S2" or "-S1" prefix, depending on the design. As stated above, food assets should have an appropriate suffix. For example, the carrot's main two files are named as follows:

File:Carrot-S1.png
File:Carrot-S2.png

For food with an edible outline, the additional "-e" suffix ("e" indicating edible) should be added, after the S1 or S2 suffix. Again the carrot will be used as an example:

File:Carrot-S1-e.png
File:Carrot-S2-e.png

For terrain assets, the simple "-S1" or "-S2" suffix is the only specific naming requirement. The rock, for example, has its files named as follows:

File:Rock-S1.png
File:Rock-S2.png

Screenshots

It does not really matter if screenshots are uniform in naming format, since the screenshot probably won't be needed elsewhere, after it is inserted on the page.

For in-game screenshots, the file can be named according to the topic of the screenshot, e.g. "File:ChickenBurning.png" or "File:Chicken burning.png" would be a screenshot of a Chicken on fire.
Do not use generic names for screenshots, such as "Screenshot 2025-06-30.png" or an unspecific numbered name. For instance, calling an image of a Mouse in-game Mouse2.png would be undesirable, as other files might have similar names.

Footnotes

↑ By listing "personal" as the type when using the {{File}} template, the file will automatically be added to the Personal images category.

[1] By listing "personal" as the type when using the {{File}} template, the file will automatically be added to the Personal images category.

[1]

Contents