Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@JRoy
Copy link
Member

@JRoy JRoy commented Jun 16, 2024

really only waiting on item aliases and maybe easter eggs

@JRoy JRoy added the type: enhancement Features and feature requests. label Jun 16, 2024
@JRoy JRoy added this to the 2.21.0 milestone Jun 16, 2024
Copy link

@CyberFlameGO CyberFlameGO left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Enchantments described in output aren't correct (though are applied correctly) - in my opinion should be a blocker to merging

Tested on 2.21.0-dev+99-07f97cf

Tested on Purpur build 2246 as well as Paper:

This server is running Paper version 1.21-37-master@dd49fba (2024-06-24T02:08:49Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version
image image Ignore riptide that was just testing image

@Evidentsinger14
Copy link
Member

image
https://essentialsx.net/dump.html?id=07510f47d29740c49790040ead07e6c6 - Confirmed, this is on a 100% default server.

@JRoy
Copy link
Member Author

JRoy commented Jun 24, 2024

Enchantments described in output aren't correct (though are applied correctly) - in my opinion should be a blocker to merging

Tested on 2.21.0-dev+99-07f97cf

Tested on Purpur build 2246 as well as Paper:

This server is running Paper version 1.21-37-master@dd49fba (2024-06-24T02:08:49Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version

image image Ignore riptide that was just testing image

Should be fixed as of latest commit, was a CraftBukkit bug/change that causes Enchantment#getName to return the wrong name for enchantments. So for example, currently Enchantment.SHARPNESS will return RIPTIDE. Switched to using namespaced keys for 1.13+.

Enchantment#getName is deprecated and gives the wrong names for enchantments starting in 1.21
@CyberFlameGO
Copy link

Seems good to me - looks like the update check for feature branches doesn't work too well (didn't seem to recognise the new commit) but that is probably unrelated/out of scope for the PR

@Tsaitou7361
Copy link

Enchantments described in output aren't correct (though are applied correctly) - in my opinion should be a blocker to merging

Tested on 2.21.0-dev+99-07f97cf

Tested on Purpur build 2246 as well as Paper:

This server is running Paper version 1.21-37-master@dd49fba (2024-06-24T02:08:49Z) (Implementing API version 1.21-R0.1-SNAPSHOT)
You are running the latest version

image image Ignore riptide that was just testing image

I know this, when I enchanting breach, it shows Projectile Protect...

@mdcfe mdcfe merged commit b392f03 into 2.x Jun 29, 2024
@JRoy JRoy deleted the mc/1.21 branch June 29, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: enhancement Features and feature requests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants