-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rankups.yml suggestion #59
base: master
Are you sure you want to change the base?
Conversation
src/main/resources/rankups.yml
Outdated
# this will run when a player ranks up from A to B. | ||
#- 'say {PLAYER} well done for ranking up from {OLD_RANK} to {RANK}!' | ||
Bexample: | ||
ExampleA: # This name doesn't matter, it can be anything you want! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But this does matter. It must at least be unique from all the other headings.
src/main/resources/rankups.yml
Outdated
#- 'say {PLAYER} well done for ranking up from {OLD_RANK} to {RANK}!' | ||
Bexample: | ||
ExampleA: # This name doesn't matter, it can be anything you want! | ||
rank: 'A' # This is the rank where you start from. Use the displayname if you have it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be "Use the from displayname.<name>
if you use displaynames."
src/main/resources/rankups.yml
Outdated
Bexample: | ||
ExampleA: # This name doesn't matter, it can be anything you want! | ||
rank: 'A' # This is the rank where you start from. Use the displayname if you have it! | ||
next: 'B' # This is the rank where you go next. Read it as "From A to B" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change to "This is the next rank users are moved into."
This is my version of the auto generated rankups.yml file that I feel better shows how to use Rankup and its features to new users. It shows the new users the basics.
If there's a possibility that the tree is going to be null we should account for it rather than let the plugin spam like: Caused by: java.lang.NullPointerException: Cannot invoke "sh.okx.rankup.ranks.RankTree.asList()" because "this.tree" is null at sh.okx.rankup.ranks.RankList.getByPlayer(RankList.java:110) ~[Rankup-3.13.2.jar:?]
some requirements had their names listed in RankupPlugin.java this is useful, but was not consistent. Also, indentation was incorrect for all `new *Requirement` lines
thinking like an array programmer the Getter also enables other plugins/spigot to ask if Rankup supports a specific locale
No reason to add more visual complexity when we should simply ask for `getValueString()` instead of `getValuesString()`.
credit to @Voltmage for being a guinea pig
bump version
7c0d135
to
360e48d
Compare
c697bb0
to
3801db6
Compare
This is my version of the auto generated rankups.yml file that I feel better shows how to use Rankup and its features to new users. It shows the new users the basics.