Forum:Hitbox image collections: Difference between revisions

m
Line 6: Line 6:
#'''Support''' They're incredibly difficult to maintain and cause lag on mobile. Also, they provide limited information compared to the information provided by the individual move pages. If they were to be kept, they would need a substantial revamp to update them with everything else. Theoretically this can be done with a ****ton of template transclusions, but there's no way around the lag issue when even viewing them. Also, in what situation would it be more useful to see every single one of a character's attacks, instead of pulling up a specific attack you wish to reference? [[User:DekZek|<font color="MidnightBlue">'''Dek'''</font><font color="Blue">'''Zek'''</font>]] [[File:Dekzeksig.png|20px|link=User talk:DekZek]] 15:39, 30 November 2018 (EST)
#'''Support''' They're incredibly difficult to maintain and cause lag on mobile. Also, they provide limited information compared to the information provided by the individual move pages. If they were to be kept, they would need a substantial revamp to update them with everything else. Theoretically this can be done with a ****ton of template transclusions, but there's no way around the lag issue when even viewing them. Also, in what situation would it be more useful to see every single one of a character's attacks, instead of pulling up a specific attack you wish to reference? [[User:DekZek|<font color="MidnightBlue">'''Dek'''</font><font color="Blue">'''Zek'''</font>]] [[File:Dekzeksig.png|20px|link=User talk:DekZek]] 15:39, 30 November 2018 (EST)
#: If they cause lag on mobile, there's an easy solution to that: don't visit them on mobile, nobody's forcing you to visit the page or anything, and they work perfectly fine on desktop. The purpose of the hitbox collections is to show the hitboxes, if people want detailed information we could simply link the move names column to the move subpages for a detailed breakdown, no complicated transclusions necessary. Finally, it's useful for exactly that purpose, for viewing all of the moves on a convenient page instead of having to manually pull up every single attack you want to see (surprisingly enough, many people want to see ''all'' of the hitboxes for their main, as they plan on using more than 1 move for the entire match :p). ''[[User:Trainer Alex|<span style="color: blue;">'''Alex'''</span>]] the [[User talk:Trainer Alex|<span style="color: red;">'''Jigglypuff trainer'''</span>]]'' 15:58, 30 November 2018 (EST)
#: If they cause lag on mobile, there's an easy solution to that: don't visit them on mobile, nobody's forcing you to visit the page or anything, and they work perfectly fine on desktop. The purpose of the hitbox collections is to show the hitboxes, if people want detailed information we could simply link the move names column to the move subpages for a detailed breakdown, no complicated transclusions necessary. Finally, it's useful for exactly that purpose, for viewing all of the moves on a convenient page instead of having to manually pull up every single attack you want to see (surprisingly enough, many people want to see ''all'' of the hitboxes for their main, as they plan on using more than 1 move for the entire match :p). ''[[User:Trainer Alex|<span style="color: blue;">'''Alex'''</span>]] the [[User talk:Trainer Alex|<span style="color: red;">'''Jigglypuff trainer'''</span>]]'' 15:58, 30 November 2018 (EST)
#::The reason I am bringing up the transclusions is keeping the information up-to-date. As it currently stands, any edit on one would require an edit on another to make them contain the same information. [[User:DekZek|<font color="MidnightBlue">'''Dek'''</font><font color="Blue">'''Zek'''</font>]] [[File:Dekzeksig.png|20px|link=User talk:DekZek]] 16:01, 30 November 2018 (EST)


==Oppose==
==Oppose==
11,012

edits