mirror of
https://gitlab.com/GameFeverOnline/mmm-nsf-changer.git
synced 2025-12-17 01:17:43 -04:00
added line in roadmap
This commit is contained in:
parent
e3d1c2b806
commit
3e3671b407
1 changed files with 1 additions and 1 deletions
|
|
@ -23,11 +23,11 @@ To use it just launch the executable file (if available for your os) or type "py
|
||||||
If you have any issues make a gitlab issue. There may be bugs.
|
If you have any issues make a gitlab issue. There may be bugs.
|
||||||
|
|
||||||
## Roadmap
|
## Roadmap
|
||||||
|
* fix restore_ogmusic so that it doesn't replace custom music. Possible windows only behaviour, testing is needed.
|
||||||
* consider the posibility of adding a alternate, custom music preserving, updater for Mega Man Maker.
|
* consider the posibility of adding a alternate, custom music preserving, updater for Mega Man Maker.
|
||||||
* improve the single-song actions to make them more persistant
|
* improve the single-song actions to make them more persistant
|
||||||
* modify restore_ogmusic so it is able to restore only the last change. Maybe config files will be needed for this.
|
* modify restore_ogmusic so it is able to restore only the last change. Maybe config files will be needed for this.
|
||||||
* make it so that if "you press apply music and then replace song" it checks for that and doesn't allow the "replaced song" to be reverted back to original.
|
* make it so that if "you press apply music and then replace song" it checks for that and doesn't allow the "replaced song" to be reverted back to original.
|
||||||
* "now playing" text
|
|
||||||
* ability to preserve changes through Mega Man Maker updates, by using a config file and/or a downloaded zip of the game.
|
* ability to preserve changes through Mega Man Maker updates, by using a config file and/or a downloaded zip of the game.
|
||||||
* stop using os.path in favour of pathlib
|
* stop using os.path in favour of pathlib
|
||||||
* switch to using a config file (or database) for keeping track of which tracks have been changed, that way only having one original_music folder and being able to *show* the user which song you used to replace which file.
|
* switch to using a config file (or database) for keeping track of which tracks have been changed, that way only having one original_music folder and being able to *show* the user which song you used to replace which file.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue