#(Revolver) LuckPerms necessary permissions for Denizen?

95 messages · Page 1 of 1 (latest)

old sentinel
#

Players on my server have very minimal ability to interact with denizen. They couldn’t interact with denizen npc’s until I enabled denizen.trigger.clickable (I think that was it). Now, for some reason, area enter events won’t trigger for the player. Or at least one, specifically and I don’t know why.

I should I’m just asking what are the basic permissions I should give players? Server owner didn’t enable anything relayed to denizen because he never touched it so now I’m left to figure out what permissions I’m supposed to give players or not

nocturne epochBOT
#

(Revolver) LuckPerms necessary permissions for Denizen?

nocturne epochBOT
#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

twin dagger
#

!lang denizen permissions

restive boneBOT
# twin dagger !lang denizen permissions
Language: denizen permissions

The following is a list of all permission nodes Denizen uses within Bukkit.

denizen.clickable # use the 'denizenclickable' command, which is automatically executed when using !command clickable and for clickable chat triggers
denizen.basic # use the basics of the /denizen command
denizen.ex # use the /ex command
denizen.debug # use the /denizen debug command
denizen.submit # use the /denizen submit command

Additionally:
denizen.npc.health, denizen.npc.sneak,
denizen.npc.effect, denizen.npc.fish, denizen.npc.sleep, denizen.npc.stand,
denizen.npc.sit, denizen.npc.nameplate, denizen.npc.nickname, denizen.npc.trigger,
denizen.npc.assign, denizen.npc.constants, denizen.npc.pushable

However, we recommend just giving op to whoever needs to access De...

Group

Console Commands

twin dagger
#

i think that list is also missing one for the announce command, uh

#

!c announce

restive boneBOT
# twin dagger !c announce
Command: Announce
Group

server

Syntax

announce [<text>] (to_ops/to_console/to_flagged:<flag_name>/to_permission:<node>) (format:<name>)

Short Description

Announces a message for everyone online to read.

Description

Announce sends a raw message to players.
Simply using announce with text will send the message to all online players using the Spigot broadcast system.
Specifying the 'to_ops' argument will narrow down the players in which the message is sent to ops only.
Alternatively, using the 'to_permission' argument will send the message to only players that have the specified permission node.
Or, using the 'to_flagged' argument will send the message to only players that have the specified flag.
You can als...

twin dagger
#

Note that the default announce mode (that shows for all players) relies on the Spigot broadcast system, which requires the permission "bukkit.broadcast.user" to see broadcasts.

#

@torn lichen the bukkit.broadcast.user permission used in the announce command may be useful for !lang denizen permissions

#

aside from those specific permissions, the only permissions you'll need otherwise are what other plugins require, any permissions specified in command script containers, and what you specify scripts to check for in tags

old sentinel
#

Hmm, so should I enable denizen.basic? What are the basic denizen commands cuz I only want to allow the player to trigger/interact with events in the server. I don’t want them using commands of any diet

#

Sort

twin dagger
#

there are no events that require permissions

#

denizen.basic is for /denizen commands, as in /denizen debug, /denizen do_nothing, /denizen submit, etc

#

the only script commands that require permissions are clickable's denizen.clickable permission and announce's bukkit.broadcast.user permission

old sentinel
#

How bizarre, cuz I did the clickable trigger and that fixed some of the issues but now the players can’t trigger some area enter events for some reason. It’s weirdly selective

twin dagger
#

if there's something specific that isn't working we can look at that directly

#

players can’t trigger some area enter events
could be the area doesn't exist for whatever reason

old sentinel
#

The ambience area enter? Check
Step into the area in front of the loot chest to open it up and take the items? Check
Walking into an area, determine cancelled, and having the number pad inventory open? Not working

twin dagger
#

!haste

restive boneBOT
twin dagger
#

share?

old sentinel
#

Currently at work, trying to relay the information to my fellow devs who are available. I’ll post what I can when I get home. I’m just trying to gather enough information so I know what to do right away when I get home

#

I think the current issue isn’t denizen related, the guys are giving me the specifics, will relay more info once I know more

swift kettle
#

!imnothome

restive boneBOT
# swift kettle !imnothome
Info: imnothome

We sometimes see users opening support threads or replying to them while not able able to test things.

This is often revealed in messages like "I'm not home right now and wanted to ask", or "I can't access my server but I think I remember the details", ...

This often leads to one of two problems:
• The user asks questions they could have answered themself if they were at their server. This is a problem because it wastes the limited resource of our expert helper team on simple questions that would never have been asked if it were not for the fact that the user wasn't near their server.
• A helper enters the thread to actively assist but is unable to provide any help because the user is unable to actually act on any responses. Many threads start with requests for basic followup information such as server logs or other demonstrative data from the server, that of course they can only provide when they have access to that data.

In both cases, helper time is wasted and the user don't actually get to act on any responses faster than they would have been able to had they simply waited til they were able to access your server before asking for help.

swift kettle
#

it's generally considered best practices to wait to ask questions about things until you are in a position to provide information and test suggestions

torn lichen
twin dagger
old sentinel
#

Alright, so what I was referring to earlier was actually not a denizen permission issue. It was another permission that didn't let players push buttons in adventure world.

However, there is now a new issue. I have a mythic mob boss that spawns and players are unable to harm it. It says they don't have permission to harm it so I'm very very confused

