open_command: prestige_0
size: 45
update_interval: 1
items:
#############################################################
'novice-1p0':
material: DIAMOND
slot: 10
display_name: "&aNovice I"
lore:
- "&7Cliquez pour acheter ce grade"
priority: 1
view_requirement:
requirements:
group:
type: not in group
group: novice-1p0
left_click_commands:
- "[console] eco take %player_name% 100"
- "[console] lp user %player_name% parent add novice-1p0"
- "[refresh]"
- "[sound] ENTITY_EXPERIENCE_ORB_PICKUP"
'novice-1p0_claimed':
material: DIAMOND
slot: 10
display_name: "&c&lNovice I &8&l▪ &7&lDéjà acheté"
lore:
- "&7Vous avez déjà acheté ce grade."
view_requirement:
requirements:
group:
type: in group
group: novice-1p0```
#Deluxe menu I'm having priority issues
1 messages · Page 1 of 1 (latest)
when I open the minuet that I use the object it makes me pay it gives me the role unfortunately I can click several times and I would like that we could buy it only once and then it goes directly to the 'novice-1p0_claimed'
for the purchase option and description to change
ah
also, not that it really matters
but conventionally: I would have priority 1 be in group and priority 2 have no view requirements
since it would only show if the view requirements for the priority 1 item aren't met
and hide_if_not_met is also not a thing
do you use luckperms @distant comet ?
yes
do you want to check if the user is IN the group, or inherits the group? (Can higher ranks access lower rank items?)
oh probably inherits by what I see
the goal is that when we buy it we get the role and then they tell us that we already have the role and that we can't buy it again
this is what I would try
https://paste.helpch.at/ofupenixen.yaml
also fyi, you can use click_commands instead of left_click_commands for ALL click types
incredible it's been 6 hours that I've been banging my teeth on it I wanted to fuck myself up I sincerely thank you @trail shoal
no problem!
Information
The all in one GUI menu plugin!
• Spigot
• Wiki
• Dev builds
• Placeholders
Requested by cj89898
·
these links might assist in the future
open_command: prestige_0
size: 45
update_interval: 1
items:
#############################################################
'page_previous':
material: PAPER
model_data: 110007
slot: 0
display_name: '&f&lPrécédent page'
left_click_commands:
- "[openguimenu] prestige_0"
#############################################################
'page_next':
material: PAPER
model_data: 110007
slot: 43
display_name: '&f&lProchaine page'
left_click_commands:
- "[openguimenu] prestige_1"
#############################################################
'back':
material: PAPER
model_data: 110007
slots:
- 37
- 38
- 39
update: true
display_name: '&c&lRetour'
left_click_commands:
- "[openguimenu] main_menu"
#############################################################
'novice-1p0':
material: DIAMOND
slot: 10
display_name: "&aNovice I"
lore:
- '&e➥ Clic gauche pour exécuter'
priority: 2
left_click_commands:
- "[console] eco take %player_name% 100"
- "[console] lp user %player_name% parent add novice-1p0"
- "[refresh]"
- "[sound] ENTITY_EXPERIENCE_ORB_PICKUP"
'novice-1p0_claimed':
material: DIAMOND
slot: 10
display_name: "&c&lNovice I &8&l▪ &7&lDéjà acheté"
lore:
- "&7Vous avez déjà acheté ce grade."
view_requirement:
requirements:
group:
type: string equals
input: '%luckperms_inherits_group_novice-1p0%'
output: 'yes'
priority: 1
#############################################################
'novice-2p0':
material: DIAMOND
slot: 11
display_name: "&aNovice II"
lore:
- '&e➥ Clic gauche pour exécuter'
priority: 2
left_click_commands:
- "[console] eco take %player_name% 100"
- "[console] lp user %player_name% parent add novice-2p0"
- "[refresh]"
- "[sound] ENTITY_EXPERIENCE_ORB_PICKUP"
'novice-2p0_claimed':
material: DIAMOND
slot: 11
display_name: "&c&lNovice II &8&l▪ &7&lDéjà acheté"
lore:
- "&7Vous avez déjà acheté ce grade."
view_requirement:
requirements:
group:
type: string equals
input: '%luckperms_inherits_group_novice-2p0%'
output: 'yes'
priority: 1
#############################################################
Okay I have a little question let's admit that if I want to make sure that you have to buy the lower role to buy the new one can I? example: points I want to buy grade 2 but I don't have grade 1 I would like it to be blocked is it possible that it even adds that you have to buy the lower grade ?
so for the priority: 2 item, add a view requirement that is identical to the one for novice-1p0_claimed
you can copy and paste
and then, if you want, you can add a 3rd item to slot 11 with priority: 3 that shows a "locked" item
open_command: prestige_0
size: 45
update_interval: 1
items:
#############################################################
'page_previous':
material: PAPER
model_data: 110007
slot: 0
display_name: '&f&lPrécédent page'
left_click_commands:
- "[openguimenu] prestige_0"
#############################################################
'page_next':
material: PAPER
model_data: 110007
slot: 43
display_name: '&f&lProchaine page'
left_click_commands:
- "[openguimenu] prestige_1"
#############################################################
'back':
material: PAPER
model_data: 110007
slots:
- 37
- 38
- 39
update: true
display_name: '&c&lRetour'
left_click_commands:
- "[openguimenu] main_menu"
#############################################################
'novice-1p0_locked':
material: DIAMOND
slot: 10
display_name: '&c&lNovice I &8&l▪ &7&lBloqué!'
lore:
- '&7Vous devez acheter le grade précédent'
- '&7avant de pouvoir acheter ce grade.'
priority: 3
view_requirement:
requirements:
group:
type: string equals
input: '%luckperms_inherits_group_default%'
output: 'yes'
'novice-1p0':
material: DIAMOND
slot: 10
display_name: "&aNovice I"
lore:
- '&e➥ Clic gauche pour exécuter'
priority: 2
left_click_commands:
- "[console] eco take %player_name% 100"
- "[console] lp user %player_name% parent add novice-1p0"
- "[refresh]"
- "[sound] ENTITY_EXPERIENCE_ORB_PICKUP"
'novice-1p0_claimed':
material: DIAMOND
slot: 10
display_name: "&c&lNovice I &8&l▪ &7&lDéjà acheté"
lore:
- "&7Vous avez déjà acheté ce grade."
priority: 1
view_requirement:
requirements:
group:
type: string equals
input: '%luckperms_inherits_group_novice-1p0%'
output: 'yes'
#############################################################
'novice-2p0_locked':
material: DIAMOND
slot: 10
display_name: '&c&lNovice II &8&l▪ &7&lBloqué!'
lore:
- '&7Vous devez acheter le grade précédent'
- '&7avant de pouvoir acheter ce grade.'
priority: 3
view_requirement:
requirements:
group:
type: string equals
input: '%luckperms_inherits_group_novice-1p0%'
output: 'yes'
'novice-2p0':
material: DIAMOND
slot: 11
display_name: "&aNovice II"
lore:
- '&e➥ Clic gauche pour exécuter'
priority: 2
left_click_commands:
- "[console] eco take %player_name% 100"
- "[console] lp user %player_name% parent add novice-2p0"
- "[refresh]"
- "[sound] ENTITY_EXPERIENCE_ORB_PICKUP"
'novice-2p0_claimed':
material: DIAMOND
slot: 11
display_name: "&c&lNovice II &8&l▪ &7&lDéjà acheté"
lore:
- "&7Vous avez déjà acheté ce grade."
priority: 1
view_requirement:
requirements:
group:
type: string equals
input: '%luckperms_inherits_group_novice-2p0%'
output: 'yes'
#############################################################```
Could it work like this?
you added it to the priority: 3 item, also that item is in the wrong slot (10, should be 11)
Oh I see you also added a 3rd item for Novice I
but that shouldn't be needed, because it will be available for all users, right?
(everybody starts with default rank)
ah you succeeded again but you are truly a genius

