Skip to content

Add and clarify Attribute#getDefaultValue#13345

Merged
Lulu13022002 merged 3 commits into
PaperMC:mainfrom
Warriorrrr:feat/attribute-defaultvalue
May 31, 2026
Merged

Add and clarify Attribute#getDefaultValue#13345
Lulu13022002 merged 3 commits into
PaperMC:mainfrom
Warriorrrr:feat/attribute-defaultvalue

Conversation

@Warriorrrr
Copy link
Copy Markdown
Member

Closes #13343

@Warriorrrr Warriorrrr requested a review from a team as a code owner November 24, 2025 19:08
@github-project-automation github-project-automation Bot moved this to Awaiting review in Paper PR Queue Nov 24, 2025
Copy link
Copy Markdown
Member

@Malfrador Malfrador left a comment

Choose a reason for hiding this comment

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

Not sure the deprecation is entirely necessary but overall lgtm.

Maybe exposing the min/max value would be cool in the future, but thats probably better for a separate PR. Surprised to learn that isn't API already.

@electronicboy
Copy link
Copy Markdown
Member

I think it is a point of confusion leaving it there because the default isn't tied to the attribute instance but to the attribute itself, having it there is just misleading

@Lulu13022002 Lulu13022002 force-pushed the feat/attribute-defaultvalue branch from cf56a46 to 23f48c4 Compare May 9, 2026 18:56
@Lulu13022002 Lulu13022002 force-pushed the feat/attribute-defaultvalue branch from 23f48c4 to 5565f84 Compare May 31, 2026 16:56
@Lulu13022002 Lulu13022002 merged commit 10a73fe into PaperMC:main May 31, 2026
4 checks passed
@github-project-automation github-project-automation Bot moved this from Awaiting review to Merged in Paper PR Queue May 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Merged

Development

Successfully merging this pull request may close these issues.

Default value for the movement_speed attribute is not correct

5 participants