Skip to content

Conversation

SpaceWalkerRS
Copy link
Contributor

The isMinecraftClass check does not consider classes in the com.mojang.rubydung package (pre-classic) or the com.mojang.minecraft package (classic). This PR adds those checks.

@Player3324
Copy link
Contributor

Do we need the env stripping and access transformation for these versions? The former only makes sense if there is a separate dedicated server jar and the latter depends on whether the production jar has mapping dependent access issues.

@SpaceWalkerRS
Copy link
Contributor Author

The access transformations are needed for sure. In old versions the main class moved between packages a few times and if you want to keep the intermediary consistent you need to fix package access errors.

An argument could be made that the env stripping applies to classic (given it has dedicated servers) though we'd first have to confirm the client and server for these versions can be merged at all.

@Player3324
Copy link
Contributor

I turned it into a more generic property, please have a look at #1056

@Player3324
Copy link
Contributor

The changes were integrated with #1056

@Player3324 Player3324 closed this Jul 26, 2025
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

Successfully merging this pull request may close these issues.

2 participants