RogerDodger (talk | contribs) No edit summary |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
The Punishers page lists f,n,d,df:2 as an i13 punish but pewgf punish is not possible with that input; to link with the Movelist page correctly the Movelist page needs to distinguish pewgf (f,n,df#2 or f,d,df#2) from regular ewgf. | The Punishers page lists f,n,d,df:2 as an i13 punish but pewgf punish is not possible with that input; to link with the Movelist page correctly the Movelist page needs to distinguish pewgf (f,n,df#2 or f,d,df#2) from regular ewgf. | ||
Do we list the ''possible'' +/- for a given move? E.g. normally ewgf is +5 but can be +6 and we typically write +5~+6 for that range. Is documenting the range preferred or is there a particular precedent for listing the common frame data (preferring writing +5 for ewgf for example)? | Do we list the ''possible'' +/- for a given move? E.g. normally ewgf is +5 but can be +6 and we typically write +5~+6 for that range. Is documenting the range preferred or is there a particular precedent for listing the common frame data (preferring writing +5 for ewgf for example)? [[User:Aglimagli|Aglimagli]] | ||
: Hit/block/ch frames are better off not showing the variable amounts unless the meaty situation is common. It's already implied by the multiple active frames. See [[Notation#Frame_advantage]]. For punishers, can use some overrides for EWGF as it's an unusual case. Separate movelist entry isn't required for that. For movelist, I'd probably list EWGF as f,n,df#2 with f,n,d,df#2 noted as an alternate input (or maybe vice versa?). [[User:RogerDodger|RogerDodger]] ([[User talk:RogerDodger|talk]]) 00:04, 30 January 2024 (UTC) | : Hit/block/ch frames are better off not showing the variable amounts unless the meaty situation is common. It's already implied by the multiple active frames. See [[Notation#Frame_advantage]]. For punishers, can use some overrides for EWGF as it's an unusual case. Separate movelist entry isn't required for that. For movelist, I'd probably list EWGF as f,n,df#2 with f,n,d,df#2 noted as an alternate input (or maybe vice versa?). [[User:RogerDodger|RogerDodger]] ([[User talk:RogerDodger|talk]]) 00:04, 30 January 2024 (UTC) | ||
From my testing, [[Kazuya_movelist#Kazuya-df+3,2,1|df+3,2,1]] is -14 on block, not -18. I am hesitant to change this as I'm still relatively new to the game, but I could not replicate a -18 on block for this move. ([[User:Aldrenean|Aldrenean]]) 2024-08-15 | |||
Latest revision as of 20:32, 15 August 2024
f,n,d,df:2 should be changed to f,n,d,df#2 for correct input notation of Electric Wind God Fist's just frame. The Punishers page lists f,n,d,df:2 as an i13 punish but pewgf punish is not possible with that input; to link with the Movelist page correctly the Movelist page needs to distinguish pewgf (f,n,df#2 or f,d,df#2) from regular ewgf.
Do we list the possible +/- for a given move? E.g. normally ewgf is +5 but can be +6 and we typically write +5~+6 for that range. Is documenting the range preferred or is there a particular precedent for listing the common frame data (preferring writing +5 for ewgf for example)? Aglimagli
- Hit/block/ch frames are better off not showing the variable amounts unless the meaty situation is common. It's already implied by the multiple active frames. See Notation#Frame_advantage. For punishers, can use some overrides for EWGF as it's an unusual case. Separate movelist entry isn't required for that. For movelist, I'd probably list EWGF as f,n,df#2 with f,n,d,df#2 noted as an alternate input (or maybe vice versa?). RogerDodger (talk) 00:04, 30 January 2024 (UTC)
From my testing, df+3,2,1 is -14 on block, not -18. I am hesitant to change this as I'm still relatively new to the game, but I could not replicate a -18 on block for this move. (Aldrenean) 2024-08-15