-
Notifications
You must be signed in to change notification settings - Fork 32
How Tos
Lodestone checks for the existence of an environmental variable LODESTONE_PATH
upon startup. If said env var exists it will use that path. If not, it will default to your home directory.
On *nix: ~/.lodestone
On Windows: %userprofile%/.lodestone
Lodestone checks for the existence of an environmental variable LODESTONE_PATH
upon startup. If said env var is found it will create that directory and use that as the storage location. If the env var is not found it will default to .lodestone
directory under the user's home directory.
If you are on *nix:
export LODESTONE_PATH=[replace this with your desired path]
If you are on Windows:
search for "env" in your search bar, open "Edit environmental variables for your account"
Click on "new"
Put LODESTONE_PATH
as the name, and the absolute path to your directory as the value
To configure SSL/HTTPS with Lodestone Core, you'll need to place your SSL certificate and key files in a specific location and format. Here's the detailed step-by-step guide:
-
Create a directory named
tls
under the main Lodestone directory (LODESTONE_PATH). -
Store your SSL certificate and key files within this newly created
tls
directory. They should be named ascert.pem
andkey.pem
respectively.Note: If you have a
fullchain.pem
or another certificate file, you can simply rename it tocert.pem
. -
Once the certificate and key files are in place, start Lodestone Core. During the boot-up sequence, you should observe a message indicating either "TLS enabled" or "Invalid TLS config".
- "TLS enabled" confirms that the SSL/HTTPS setup was successful.
- "Invalid TLS config" signifies that there was a problem with the configuration. If you encounter this, double-check the certificate and key files, their names, and their location.
-
Depending on your SSL certificate source, you may need to do the following:
-
Self-signed certificate: If you're using a self-signed certificate, you'll need to manually add it to your browser's trust store to avoid security warnings.
-
Publicly trusted certificate (e.g., Let's Encrypt): If your certificate comes from a publicly trusted Certificate Authority (CA) such as Let's Encrypt, you should remove the existing Lodestone Core instance from your dashboard and re-add it using its domain name.
-
- Create your Lodestone instance
- Get the Minecraft version of the modpack
- Get the modloader of the modpack such as fabric or forge
- Create an instance for that modloader and that Minecraft version
- Run the Lodestone instance
- Once running, Stop the Lodestone instance
- Delete the mods folder from the instance if it exists
- Download the modpack
- If they have a version that is specifically for servers, download that one, otherwise download the latest version for your modloader and Minecraft version
- If you downloaded the modpack from Modrinth, add
.zip
on the end of the downloaded file name- MAKE SURE YOU HAVE FILE EXTENTIONS TURNED ON If you don't, follow this: https://windowsdigitals.com/how-to-change-or-remove-file-extension-in-windows-11/
- Unzip the file
- Open the unzipped file and go into the overrides folder
- Select the
mods
folder and theconfig
folder and zip them - Upload the resulting zip file to lodestone
- Left click the zip file and press
Unzip here
Done. If you are getting errors feel free to ask in the support forum on the lodestone discord server