Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cape shows as "UPDATE YOUR MOD" despite having no new version #118

Open
SafetyFlux opened this issue Oct 10, 2023 · 11 comments
Open

Cape shows as "UPDATE YOUR MOD" despite having no new version #118

SafetyFlux opened this issue Oct 10, 2023 · 11 comments

Comments

@SafetyFlux
Copy link

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:

  1. Open Minecraft with the mod.
  2. Look at your cape.
  • Minecraft version: 1.19.2
  • Capes version: 1.5.2
  • Mod list: Optifine
  • Server: Singleplayer
@RemagOfficial
Copy link

why do you have optifine and the capes mod?

@SafetyFlux
Copy link
Author

Optifine improves my game performance. I don't use the Optifine cape

@RemagOfficial
Copy link

optifine also causes a ton of issues with mods, I'd recommend using alternative mods like sodium

@SafetyFlux
Copy link
Author

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.

@RemagOfficial
Copy link

then use rubidium

@SafetyFlux
Copy link
Author

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.

@RemagOfficial
Copy link

well why can't you update to 1.19.4 and use 1.5.3

@Madis0
Copy link

Madis0 commented Oct 12, 2023

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.

@james090500
Copy link

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.

@QianFuv
Copy link

QianFuv commented Jan 2, 2024

You can build version 1.19.2 yourself based on the changes made in this pull request: #97

@im-PJs
Copy link

im-PJs commented May 19, 2024

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! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants