Describe the bug
When modpack name contains special characters, Minecraft will crash.

To Reproduce
Steps to reproduce the behavior:

1. create new modpack with special characters (*, !, $, &, etc)
2. press play
3. launch MC

Expected behavior
Not crash

About:

• OS: Windows 10
• App Version: 0.2.0-beta

Is your feature request related to a problem? Please describe.
It is inefficient to have to load the mod information every time a user wants to read the summary or add a mod even though the mod information has already been loaded

Describe the solution you'd like
I propose storing the mod info along with the HTML element to make later retrieving the data easier and more efficient

Describe the bug
After an update, the modpack data stored in projects.json is deleted.

To Reproduce
Steps to reproduce the behavior:

1. update

Expected behavior
Modpack data remain

About:

• OS: Windows 10
• App Version: 0.2.0-beta

Please assess the severity of the problem:
[ ] severe (crash, unplayable, feature not working, etc)
[x] minor (graphical, performance, etc)

Describe the bug
When renaming a modpack, it creates a new folder with the save data instead of renaming the current one

To Reproduce
Steps to reproduce the behavior:

1. Create new modpack + run
2. Rename modpack + run

Expected behavior
Rename folder

About:

• OS: Windows 10
• App Version: 0.2.0-beta

Please assess the severity of the problem:
[x] severe (crash, unplayable, feature not working, etc)
[ ] minor (graphical, performance, etc)

Describe the bug
In the Minecraft compatibility table, MC 1.12 and 1.12.2 are listed as separate entries, even though they are compatible. In addition, if two MC versions have the same number of compatible mods, the older MC version is being recommended

To Reproduce

1. Add mods (I used chisel)
2. View compatibility table under settings

About:

• OS: Windows 10 x64
• App Version: 0.3.0-beta

Please assess the severity of the problem:
[ ] severe (crash, unplayable, feature not working, etc)
[x] minor (graphical, performance, etc)

Describe the bug
Only affects > 1.12.2, when attempting to play, it will constantly prompt to install Forge. Trying to play directly from the launcher won't work either as it will produce and "invalid configuration" error.

To Reproduce
Steps to reproduce the behavior:

1. Create new modpack
2. Set modpack MC version > 1.12.2
3. Install mod
4. Run

Reason
The forge naming convention changed, meaning that the name gotten from the website does not match the name that was installed. Therefore, the launcher profile is pointing at a nonexistant version.

About:

• OS: Windows 10
• App Version: 0.3.2-beta

Please assess the severity of the problem:
[x] severe (crash, unplayable, feature not working, etc)
[ ] minor (graphical, performance, etc)

Is your feature request related to a problem? Please describe.
Currently, there is no way to find out what MC version each mod is compatible with or the best MC version.

Describe the solution you'd like
This feature would add a table in the settings tab that shows all the mods and which MC version they're compatible with, along with the most compatible version.

Describe alternatives you've considered
No alternative

Additional context
This is what it might look like:

	1.12	1.8	1.11
Mod 1	X
Mod 2		X
Mod 3	X		X