User blog comment:Emitewiki2/A new project!/@comment-4628859-20150619020215/@comment-3060206-20150619084434

You're right on the fact that many of the page titles are for components that don't have official names. If that page title is moved, the file name would probably have to be moved as well, making the process very arduous for the admins who have to rename every related file. For official names, there is more stability, but even those have alternate names that the community has trouble deciding which should be the "target title".

If people don't actually search for images, then they would have to rely on what they already know when it comes to adding an image. Due to the inconsistency of the filenames, however, this becomes a near impossible task because everyone has their own way of naming images. Suppose a file was used on a page, but had some weird gibberish name. If another user wants to add this same file to another page four weeks down the road, they're probably not going to remember that gibberish convention, which means they have to take time to go to the page and view the image to get its name. Even worse, some files may be uploaded, but not used. They end up being forgotten when their related page is created, which means users upload duplicates because they could not find or were not aware of the original file. Why do that when you can develop a consistent naming system that makes it easier to add the image based on its characteristics and reduce the trouble of having to search for the image's name?

And not just that...by giving each file a naming format such as "game name object.png", we can make it easier for users who need to find a certain file using tools such as the link prompt in the source editor or Special:PrefixIndex, which allows you to view all pages that start with a given string of characters. If the sprites had the game name as their prefix, then a user searching for images could use the prefix index to quickly search up files beginning with that game name.

I think Emite mentioned how the form of a component would be referenced in an image name. The syntax he proposed puts the "state" at the end before the extension, as evident in the fan-spinning example. Though he will need to readjust this because his intended syntax will not work; file names cannot have forward slashes in them. If he continues to propose this, the project is going to fall flat on its face before it can even take off.