Ranks

[SymbioteSpidey]

I don't know how to setup this rank up config... It's a lot more complex than it should be compared to the autorank plugin on spigot.

All I want to do is let default players rank up to Verified after playing for 24 hours. Everyone who joins the server is auto in the default group of luckperms.
I don't know why there's all "on leave rank node" stuff, it makes no sense

This is my code:

{
"starting_rank_node_id": "default",
"no_rank_status_text": "[Passed Verified Rank]",
"graph": [
{
"enable": true,
"id": "default",
"display_name": "Default",
"description": "Current Rank:\nDefault",
"next_rank_nodes": [
"Verified"
],
"requirements": [],
"events": {}
},
{
"enable": true,
"id": "Verified",
"display_name": "Verified",
"description": "This is the first line.\nThis is the second line.",
"next_rank_nodes": [],
"requirements": [
{
"description": "Play for 24 Hours.",
"commands": [
"<=? %player:name% 1728000 %player:statistic_raw minecraft:play_time%"
]
}
],
"events": {
"on_enter_this_rank_node_commands": [
"lp user %player:name% parent add Verified",
"send-broadcast <#FFA1F5>Player %player:name% has played for 24 Hours and has become Verified"
],
"on_first_enter_this_rank_node_commands": [
"when-online %player:name% send-message %player:name% You have become Verified",
"when-online %player:name% give %player:name% minecraft:diamond 5"
]
}
}
],
"MOD_VERSION": "12.31.0"
}

[sakurawald]

I don't know how to setup this rank up config... It's a lot more complex than it should be compared to the autorank plugin on spigot.

I agree, the default config tries to provide a full example with 1 starting rank and 2 possible ranking-up paths to the expert rank.

In the default config, it's not a simple example with a linear path (Only 1 possible ranking-up path).
There are 2 possible ranking-up paths in the default config, and that's why the default config looks so complex.

All I want to do is let default players rank up to Verified after playing for 24 hours.

This is an example with only 3 nodes, 1 possible ranking-up path: newbie -> middle -> expert
I have posted it in https://pastebin.com/a8482JsJ

Everyone who joins the server is auto in the default group of luckperms.

Sets the starting_rank_node_id id to the rank you want to assign for new players.

I don't know why there's all "on leave rank node" stuff, it makes no sense

For a given rank like rank-5, you may want to assign a my-custom-permission.rank-5 on enter this rank, and you may need to remove this my-custom-permission.rank-5 permission on leave this rank. (For any reason the player leaves the rank-5 rank)

[SymbioteSpidey]

Can you please create an example with just default -> verified? Using luckperms parent add command

default is what you have on join

[sakurawald]

https://pastebin.com/iRQvvH0p

1. This is the example config file, which defines 2 ranks named unverified and verified.
   1.a. For unverified rank, there is no requirement to enter this rank.
   1.b. For verified rank, the requirement to enter this rank is to play for 1440 seconds.

2. When a new player joins the server, its rank is defaulting to none. You can use command_scheduler module, to define a job to execute the /rank try-up %player:name% command automatically.

Note that the /rank try-up %player:name% command will try to rank up for the specified player, if there is only 1 possible ranking-up path. (In your case, there is exactly only 1 possible ranking-up path, so this command will auto-rankup the player from none rank to unverified rank, and then if the requirements are met, it will rank-up the player to verified rank

[SymbioteSpidey]

I don't want the players to be placed in a none rank though.

I just want it to make players verified through luckperms after 24 hours of playing as long as their current rank on luckperms is default

[sakurawald]

I don't want the players to be placed in a none rank though.

Yes, that's what the /rank try-up %player:name% command does.
This command will try to auto-rank-up the rank of the specified player.

The only thing you need to do, is to use command_scheduler to define a job, to execute this command schedully.

This is an example to define a job to run /rank try-up %player:name% command for each online players.

{
  "jobs": [
    {
      "enable": true,
      "name": "auto_rank_up_job",
      "remaining_runs": 999999999999,
      "schedules": [
        "0 */3 * ? * *"
      ],
      "command_groups": [
        [
          "foreach rank try-up %player:name%"
        ]
      ]
    }
  ],
  "MOD_VERSION": "13.0.0"
}

[SymbioteSpidey]

Would it be possible to change the autorank system to be more like the plugin on spigot? It's a lot more simple and will do wonders to help new server owners using fuji. The current system is more complicated than it needs to be. It should just link directly to luckperms like how autorank does and if the player has default, they auto get put to Verified using the luckperms command and play a broadcast, that's it

https://www.spigotmc.org/resources/autorank.3239/

[sakurawald]

Would it be possible to change the autorank system to be more like the plugin on spigot? It's a lot more simple and will do wonders to help new server owners using fuji. The current system is more complicated than it needs to be. It should just link directly to luckperms like how autorank does and if the player has default, they auto get put to Verified using the luckperms command and play a broadcast, that's it

https://www.spigotmc.org/resources/autorank.3239/

After having a second thought, and re-analyze what you actually need.

Let's say, the rank module is designed to handle complex ranking system, which supports rank-up, rank-down, and multi possible rank paths.

If a player meet some requirements, you want to run some commands on it exactly once.
In this case, you can use command_state module, to define a state named is-verified, and define the requirements to enter this state. (Since the playtime is an accumulating value, the player won't have chance to leave this is-verified state)

The full example for fuji/modules/command_state/config.json file is

{
  "state_descriptors": [
    {
      "enable": true,
      "id": "is-verified",
      "definition": {
        "predicate_commands": [
          "<=? %player:name% 1728000 %player:statistic_raw minecraft:play_time%"
        ]
      },
      "update_interval_seconds": 30,
      "events": {
        "on_enter_this_state_commands": [
          "lp user %player:name% parent add Verified",
          "send-broadcast <#FFA1F5>Player %player:name% has played for 24 Hours and has become Verified",
          "send-message %player:name% You have become Verified",
          "give %player:name% minecraft:diamond 5"
        ],
        "on_leave_this_state_commands": []
      }
    }
  ],
  "MOD_VERSION": "13.1.0"
}

This is the full example, it's much simple than the rank plugin, and meet what you need.

[SymbioteSpidey]

Do I use this instead of the previous code? This doesn't have any lp parent add command (that's the command to add a group)

[sakurawald]

Do I use this instead of the previous code? This doesn't have any lp parent add command (that's the command to add a group)

Yes. You can insert the lp group add command in the on_enter_this_state_commands.
Once a player meets the requirements of is-verified state, it will enter the is-verified state, and execute the on_enter_this_state_commands.

[sakurawald]

Do I use this instead of the previous code? This doesn't have any lp parent add command (that's the command to add a group)

I have updated the example to reflect the lp interface command.