I suggest one more thing. Considering this will help in modding, which means occasional rechecking, that after you check a map, it generates a mini database (can be in .txt, you just format it so it reads it just like it's scanning files) which is stored somewhere, probably let user decide where if you wish, or just generate it in the map folder (and then add a check when you run the program to see if such a file already exists in the folder, probably needs a standard name).
I suggest this, because usually it takes a lot of time to recheck something, and when a mod is complete and you want to recheck it, you can just see the differences between the 2 mapsets (i mean the mapset before and the mapset after the mod) easily from the .txt files (or whatever extension you feel using for this kind of work).
Also in addition to this, you can add an option to generate a new file every time (like standardname_1, standardname_2, etc, ofc original being _0) or to overwrite, depending what the user wants. This will let the user control the amount of "spam" he could get in that folder.
Oh and one more thing, when we're talking about snapping @timeline, I suggest that you make a check for 1/6ths and 1/8ths as well. They might be placed correctly, but usually (depends on the mapping experience obviously) it may not be, so you could just list where these are in case someone misses those.
This could add quite some effort to coding, but consider putting these to the "to do" list if you want, I think these are nice features. :3
I suggest this, because usually it takes a lot of time to recheck something, and when a mod is complete and you want to recheck it, you can just see the differences between the 2 mapsets (i mean the mapset before and the mapset after the mod) easily from the .txt files (or whatever extension you feel using for this kind of work).
Also in addition to this, you can add an option to generate a new file every time (like standardname_1, standardname_2, etc, ofc original being _0) or to overwrite, depending what the user wants. This will let the user control the amount of "spam" he could get in that folder.
Oh and one more thing, when we're talking about snapping @timeline, I suggest that you make a check for 1/6ths and 1/8ths as well. They might be placed correctly, but usually (depends on the mapping experience obviously) it may not be, so you could just list where these are in case someone misses those.
This could add quite some effort to coding, but consider putting these to the "to do" list if you want, I think these are nice features. :3