Would it be possible to support a more traditional input notation style, maybe with a different code-block name?

• Allow joining movement and hit buttons with an optional +.
  So, instead of uf,3+4, it would be uf+3+4 and as + is optional uf3+4 would also be the same.
  With the traditional notation style, uf,3+4 would actually be the same as uf,n,3+4.
• Use ~ for sliding motion.
  So, instead of [,3,4,], it would be 3~4.
• Comma followed by a space separates input groups instead of -
  So, instead of 1,-,1+2,-,[,3,4,] you would write 1, 1+2, 3~4
  The comma before the space would be optional, so you could write
  This way you could write:
  • d+1+2 [AOP] - pressing the buttons leads to AOP - no green arrow
  • 1, [AOP] - after a 1 jab, you should go into AOP - green arrow between 1 and AOP
• Textual hints in brackets and quotes (so it doesn't render brackets), stances in square brackets.
  For example: SSR, d1+2 [AOP], "continue on whiff, otherwise cancel stance", uf3 (launch)
  This would allow the comma+space combination to be used in hints.
• Diagonal input aliases with a slash
  So, instead of f,n,d,df+2 you could also write f,n,d,d/f+2
  Wouldn't personally use it, but some do and it's probably easy to add.

Full example:

```tekken-classic
"Flowchart 1"
SSR, d1+2 [AOP], "continue on whiff, otherwise cancel stance", uf3 (launch)
"Damage xx"
```

Btw, cool plugin!