From d6ac1bccf150d2d7537cb68f1c8a2a7c1d8bc443 Mon Sep 17 00:00:00 2001 From: <> Date: Mon, 21 Oct 2024 10:21:56 +0000 Subject: [PATCH] Deployed 46b4663 with MkDocs version: 1.6.1 --- instructions/index.html | 15 +++++++++++---- search/search_index.json | 2 +- sitemap.xml.gz | Bin 127 -> 127 bytes 3 files changed, 12 insertions(+), 5 deletions(-) diff --git a/instructions/index.html b/instructions/index.html index 8efea11..ca55351 100644 --- a/instructions/index.html +++ b/instructions/index.html @@ -506,16 +506,23 @@

Using the CatPack If you are using a portable build of Prism, .. represents the directory where your portable build resides. - +
+
If you are using a fully installed build of Prism, .. is represented differently depending on OS: - +
+
- Windows: `%appdata%` +
- macOS: `~/Library/Application Support` +
- Linux: `~/.local/share` - +
+
However, if you use either of the following package managers, they will instead be located at: - +
+
- Scoop: `%HOMEPATH%/scoop/persist` - Note that the directory may be seen as `prismlauncher` instead of `PrismLauncher`. This is as intended. +
- Flatpak: `~/.var/app/org.prismlauncher.PrismLauncher/data` diff --git a/search/search_index.json b/search/search_index.json index e772568..d4dcac7 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -1 +1 @@ -{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Advanced CatPack crafter","text":"

This program simplifies creating an advanced Prism Launcher CatPack.

This site hosts documentation on how to use this program. You can navigate using the sidebar.

Other useful links:

"},{"location":"contributing/","title":"Contributing","text":"

Want to help? Great! To get started, follow these steps. This guide assumes you know how to use Git on a basic level.

We recommend the following when contributing:

"},{"location":"downloads/","title":"Downloads","text":"

The following page lists releases of this software.

"},{"location":"downloads/#historical-versions","title":"Historical versions","text":"

This is here for archival purposes. When new versions are released, it may take a little bit before this table is updated.

"},{"location":"downloads/#catpack-crafter-v100","title":"CatPack Crafter v1.0.0","text":"

Release notes: Initial release

Tag comparison

Prebuilt binaries:

Source code:

"},{"location":"instructions/","title":"How to use","text":"

Using the app should be fairly simple, so hopefully this will be a walk in the park.

"},{"location":"instructions/#1-locate-your-images","title":"1. Locate your images","text":"

It's a good idea to consolidate the images you will be using in a singular folder, or at least remember the path to get to them. Otherwise, you'll have take very long time trying to find the images you want.

"},{"location":"instructions/#2-using-the-app","title":"2. Using the app","text":"

Assuming you have already downloaded the program, run it and you'll be presented with a couple of options.

"},{"location":"instructions/#using-the-catpack","title":"Using the CatPack","text":"

Once your CatPack is created, you can move the folder with all the CatPack stuff into your Prism installation's catpacks folder. This should be located at ../PrismLauncher/catpacks, where .. varies depending on the form of Prism you are using:

\"What would .. mean in my case?\" If you are using a portable build of Prism, .. represents the directory where your portable build resides. If you are using a fully installed build of Prism, .. is represented differently depending on OS: - Windows: `%appdata%` - macOS: `~/Library/Application Support` - Linux: `~/.local/share` However, if you use either of the following package managers, they will instead be located at: - Scoop: `%HOMEPATH%/scoop/persist` - Note that the directory may be seen as `prismlauncher` instead of `PrismLauncher`. This is as intended. - Flatpak: `~/.var/app/org.prismlauncher.PrismLauncher/data`"},{"location":"run-from-source/","title":"Run from source","text":"

This page details how to run the program from source. If you have no idea what this page is saying, you probably shouldn't follow it.

"},{"location":"run-from-source/#setup","title":"Setup","text":"

In order to build, you'll need the following as prerequisites:

"},{"location":"run-from-source/#running-the-app","title":"Running the app","text":"

Once you have the \"App\" category of dependencies installed, you can simply run python script.py.

"},{"location":"run-from-source/#compiling-from-source","title":"Compiling from source","text":"

After installing dependencies in both the \"App\" and \"Compiling\" categories, you can run pyinstaller script.py to compile. Some additional arguments you might want to use are:

"},{"location":"run-from-source/#building-the-documentation-site","title":"Building the documentation site","text":"

You only need to install the dependencies listed in the \"Documentation\" category. After that, you can simply run mkdocs build, which will output a site/ folder that contains the fully built site.

Do NOT attempt to run mkdocs gh-deploy, as it will create a new branch and (attempt to) push it to the remote.

"}]} \ No newline at end of file +{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Advanced CatPack crafter","text":"

This program simplifies creating an advanced Prism Launcher CatPack.

This site hosts documentation on how to use this program. You can navigate using the sidebar.

Other useful links:

"},{"location":"contributing/","title":"Contributing","text":"

Want to help? Great! To get started, follow these steps. This guide assumes you know how to use Git on a basic level.

We recommend the following when contributing:

"},{"location":"downloads/","title":"Downloads","text":"

The following page lists releases of this software.

"},{"location":"downloads/#historical-versions","title":"Historical versions","text":"

This is here for archival purposes. When new versions are released, it may take a little bit before this table is updated.

"},{"location":"downloads/#catpack-crafter-v100","title":"CatPack Crafter v1.0.0","text":"

Release notes: Initial release

Tag comparison

Prebuilt binaries:

Source code:

"},{"location":"instructions/","title":"How to use","text":"

Using the app should be fairly simple, so hopefully this will be a walk in the park.

"},{"location":"instructions/#1-locate-your-images","title":"1. Locate your images","text":"

It's a good idea to consolidate the images you will be using in a singular folder, or at least remember the path to get to them. Otherwise, you'll have take very long time trying to find the images you want.

"},{"location":"instructions/#2-using-the-app","title":"2. Using the app","text":"

Assuming you have already downloaded the program, run it and you'll be presented with a couple of options.

"},{"location":"instructions/#using-the-catpack","title":"Using the CatPack","text":"

Once your CatPack is created, you can move the folder with all the CatPack stuff into your Prism installation's catpacks folder. This should be located at ../PrismLauncher/catpacks, where .. varies depending on the form of Prism you are using:

\"What would .. mean in my case?\" If you are using a portable build of Prism, .. represents the directory where your portable build resides. If you are using a fully installed build of Prism, .. is represented differently depending on OS: - Windows: `%appdata%` - macOS: `~/Library/Application Support` - Linux: `~/.local/share` However, if you use either of the following package managers, they will instead be located at: - Scoop: `%HOMEPATH%/scoop/persist` - Note that the directory may be seen as `prismlauncher` instead of `PrismLauncher`. This is as intended. - Flatpak: `~/.var/app/org.prismlauncher.PrismLauncher/data`"},{"location":"run-from-source/","title":"Run from source","text":"

This page details how to run the program from source. If you have no idea what this page is saying, you probably shouldn't follow it.

"},{"location":"run-from-source/#setup","title":"Setup","text":"

In order to build, you'll need the following as prerequisites:

"},{"location":"run-from-source/#running-the-app","title":"Running the app","text":"

Once you have the \"App\" category of dependencies installed, you can simply run python script.py.

"},{"location":"run-from-source/#compiling-from-source","title":"Compiling from source","text":"

After installing dependencies in both the \"App\" and \"Compiling\" categories, you can run pyinstaller script.py to compile. Some additional arguments you might want to use are:

"},{"location":"run-from-source/#building-the-documentation-site","title":"Building the documentation site","text":"

You only need to install the dependencies listed in the \"Documentation\" category. After that, you can simply run mkdocs build, which will output a site/ folder that contains the fully built site.

Do NOT attempt to run mkdocs gh-deploy, as it will create a new branch and (attempt to) push it to the remote.

"}]} \ No newline at end of file diff --git a/sitemap.xml.gz b/sitemap.xml.gz index 077e3cec1847f3c7f1c332e48384917cabb57cdb..a2964eb081d1eeaabbd4d6b4e2fad13172d66715 100644 GIT binary patch delta 13 Ucmb=gXP58h;AogBI+48s02|x`{r~^~ delta 13 Ucmb=gXP58h;9&3&naExN02f08EC2ui