Functional Storage Unofficial Extended Life is a fork of Functional Storage (see its GitHub, Curseforge and Modrinth pages) that aims to solve the most problematic bugs of the 1.20.1 version. I don't plan to add any new features to it, but feel free to ask and I may consider it.

How to install

There are multiple ways to install Functional Storage UEL :

• You can create a new instance of Minecraft with Functional Storage UEL in it using the Curseforge app.
• If you already have an instance of Minecraft 1.20.1 with Forge 47.4.10, you can add Functional Storage UEL to it using either the Curseforge app or Prism launcher.
• You can also manually download the mod as a jar file from the Releases page or from Curseforge and copy it into the <Minecraft directory>/mods folder of your instance. Note that if you do that, you will also need to install Titanium 3.8.32 separately; you can download it from Curseforge or Modrinth.
• Finally, you can download the source code and compile it yourself to generate the jar file. More information on that below.

Changelog

You can see the full changelog here.

License

Functional Storage UEL is provided under an MIT license. You can find the full license text as well as the licenses of third-party works included in Functional Storage UEL here.

Credits

Functional Storage UEL reuses work made for Functional Storage and Storage Drawers.

How to build from source

In order to build the mod, you will need to have Java 17 JDK installed.

Using IntelliJ IDEA

1. On the IntelliJ IDEA homepage, click on Clone Repository, enter the URL of this repository (https://codeberg.org/esmenard/FunctionalStorage-UEL.git), and click on Clone.
2. Go to the Gradle Settings by clicking on the Gradle button on the right sidebar, then on the Build Tool Settings button (gear-shaped button at the right of the top bar), then on Gradle Settings, and make sure that Gradle JVM is set to Project SDK.
3. Go to the Terminal by clicking on the button in the bottom part of the left sidebar and run ./gradlew build (in Linux or Mac) or gradlew.bat build (in Windows). The mod's jar file will be located in the build/libs folder and named functionalstorage-uel.jar.

Using the Gradle CLI

You will first need to download the source code. The simplest way to do it is to have Git installed on your computer and to run git clone https://codeberg.org/esmenard/FunctionalStorage-UEL.git. You can also click on the three dots (on the right side of the page, above the search bar) to download it as a zip, tar.gz or bundle, or download the code of a release as a zip or tar.gz on the Releases page.

If you have multiple versions of Java installed on your computer, you will also need to set your JAVA_HOME environment variable to the correct version. If you kept the default installation folder when installing Java, the command you need to run is the following:

• Windows (legacy terminal):

set JAVA_HOME="C:\Program Files\Java\jdk-17"

• Windows (Powershell 7 terminal):

$env:JAVA_HOME = "C:\Program Files\Java\jdk-17"

To check that JAVA_HOME points to the right version, you can run:

• Windows (legacy terminal):

%JAVA_HOME%\bin\java.exe --version

• Windows (Powershell 7 terminal):

& $env:JAVA_HOME\bin\java.exe --version

The version number displayed should be some variant of Java 17.

Once everything is setup correctly, open the terminal from the FunctionalStorage-UEL folder you downloaded and build the mod by running:

• Linux/Mac:

./gradlew build

• Windows (legacy terminal):

gradlew.bat build

• Windows (Powershell 7 terminal):

.\gradlew.bat build

The mod's jar file will be located in the build/libs folder and named functionalstorage-uel.jar.

If you want to see the deprecaction warnings, add the following to build.gradle before building the mod:

allprojects {
 gradle.projectsEvaluated {
 tasks.withType(JavaCompile) {
 options.compilerArgs << "-Xlint:deprecation"
 }
 } 
}

If you want to see the warnings for unchecked or unsafe operations, add the following to build.gradle before building the mod:

allprojects {
 gradle.projectsEvaluated {
 tasks.withType(JavaCompile) {
 options.compilerArgs << "-Xlint:unchecked"
 }
 } 
}

How to fork

In order for the jar file to be automatically added as a release attachment when making a new release, you will need to do the following:

• Add a new token to your Codeberg account with the permissions write:repository and read:user and copy it.
• Go to your repository settings (button at the right of the top bar below the name of the repository), then click on Actions > Secrets > Add a secret, put WRITE_TOKEN in the "Name" field and paste the token inside the "Value" field.