Disable Fly Mode (Potentially others)

[itzrobotix]

Hey, I find myself with a problem. I would like to give players temporary access to certain commands such as /fly, which I can do no problem with luckperms settemp permissions, however when the permission is removed, if the player was still in fly mode that would remain. So their access to be able to fly would remain, sadly this functionality is something outside of the scope of Luckperms but I wondered if there's anything Fuji could implement to accommodate this. Maybe even something as simple as resetting these things on login/logout or maybe even a customer implementation where permissions could be checked during login/logout and custom responses get executed. Like I have made a customer /nightvision command that gives the nightvision effect on a toggle. If I could give someone temporary access to this and then when that permission expires have it disabled again for them for example, that would be really cool. What do you think?

[sakurawald]

The tempfly is not directly supported. Currently a workaround is to setup a state using command_state module.

The example is

    {
      "enable": true,
      "id": "can-use-fly-command",
      "definition": {
        "predicate_commands": [
          "has-perm? %player:name% fuji.permission.fly"
        ]
      },
      "update_interval_seconds": 3,
      "events": {
        "on_enter_this_state_commands": [
          "send-message %player:name% <green>You have gained access to `/fly` command."
        ],
        "on_leave_this_state_commands": [
          "send-message %player:name% <red>You temporary `/fly` command access has expired.",
          "run as fake-op %player:name% fly false"
        ]
      }
    }

This example does:

1. Define a state named can-use-fly-command, its definition is to execute the has-perm? command, to check if the target player has the specified permission. (So it works with luckperms's temporary permission
2. Specify the check interval to 3 seconds, so the predicate commands will be executed every 3 seconds, to check the value of this state
3. Specify the commands to be executed, when a player enters or leaves this state.

[sakurawald]

If you don't want to setup the command state module, then you can use a single command to achieve this.

/IF NOT has-perm? SakuraWald fuji.permission.fly THEN run as fake-op %player:name% --silent true fly false ELSE nop

You can insert this command in command_event module, to execute it on player joined the server.

1. /IF ... THEN ... ELSE to check the condition (command_meta.IF)
2. /NOT to reverse the result of predicate-command (command_meta.NOT)
3. /has-perm? is a predicate-command, to test whether the target player has specified permission (predicate)
4. /run as fake-op %player:name% --silent true is used to switch command context, and silent the /fly command. (command_meta.run)
5. /fly false is used to turn off the flying state (command_toolbox.fly)
6. /nop is used to do nothing, as a dummy command. (command_meta.NOP)
   Finally, the command_event to execute commands on player joined.

[itzrobotix]

Thanks, I will look to implement the command state example as that seems like it will be more consistent at removing the states effectively.

[itzrobotix]

Just implemented it now, looks to work perfectly! This is amazing functionality you've coded into Fuji I love it!