[Suggestion] Pre-determined Java profiles
- 32 bit single core + low memory (lighter packs / vanilla + client side mods etc)
- 32 bit multi core (designed to take advantage of multiple cores)
- 64 bit single core
- 64 bit multi core
- Custom (base off the above profile) In this mode /all/ java parameters would be exposed and could be edited (have wildcard substitutions for some things, maybe 'magic cookie' format %x style stuff).
[Suggestion] Server Profiles
Have different server + pack profiles for different servers. Allow the end user to add a server by keyword, URI to an XML describing a server (would have server name, multiple resource overlays (configs, textures/sounds, etc), etc) and a overlay pinnings (resource packs of .zip / .jar files which would be extracted with default permissions in the relative Minecraft base folder).
This would make it easier for servers to distribute tweaked configs, waypoints, and possibly even mods which they have permission to distribute (E.G. open source and/or direct permission from the developer) as well as developers pushing out new mods to their test server, but against an existing pack.
The same general format for the XML descriptor could also be used to setup a pack initially, per resource specifying:
- display name
- description
- author
- mod homepage
- mod help link (wiki/etc)
- file name
- file size
- file checksums (please use a few algorithms as it's extremely unlikely for an exploit to exist which can compromise both without impinging upon archive functionality, currently SHA-1 and SHA-256 are recommended);
- output location (if empty/not specified it's an overlay to be extracted in to the base directory)
- source URI (if specified it's a direct download and not something in the FTB repository)
The file size and checksums could be used to determine if the file in question is already part of an existing downloaded mod pack and thus already cached locally; in that case the local copy would be used (hardlink / symlink / copy). File size difference and/or checksum/extraction error would trigger a re-download.
[Suggestion] Forced Rebuild
Move the saves and other local content out, forcefully rebuild the pack to baseline, re-install backup of saves/etc.