Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SrgToMcpRenamer uses hardcoded path for nested jars

Open
#14 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Inspect src/main/java/net/minecraftforge/installertools/SrgMcpRenamer.java around line 132, then read the linked JarJar metadata definition to understand how nested jar paths are represented relative to the outer jar. Done means SrgToMcpRenamer reads those metadata paths and deobfuscates nested jars regardless of their location, rather than assuming META-INF/jarjar/.

Written by the indexing model from the issue text.

Description

The Issue

Currently, only nested jars under the META-INF/jarjar/ directory are deobfuscated by SrgToMcpRenamer.

https://github.com/MinecraftForge/InstallerTools/blob/dd66a7d92e635e654ad356b7a18e56149e339539/src/main/java/net/minecraftforge/installertools/SrgMcpRenamer.java#L132

While this is the most common folder for nested jars, JarJar metadata defines nested jar paths as paths relative to the outer jar's root, and therefore nested jars can be located anywhere in the jar. This breaks mods that place their nested jars in other paths than the mentioned folder.

Expected behavior

SrgToMcpRenamer is able to deobfuscate any nested jars regardless of their location, as specified by JarJar metadata. Rather than assuming all nested jars are in the META-INF/jarjar/ directory, we should open the jar's JarJar metadata file and read nested jar paths from it.

Dominant language
Java
Stars
6
Forks
8
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.