no
All users aren't default rank? 
it's a subcategory but it works in any case it's perfect
to sort the roles anyway it's my mic mac
ahh there's an issue
move the view requirement from 'novice-1p0_locked' to 'novice-1p0'
because, as it is now, 'novice-1p0_locked' will never show because there is no view requirement on 'novice-1p0, so that will ALWAYS show before 'novice-1p0_locked'
if that makes sense
I did that change for you, also switched left_click_commands to click_commands so users can right-click it as well (If you want)
~~https://paste.helpch.at/ogatuxijos.yaml~~
wait
i made an error wtf
ok here lol https://paste.helpch.at/jonafodoho.yaml
thank you for your help and I learn a lot
of course! 😊
❤️
Hello, could you perhaps still help me today @trail shoal ? The goal is to create a daily reward I will put the rewards myself after that I know how to do it but I would like there to be a system immediately example : to buy day 1 I just have to have the default role and I can take it at any time there is no problem once I have taken it and it has given me the days 1 role I cannot plus recover the reward from days1 to the second I obtain the days1 role I would like there to be a 24 hour delay before the player takes day2 so on but if the player does not collect the next role within 48 hours I want it to start from the beginning message I will I just need your help to make a little pattern because I'm having difficulty making it work
menu_title: '&f七七七七七七七七╯'
open_command: daily_rewards2
size: 54
update_interval: 1
items:
#############################################################
'jours1':
material: PAPER
model_data: 3301
slot: 12
display_name: 'Jours 1'
lore:
- '&7Cliquez pour récupérer votre récompense du Jours 1.'
click_commands:
- '[console] lp user %player_name% parent addtemp jours1 24h'
view_requirement:
requirements:
has_group:
type: not
groups:
- jours1
update: true
'jours1_obtained':
material: BARRIER
slot: 12
display_name: '&cJours 1 déjà obtenu'
lore:
- '&7Vous avez déjà récupéré votre récompense du Jours 1.'
- '&7Revenez demain pour récupérer votre récompense du Jours 2.'
- '&7Temps restant: &a%luckperms_expiry_time_jours1%'
view_requirement:
requirements:
has_group:
type: or
groups:
- jours1
update: true
#############################################################
'jours2':
material: PAPER
model_data: 3301
slot: 14
display_name: 'Jours 2'
lore:
- '&7Cliquez pour récupérer votre récompense du Jours 2.'
click_commands:
- '[console] lp user %player_name% parent addtemp jours2 24h'
view_requirement:
requirements:
has_group:
type: and
groups:
- jours1
elapsed:
time: 24h
after: addtemp
action: true
update: true
'jours2_locked':
material: BARRIER
slot: 14
display_name: '&cJours 2 verrouillé'
lore:
- '&7Vous devez attendre 24 heures après avoir récupéré Jours 1.'
- '&7Temps restant: &a%luckperms_expiry_time_jours1%'
view_requirement:
requirements:
has_group:
type: and
groups:
- jours1
elapsed:
time: 24h
after: addtemp
action: false
update: true
#############################################################
'back':
material: PAPER
model_data: 110007
slots:
- 46
- 47
- 48
update: true
display_name: '&c&lRetour'
click_commands:
- '[player] dr'
#############################################################
I wrote this for the moment but obviously it doesn't work 😅
basically you want this
-you can get day1 with default but you'd require day1 to get day2 that too with a 24 hour delay (just like a streak system)
-if a player doesnt click on day2 item under 48 hours, they will lose the streak and will be given default back
am i correct 🤔
yes
would you mind if i create the menu in english?
well this might require intense configuration, though ill try my best
could you share your luckperms editor through DMs?
cant find a way to clear the groups if they haven't claimed
if we use group expiry time, then all the groups wont be cleared at the same time
you have to use the tracks at the same time but I don't know how to do it
can you test something
yes
create a track with 2 groups, give that track to a player and then use lp commands to remove the track and tell if it does remove all the groups at the same time
kind of yes but its like promotion
you upgrade the position of the player group using commands
even though if this worked, how will we tell the menu to run the command if they havent claimed daily for 48 hours
in fact the question would be can we make a role whatever happens after a certain time they are removed from the person thanks to that it would be possible
is there a function to put an expiration time but not on the player on the group and which activates the moment it is on someone for the person ?
like i said above, even if theres an expiration time, how we will tell it to start from a specific instant?
well you know what to drop I don't think it's possible thank you anyway for your time
it's possible, but very very complicated and not something I could really assist with due to the time required
would be better to have a custom plugin tbh
@carmine saddle
yeah?
.
nope
yes