Wow, I haven't replied in this thread for a while. Lets see what I can find now xD
Adding [Colours] after [Colours] is already staated once (I know you didn't fix this, but I wanted to recheck this): If my code is like
[Colours][Colours]
then I get
- [Easy] :
olours]
, but if my code is like
[Colours]
[Colours]
then I get
- [Easy] :
[Colours]
just found that interesting. Not in the mood to check the source code to find out why, but there is no need for you to fix it.
Timing sections check is not implemented yet (see
viewtopic.php?p=922062#p922062 if you forgot) (not on your list of todo, so just reminding you)
Another stupid bugs that I doubt will come up:
If the timing sections are like this:
56713,-100,4,1,1,75,0,1
83947,-100,4,1,1,75,0,0
then the it will be read as
Kiai #1: Starts on 00:56:713, until the end
Feature Request:Warn if 2 notes are at the same point in time (Forgot if this was mentioned before)
Check for unused custom hitsounds (including bogus names) (was this supposed to be already implemented in 0.7? because it doesn't seem to work for me.)
Warn about sbed hitsounds (I know some users dislike them, so I a notficiation about them would be nice)
All the new features I tried seemed to work, so great job with 0.7. I wish you the best of luck as you move onward (and a modding companion would be nice)
Edit: I thought about the comboburst thing, and I think the code should probably go something like this.(going to be typing in visual basic style since I have been using that a lot lately)
If it ends in ".png" then
If the first few characters are "comboburst-" then
read the characters after the "comburst-" until you find '.'
if characters inbetween those 2 points are
not numbers then
trigger error
end if 'else ignore
end if
end if
so confusing without tabs, but I think you get the general idea