pastel roost
old sentinel
#

Yeah, so, when a player tries hurting my boss, the message "Sorry, you can't hurt that here" pops up. I'm confused because the boss and the other custom mobs in the dungeon were all made with mythicmobs, they're all even in the same document. So i can't understand why the player can hurt the other mobs but not this boss

swift kettle
#

you need to do more thorough testing on development servers before pushing to live

old sentinel
#

I'll keep that in mind for the future. Now there's another issue on top of that one, perhaps y'all have a good idea

#

so, I'm trying to have npc's give players items from other plugins. The way I was shown before was:
- execute as_player "mi give ACCESSORY EMBER"
Unfortunately, this doesn't work for non op's/admins on the server. I'm not sure what permission I'd have to give the player for this to work or if I should change the as_player to as_op

#

or potentially as_server

normal flint
#

I think thats obvious enough at this point

#

Its similar to vanilla sudo

old sentinel
#

so I should change the as_player to as_op? because I don't want to change the permission so players can just start executing commands via denizen but I only want that command to be ran when they interact with the specific npc

normal flint
#

I think you're missing the point of execute

#

You are "executing" a specific command as "operator".

old sentinel
#

I understand that much. But the only thing part that's got me stuck is that I'm assuming it's a permissions problem cuz when the player interacts with the npc and it gets to that part of the script, it runs the execute command is supposed to give the player the item. But now I'm not sure what specific denizen permission I'm supposed to give where they can get the item but not just use it on a whim. I don't want them to start running around using /ex commands

normal flint
#

Dont assume

#

!tias

restive boneBOT
# normal flint !tias
Info: tias

Try it and see!

If somebody pulled this up for you, you're probably asking a question of the public channel that's easier and faster to figure out by just attempting your idea in-game and looking at the result of that attempt.

old sentinel
#

I just tried enabling denizen.ex but that didn't do anything. I don't see any other permissions that can work. All the other parts of the NPC work but I'm not sure what to enable specifically so a npc execute as_player command will work for a player.

normal flint
#

!haste

restive boneBOT
old sentinel
#

It works for admins of the server but not for players

pastel roost
#

pay more attention to your actual script. you're making them execute /mi give ACCESSORY EMBER

normal flint
#

Exactly what I was pointing out

pastel roost
#

you should do it as the server, and direct the give to the player

normal flint
#

You are literally missing the point of execute

pastel roost
#

if /mi give doesn't have a <player> input then meh

#
  • NEVER give players access to the /ex command. they can op themselves with that
old sentinel
#

I'm aware that's exactly what it's doing, but that was what I was told to write a while ago in a older post. It just worked at the time so I rolled with it.

pastel roost
#

"it works" fallacy

normal flint
#

Execute is like an action.
Example analogy:

Run as_horse distance:10meters -> horse finished the distance in 10 seconds

Run as_human distance:10meters -> human finished the distance in 5minutes

#

See the difference?

old sentinel
#

correction: with my lack of knowledge regarding "permissions" the command worked as instructed to me at the time without me understanding the difference and coming to the conclusion that it works universally

normal flint
#

You are running a command in the script "as" something that has access to something

#

So if a player has access to admin command, then they can run as admin

#

But if they dont

#

You can PROXY them admin access on that one command

#

Thats what as_type means

#

Its as simple as that

pastel roost
old sentinel
#

Alright, I believe that reality is more clear to me now. So, I should run it as a as_server like suggested by Bill and have it give it to the player. Now the only question I have in that regard is how do I make the server recognize the specific player? Would it automatically assign the command/give to the player because they are the one that triggered the npc/interact or do I have to type something else in?

normal flint
#

Whos interacting with the NPC?

#

!c give

restive boneBOT
# normal flint !c give
Command: Give
Group

item

Syntax

give [xp/<item>|...] (quantity:<#>) (unlimit_stack_size) (to:<inventory>) (slot:<slot>)

Short Description

Gives the player an item, xp, or money.

Description

Gives the linked player or inventory items, xp.

Optionally specify a slot to put the items into. If the slot is already filled, the next available slot will be used.
If the inventory is full, the items will be dropped on the ground at the inventory's location.
For player inventories, only the storage contents are valid - to equip armor or an offhand item, use !command equip.

Specifying "unlimit_stack_size" will allow an item to stack up to 64. This is useful for stacking items
with a ma...

normal flint
#

"When giving an item, you can specify any valid inventory as a target. If unspecified, the linked player's inventory will be used."

old sentinel
#

Alright, so it would be automatic because they are the ones triggering the command much like an event. The <player> is the one who triggers the event, it's contextual

#

I'm going to try it as_server real quick

pastel roost
#

i think as_op would save the hassle of linking the player bc it'd still be the player executing it, but with op perms

warped turtle
normal flint
#

only time you execute as_op is if the external command needs to be executed by a player

pastel roost
warped turtle
#

(Which the execute command meta mentions, always a good idea to check meta if you're unsure, especially when providing support)

#

Most plugins will probably have a /give <player> <item> style command, which is a better option

normal flint
#

true, I've only encountered very few (which I can no longer remember) commands that needs actual player. later on tho, plugin devs adds option for console version of em

jovial wedge
pastel roost
#

yea, i had a brainfart