Viv
5474ad0baa
README.md: Rewrite usage section for clarity
2024-02-07 12:42:02 -05:00
Viv
0383efea00
README.md: Mention SENOTE changes
2024-02-03 23:00:27 -05:00
Viv
47ef31fc5c
README.md: Make TakoTako 3.2.0 note more apparent
2024-01-13 12:01:08 -05:00
Viv
0fa2fda3d0
README.md: Update feature description
2023-10-17 22:03:31 -04:00
Viv
dcf74a45a2
README.md: Update "Features" section
2023-10-17 22:01:56 -04:00
Viv
300a58eb14
README.md: Add badges for code quality tools
2023-07-30 18:50:20 -04:00
Viv
03c8892243
README.md: Fix table row for A, B notes
2023-07-27 18:56:16 -04:00
Viv
e126494496
README.md: Restructure 'notes' part of table
2023-07-27 15:16:09 -04:00
Viv
c0442f3721
Fix behavior for the #LEVELHOLD command ( #54 )
...
Previously, I had translated the existing levelhold behavior in
WHMHammer's tja parsing code, assuming that it would produce the correct
behavior for fumen charts. However, that is not the case -- the behavior
is completely wrong.
So, this PR takes out all the old `flag_levelhold` behavior and instead
properly sets the `branch_info` bytes whenever #LEVELHOLD is present on
a branch.
This PR also prepares `shoto9.tja` for further testing, but I'm leaving
that for later...
Fixes #52 .
2023-07-27 15:02:19 -04:00
Viv
79cca3d75e
README.md: Try adding a Features section
2023-07-24 22:58:22 -04:00
Viv
7baa5ea859
README.md: Improve table spacing for mobile
2023-07-24 22:47:46 -04:00
Viv
d33562fef7
README.md: Update tja2bin crash commands
2023-07-24 17:33:24 -04:00
Viv
86f394e8ca
README.md: Update sim-specific wording
2023-07-24 17:28:04 -04:00
Viv
5ca4f080d3
README.md: Clarify #LEVELHOLD status
2023-07-24 17:22:14 -04:00
Viv
a09bfb87d4
Add test for 2P commands
2023-07-24 16:55:52 -04:00
Viv
6eb3676343
Add double Kusudama test
2023-07-24 16:46:21 -04:00
Viv
276bd0b70c
Add semi-support for sim-specific notes
2023-07-24 16:28:49 -04:00
Viv
f1cd73ebb9
README.md: Add table for file formats
2023-07-24 16:07:38 -04:00
Viv
45535d6fb1
README.md: Reformat tables using PyCharm
2023-07-24 16:00:04 -04:00
Viv
a4c9fb2b18
Add support for A/B notes (hands)
2023-07-24 15:57:58 -04:00
Viv
9f71a801ce
Update README.md
2023-07-24 09:21:23 -04:00
Viv
e848fc9499
README.md: Make emoji platform-agnostic
2023-07-24 01:02:53 +00:00
Viv
907ea43f16
Update README.md
2023-07-23 09:16:11 -04:00
Viv
3ae4bcc310
README.md: Play with <br>
2023-07-23 09:15:41 -04:00
Viv
ee7a3ae3cf
README.md: Remove ? from legend
2023-07-23 09:14:37 -04:00
Viv
b965633a73
README.md: Split tables into two
2023-07-23 09:11:10 -04:00
Viv
54d0ce402b
README.md: Rearrange table and fix command typos
2023-07-23 08:42:55 -04:00
Viv
eaa824cacf
README.md: Fix issues
2023-07-23 08:31:09 -04:00
Viv
2ca5406cdc
README.md: Shorten tagline
2023-07-22 21:05:26 -04:00
Viv
f4d5a52e5c
README.md: Style Note: paragraph
2023-07-22 21:03:18 -04:00
Viv
e1d562f5ef
README.md: Restructure sections, add badges, add command support
...
Fixes #43 .
2023-07-22 20:57:51 -04:00
Viv
5e313a3549
README.md: Fix logo colors
2023-07-22 18:23:57 -04:00
Viv
9c31f41066
README.md: Add newline
2023-07-22 10:44:26 -04:00
Viv
56df81b59b
README.md: Add logo, divider, smaller headers
2023-07-22 10:41:14 -04:00
Viv
ecfed22b38
Update README.md
2023-07-19 14:10:32 -04:00
Viv
ee265327de
README.md: Expand "Goals" section
2023-07-11 21:33:30 -04:00
Viv
1abd86885e
README.md: Update for 0.0.1 release.
2023-06-04 15:27:01 -04:00
Viv
84056aef27
README.md: Stop using README as issue tracker
...
I will move the issues to GitHub.
2023-06-03 11:07:27 -04:00
Viv
a66498a6db
Update README.md
2023-06-02 17:43:59 -04:00
Viv
383c2c6fd0
Update README.md
2023-06-02 17:43:59 -04:00
Viv
7c5cd18ac1
Update README.md
2023-06-02 17:43:59 -04:00
Viv
e856f302b7
Update README.md
2023-06-02 17:43:59 -04:00
Viv
5adcdd47d0
Update README.md
2023-06-02 17:43:59 -04:00
Viv
b4ab35a09a
Create README.md
2023-06-02 17:43:59 -04:00
