Cape shows as "UPDATE YOUR MOD" despite having no new version
SafetyFlux opened this issue ยท 11 comments
I've noticed that when a new version of this mod is available, the cape is replaced with a black and yellow texture containing the phrase "UPDATE YOUR MOD". However, as I'm playing on 1.19.2, the latest version of the mod isn't actually available.
Steps to reproduce the behavior:
- Open Minecraft with the mod.
- Look at your cape.
- Minecraft version: 1.19.2
- Capes version: 1.5.2
- Mod list: Optifine
- Server: Singleplayer
I can confirm that pull request #97 works! If you're unfamiliar with how to download and build this, follow these steps:
1. Create a new folder, open Command Prompt, and navigate to that folder.
2. In Command Prompt, clone the repository:
git clone https://github.com/MinecraftModDevelopmentMods/Capes.git
3. Navigate to the project directory:
cd Capes
4. Fetch the specific pull request:
git fetch origin pull/97/head:pr-97
5. Checkout the pull request branch:
git checkout pr-97
6. Build the project (this may take 5-10 minutes):
For Linux/Mac:
./gradlew build
For Windows:
gradlew.bat build
7. After building, navigate to the following directory:
\Capes\build\libs\capes-1.5.2+1.19.3.jar
8. Paste the JAR file into your Minecraft Mods folder and remove the old capes mod.
Congratulations, you're done! ๐
The reason for the issue is likely that one of the cape providers has changed their API URL and the Capes mod has not been updated for your Minecraft version to reflect this.
Workaround: use a different mod for now or update to the latest Minecraft version.
optifine also causes a ton of issues with mods, I'd recommend using alternative mods like sodium
I should probably specify that I'm playing on Forge. And no, I'm not interested in switching to Fabric. I have a bunch of others mods on (that I know aren't the problem) that are only available on this version of Forge.
None of this is relevant. With a clean install that has ONLY the Capes mod and its dependency, I still run into the issue. Optifine is not what's causing the problem.
This is due to my mod (MinecraftCapes) changing the API URl. I posted about this frequently in my discord and rasied an issue here: #96
It's likely the old version of Capes doesn't use the new API.
You can build version 1.19.2 yourself based on the changes made in this pull request: #97