Don't create new polymc.cfg on each start

[404NetworkError]

Role

I mantain a Scoop bucket that contains PolyMC.

Suggestion

Allow an existing hardlinked polymc.cfg file.

Benefit

To support Scoop installs

This suggestion is unique

• [X] I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.

You may use the editor below to elaborate further.

Scoop is a command-line installer similar to Chocolately. It allows for linking folders and files into a persist folder through junctions and hardlinks respectively.

An issue arises when setting the polymc.cfg as a hardlinked file in the persist folder. Each time the program starts up, the polymc.cfg file is re-created. I believe the reason is due to the initialization of the configuration file which creates a new file.

(This issue also occurs for MultiMC.)

[DioEgizio]

This is how it works on scoop-games:

https://github.com/Calinou/scoop-games/blob/master/bucket/polymc.json