File path mismatches in Crafty Controller updater

[dqni710]

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Crafty Controller

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/crafty-controller.sh)"

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📈 Which Proxmox version are you on?

pve-manager/9.0.3/025864202ebb6109

📝 Provide a clear and concise description of the issue.

The update script uses /opt/crafty-controller as Crafty's installation path, but in reality it is /var/opt/minecraft with Crafty 4 and onwards. This causes the update script to never function properly.

🔄 Steps to reproduce the issue.

Step 1: Run the script in a healthy Crafty Controller installation
Step 2: Observe

❌ Paste the full error output (if available).

✖️ No Crafty-Controller Installation Found!

🖼️ Additional context (optional).

No response

[michelroegl-brunner]

@CrazyWolf13

[CrazyWolf13]

@cz-cs The installation path is not in/var/opt/crafty.

The script is configured to use /opt/crafty

I just confirmed this on my own instance running since I created this script initially and uploaded it to this repo.

Can you run the following?

ls -al /var/opt/crafty
ls -al /opt/crafty
ls -al /opt/crafty/crafty-4

[dqni710]

Output:
ls: cannot access '/var/opt/crafty': No such file or directory
ls: cannot access '/opt/crafty': No such file or directory
ls: cannot access '/opt/crafty/crafty-4': No such file or directory

I think I updated Crafty myself, and the installer placed it in /var/opt/minecraft/crafty...
The script should be updated to accommodate the installer's default path, though. If there's a flag that can be set for /opt/crafty or something along those lines then that would be better. /var/opt is an unusual place to install

[CrazyWolf13]

@cz-cs Yeah that sounds like the problem to me, unfortunately that's a bit difficult now as this probably messed up all your paths.

We have a standard policy to place as much apps as possible under /opt/{appname} and as this works perfectly fine for crafty this is what we did here.

[CrazyWolf13]

As this fully removed your /opt/crafty path there isn't much we can do, maybe you have a backup before you messed with the installer, otherwise I suggest exporting the worlds and doing a fresh install.

As you messed around with the crafty installer to update the app, we can't really support this.