Skip to content

Conversation

@MartijnMuijsers
Copy link
Contributor

The code to convert legacy spawn eggs was a bit ridiculous, so I've improved it somewhat:

  • Instead of first setting maxData to 121 for LEGACY_MONSTER_EGG and then continue-ing every iteration of the loop (in other words, doing nothing for LEGACY_MONSTER_EGG), just continue the outer loop for LEGACY_MONSTER_EGG (in other words, do nothing for LEGACY_MONSTER_EGG)
  • Instead of going over all old spawn eggs inside the Material loop (so for every single material), just do it once at the end

The code to convert legacy spawn eggs was a bit ridiculous, so I've improved it somewhat:
* Instead of first setting maxData to 121 for LEGACY_MONSTER_EGG and then continue-ing every iteration of the loop (in other words, doing nothing for LEGACY_MONSTER_EGG), just continue the outer loop for LEGACY_MONSTER_EGG (in other words, do nothing for LEGACY_MONSTER_EGG)
* Instead of going over all old spawn eggs inside the Material loop (so _for every single material_), just do it once at the end
@MartijnMuijsers MartijnMuijsers requested a review from a team as a code owner January 9, 2026 22:27
@github-project-automation github-project-automation bot moved this to Awaiting review in Paper PR Queue Jan 9, 2026
@Astralchroma
Copy link
Contributor

should just get rid of Legacy Materials lol

@MartijnMuijsers
Copy link
Contributor Author

should just get rid of Legacy Materials lol

Imo we should just get rid of Material :p (I mean still including it, but replacing it with bytecode generated based on the item and block registries on the server)

I'm one of the people still running the same server and world file as in the beta get-CraftBukkit-jars-from-Jenkins days and I still have some of the same outdated plugin JARs that I can't just remove, so I have a personal interest in keeping the conversions in place~

@Astralchroma
Copy link
Contributor

decompile and update those plugins lol
or find modern versions

@masmc05
Copy link
Contributor

masmc05 commented Jan 9, 2026

Imo we should just get rid of Material :p

There is already ItemType and BlockType that are meant to replace Material one day and are already used in newer apis

@MartijnMuijsers
Copy link
Contributor Author

Imo we should just get rid of Material :p

There is already ItemType and BlockType that are meant to replace Material one day and are already used in newer apis

Yep yep that's what I mean :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Awaiting review

Development

Successfully merging this pull request may close these issues.

3 participants