Latest revision |
Your text |
Line 32: |
Line 32: |
|
| |
|
| Would images from the fan-translated MOTHER 3 break the "no fanart" rule listed here? {{s|user|Red}} ([[User talk:Red|talk]]) [[File:RedSig.png|12px|link=Special:Contributions/Red|Red]] 13:04, 27 May 2014 (EDT) | | Would images from the fan-translated MOTHER 3 break the "no fanart" rule listed here? {{s|user|Red}} ([[User talk:Red|talk]]) [[File:RedSig.png|12px|link=Special:Contributions/Red|Red]] 13:04, 27 May 2014 (EDT) |
| :Images from fan translations of games are acceptable if the game in question has no official English release. This includes the Mother 3 fan translation, and would also apply to things like older Fire Emblem games. [[User:Miles of SmashWiki|<font color="dodgerblue"><span style="font-family:Comic Sans MS;">'''Miles''']] <font color="silver">([[User talk:Miles of SmashWiki|<font color="silver">talk]])</font></font></span></font> 13:18, 27 May 2014 (EDT)
| |
| ::Thanks for that answer. {{s|user|Red}} ([[User talk:Red|talk]]) [[File:RedSig.png|12px|link=Special:Contributions/Red|Red]] 13:21, 27 May 2014 (EDT)
| |
|
| |
| == Stage hazards? ==
| |
|
| |
| We currently have some inconsistencies with pages on stage hazards. [[Flying Man]], [[Kamek]], [[Charmander]], [[Cresselia]], [[Dark Emperor]], [[Dialga]], [[Fish]], [[King Bulblin]], [[Klaptrap]], [[Meta Ridley]], [[Palkia]], [[Porygon]], [[Rayquaza]], [[Registeel]], [[Reshiram]], [[Ridley]], [[Ultimate Chimera]], [[Yellow Devil]], and [[Zekrom]] all use images from their appearance in Super Smash Bros. for their infobox. However, [[Shellcreeper]], [[Shy Guy]], [[Sidestepper]], [[Whispy Woods]], [[Wolfen]], [[Peckish Aristocrab]], [[Piranha Plant]], [[Metal Face]], [[Great Fox]], [[Banzai Bill]], [[Birdo]], [[Nabbit]], and [[5-Volt]] use artwork from their source games. And then we have [[Arwing]], [[F-Zero Racers]], and [[Pidgit]], which don't have infoboxes at all. I excluded the stage hazards who fill other roles in other games (such as [[Chansey]]) since they seem to at least be consistent with other characters in their group, but we need to define whether or not stage hazards get their own artwork in infoboxes or not. [[User:TheNuttyOne|TheNuttyOne]] 15:03, 18 May 2018 (EDT)
| |
|
| |
| == Replacing "inferior" images? ==
| |
|
| |
| What's the approach to replacing an image that isn't exactly in "poor quality" but I have a better one?
| |
| ''Example:''
| |
|
| |
| <nowiki>[[Image:SSBU-Great_Plateau_TowerBattlefield.png|350px|]]</nowiki>
| |
|
| |
| This is generally a good image of the Battlefield Form of the stage, but I think a zoomed out picture would be better fitting:
| |
|
| |
| <nowiki>[[Image:SSBU-Great_Plateau_TowerBattlefield_ZoomOut.png|350px|]]</nowiki>
| |
|
| |
| I don't want to just remove something claiming "my image is better" out of the blue.
| |
| What are the rulings on this kind of situation?
| |
| [[User:Boogs|Boogs]] ([[User talk:Boogs|talk]]) 08:22, 20 November 2018 (EST)
| |
| :You click on the image you want to replace. Under "File history" there will be a blue link that reads: "Upload a new version of this file". Click on that and then follow the usual procedure. '''[[User:Voqéo|<span style="background:#000; color:white; padding:2px 6px;font-size:12px;">Voqéo</span>]][[User talk:Voqéo|<span style="background:#e70012; color:white; padding:2px 4px;font-size:12px;">T</span>]]''' 08:58, 20 November 2018 (EST)
| |
| ::Thanks for the help! [[User:Boogs|Boogs]] ([[User talk:Boogs|talk]]) 09:14, 20 November 2018 (EST)
| |
| :::No problem. I also already went ahead and replaced it and placed a deletion tag on the duplicate image you uploaded. '''[[User:Voqéo|<span style="background:#000; color:white; padding:2px 6px;font-size:12px;">Voqéo</span>]][[User talk:Voqéo|<span style="background:#e70012; color:white; padding:2px 4px;font-size:12px;">T</span>]]''' 09:23, 20 November 2018 (EST)
| |
|
| |
| == Native resolution ==
| |
|
| |
| It is currently an unwritten rule that images should be taken at native resolution, having overlap with the "represent the subject as "natural" as possible" and no "hacks or codes" policy as that is the primary means of non-native resolutions. Since that policy's addition in 2012, various means of capturing non-native resolutions have become much more common:
| |
| *Emulators are much more widespread and accessible, many of which allow for higher output resolutions either through built-in cheats or built into the emulator itself
| |
| *Gameplay capture has also become more prevalent, with companies engaging in the practice themselves. Recorded video can be saved and uploaded at whatever resolution the uploader desires
| |
| *Along with the above, said videos can be viewed at whatever resolution depending on their display device and then taking a screenshot; get a "4k image" of a 3DS game by watching a video in fullscreen on a 4k monitor
| |
|
| |
| As previously mentioned, these (and probably other) methods ''can'' be covered by the aforementioned policy, however it is easily up to interpretation. As such, it should be codified that images should not be at a higher resolution than the parent hardware is capable of producing under normal circumstances along with listing said resolutions: N64 = 320x240 (640x480 with Expansion Pack RAM, don't think Smash 64 makes use of it), GCN/Wii = 640x480; 3DS = 400x240 (top), 320x240 (bottom); Wii U = 1280x720 or 1920x1080 (Smash Wii U uses 1080p); Switch 1920x1080 (docked), 1280x720 (handheld); other consoles too if we extend to non-Smash titles. The primary exception to this would be images from official sources—they have direct means of producing higher resolutions as well as to preserve history.
| |
|
| |
| Lastly, in the event that upscaled media is allowed, I think a policy similar to WiKirby's should be employed. Specifically the [[wikirby:WiKirby:Image_standards#Upscaled images|upscaled image policy]] in that uspcaled images take lower precedence to native resolution images and that the upscaled images must explicitly mention that they are upscaled (the means of upscaling and by how much should also be listed on the image page). I'd also suggest restrict what means of uspcaling can be used to "nearest-neighbor" (namely for sprites) and hardware upscaling (primarily emulators)—various other interpolation methods can add pixels that don't exist (running into the no edited images policy) and AI upscaling does the same but can wrongly assume what the subject is and insert pixels that shouldn't exist.
| |
|
| |
| --[[User:CanvasK|CanvasK]] ([[User talk:CanvasK|talk]]) 12:11, December 11, 2022 (EST)
| |