Make sure that the zipped modpack that you are uploading to AMP is not a zip of a directory containing the modpack files and directories, but rather a direct zip of those files and directories.However, depending on the modpack, some additional steps may be necessary. The recommended method above applies equally to adding server modpacks to AMP. You can symlink the Minecraft directory under the new instance’s datastore to your existing directory.Make sure to check the ownership/permissions to allow the user AMP is running as to have full read/write access. In the new instance’s datastore, there will be a file called MinecraftModule.kvp containing the configuration data for that module, you can edit the ServerPath setting to point to the absolute path on-disk of your existing server.Right click your server's jar file and select the 'Set as startup jar' option.Note that this option is only available when using the instance's File Manager, not the ADS File Manager. Right click the server.properties file and select the 'Import Configuration' option.Alternatively, go to the datastore directory for that instance and extract it as the user that AMP is running as. Extract the archive in-place (right click in the File Manager).Alternatively, upload the zip using AMP's integrated SFTP server. Drag the zip into the File Manager to upload it.This will reveal the contents of the Minecraft directory in the instance's datastore. Manage the new instance and go to the File Manager. ![]() Make a new Minecraft instance within AMP (or a McMyAdmin3 instance if you are using a legacy McMyAdmin2 licence key with AMP).Make a zip of your server, making sure the top level of the zip contains your jar file, server.properties, world directories and other data.If you have an existing Minecraft server that you want to manage with AMP, it's trivial to import it along with all of its configuration into a new AMP instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |