Skip to content

Conversation

@PUDGE133
Copy link

@PUDGE133 PUDGE133 commented Nov 6, 2025

feat: TrySetRank method(and refactor)

Describe the changes
New TrySetRank method. Refactoring of the SetRank method.

What is the current behavior? (You can also link to an open issue here)
Unfortunately, the standard SetRank method requires creating a UserGroup object, which isn't always convenient. Specifying "null" isn't always a good idea, and it doesn't meet the requirements for clean and correct code. Furthermore, it's not entirely clear what happens if you specify null.
https://discord.com/channels/656673194693885975/1002713309876854924/1436117402965508147

What is the new behavior? (if this is a feature change)
It has become convenient to assign a rank (group).

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.


Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentations

Submission checklist

  • I have checked the project can be compiled(An error related to "RelativeBounds" prevented the compilation, but I didn't create this error.)
  • I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

  • I have checked no IL patching errors in the console

Other

  • Still requires more testing

@PUDGE133
Copy link
Author

PUDGE133 commented Nov 6, 2025

Why did all the old commits end up here if I synced the repository?

Copy link

@VALERA771 VALERA771 left a comment

Choose a reason for hiding this comment

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

Lgtm

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants