16 Directional Inputs would be adding increments of 0.5 to each number. + is top, - is bottom.
1.5 would be somewhere between 4 and 1.
-1.5 would be somewhere between 1 and 2.
It never occurred to me 8 directional inputs don't have an easy way of saying which direction to press / enter, unlike the lingo for 4 directional inputs.
4 Directional Inputs Code:
I propose we use the NumPad notation for 8 Directional Inputs.
The same 8 Directional Inputs Code would be:
Pros:
1.5 would be somewhere between 4 and 1.
-1.5 would be somewhere between 1 and 2.
It never occurred to me 8 directional inputs don't have an easy way of saying which direction to press / enter, unlike the lingo for 4 directional inputs.
4 Directional Inputs Code:
- WASD
- UDLR (Up, Down, Left, Right)
- ← →↑↓
- ← →↑↓↖ ↗ ↘ ↙
I propose we use the NumPad notation for 8 Directional Inputs.
The same 8 Directional Inputs Code would be:
- 4 6 8 2 7 9 3 1
- ↓↘ → + Punch
- 236P
Pros:
- You do not have to type out Unicode arrows on mobile devices. I doubt most keyboards support entering Unicode arrows by default, especially diagonal arrows.
- No need to memorize Unicode hex values.
- Faster to type.
- You don't see arrows being literally typed out on a normal basis anyway...
- Consistency. Unicode gets displayed differently on different devices.
- It may take a bit to get used to.
- Arrows are more intuitive.
Last edited: