#Need help with success/deny commands per requirements

1 messages · Page 1 of 1 (latest)

lean wing
#

Hi there. i'm struggling with fully understanding how to properly use success/deny commands on requirements. I'm following the wiki, but everything that I try to do on a requirement basis, fails. I can't help but feel like that there's an issue with how the wiki is written, since at this point I've started to just shuffle things around in the hopes that I'll eventually hit something that works. I'd love if someone could enlighten me.

Here's 3 examples of what I've done, that I've made based on what the wiki is telling me: https://paste.helpch.at/jagoxekeye.yaml

I want to add that at no point has success_commands ever worked for me

#

In short, what I'm trying to do:
If player has item = take item
If player has item and placeholder is:
= true: say yes
= false: say no

#

My question is really just how to use success commands/click commands on a single requirement basis
(and I'd prefer to compact it instead of having 3 requirements sections per 17 buttons in this GUI)

lean wing
#

I understand that success commands might not be what I'm looking for, but I can't seem to get click commands to rely on single requirements from a list either, while allowing another requirement on the same list to have its own independent outcome

lean wing
#

Okay there's definitely 1 issue with the wiki: in your requirements_menu.yml file listed under "plugin files", your right_click_requiremens example has a "type: has item" example with "deny_commands" written in the requirement ID indendentation, which leads to an error as a "type" is expected after that declaration

#

[DeluxeMenus]: No type set for requirement: deny_commands for path: items.Ashfall Dragon Wings.left_click_requirement.requirements.deny_commands

#

(this is not the case in the file that actually comes with the plugin though)

lean wing
#

sighs. nvm. I had the basic structure working at some point, but I somehow worked in a syntax error in the process of testing success/deny.[message] in click_commands fucked the whole thing over