Editing Talk:Hitlag
From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
|
You aren't logged in. While it's not a requirement to create an account, doing so makes it a lot easier to keep track of your edits and a lot harder to confuse you with someone else. If you edit without being logged in, your IP address will be recorded in the page's edit history. | |
 Log in
|
Create account
| |
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 17: | Line 17: | ||
This was brought up before, but I think it bears being considered again, as it is still relevant to this day. The term "freeze frame" is a pretty niche and even rather juvenile one. It is my understanding that the only reason we still call it freeze frames instead of hitlag is because of the potential for hitlag to be confused with hitstun. However, aside from the fact that Nintendo is doing a pretty good job at making sure of that themselves, I don't think this is a particularly good reason to use a more obscure term. Of the 3 terms used (hitlag, hitstop and freeze frames), freeze frames appears to be the least commonly used in my experience, and I think it's pretty clear to anyone that hitlag is the most commonly used, especially with Ruben's script viewer becoming more and more widely used as a resource by the community. We tend to use the most common community terms in our page titles, and I don't think there's a particularly good reason for this to be an exception, especially when the alternative we are using is such a poor one. ''[[User:Alex the weeb|<span style="color: blue;">'''Alex'''</span>]] the [[User talk:Alex the weeb|<span style="color: red;">'''Weeb'''</span>]]'' 05:47, February 21, 2020 (EST) | This was brought up before, but I think it bears being considered again, as it is still relevant to this day. The term "freeze frame" is a pretty niche and even rather juvenile one. It is my understanding that the only reason we still call it freeze frames instead of hitlag is because of the potential for hitlag to be confused with hitstun. However, aside from the fact that Nintendo is doing a pretty good job at making sure of that themselves, I don't think this is a particularly good reason to use a more obscure term. Of the 3 terms used (hitlag, hitstop and freeze frames), freeze frames appears to be the least commonly used in my experience, and I think it's pretty clear to anyone that hitlag is the most commonly used, especially with Ruben's script viewer becoming more and more widely used as a resource by the community. We tend to use the most common community terms in our page titles, and I don't think there's a particularly good reason for this to be an exception, especially when the alternative we are using is such a poor one. ''[[User:Alex the weeb|<span style="color: blue;">'''Alex'''</span>]] the [[User talk:Alex the weeb|<span style="color: red;">'''Weeb'''</span>]]'' 05:47, February 21, 2020 (EST) | ||
:Your argument seems to be based on the premise that "freeze | :Your argument seems to be based on the premise that "freeze frames" is a "poor" and "juvenile" choice. You have provided no evidence of this. Conversely, here are the Google results I am currently seeing: | ||
:*<code>Smash Bros "hitlag"</code>: 4,880 | :*<code>Smash Bros "hitlag"</code>: 4,880 | ||
:*<code>Smash Bros "hitstop"</code>: 2,630 | :*<code>Smash Bros "hitstop"</code>: 2,630 | ||
