[Feature Request] A command to toggle the silent join/quit messages when you can the silent join/quit perms

[AZFire1]

Description of feature/improvement request:

---

Detailed explanation of what it should do, when and in what situation:

This would be a new command added just to be able to toggle if your join is silent or not when you have the permissions, cmi.messages.disablelogin, cmi.messages.disablequit. This could have a new permission of it's own dedicated to toggling your join. These don't necessarily have to be connected though. This is just to toggle it, as currently I have to negate the perm for players with the "*" perm or op as their join is automatically silenced.

Basic explanation as to why this feature is needed and/or useful to have:

Just to quickly sumarize what I just said, I think there should be a command to toggle your join/leave message manually ingame rather than having to negate the previously mentioned permissions for your join message to show if you have all permissions.

Now, this may already exist and I just couldn't find it. Let me know if I missed it, thanks :)

[CloudeLecaw]

You can create a custom alias that gives and negate the the permission asConsole! (use the check for permission for this) for you. Dont forget to add a needed permission to execute this custom alais.

Example with PermissionEx

CustomAlias:
  joinleave on:
    Cmds:
    - perm:cmi.command.customalias.joinleaveswap#! check:%cmi_user_name%==$2! asConsole! pex user [playerName] add cmi.messages.disablequit
    - check:%cmi_user_name%==$2! msg! [playerName] Your Join and Leaving messages will now be shown in chat.
    - check:%cmi_user_name%=!$2! asConsole! pex user $2 add cmi.messages.disablequit
    - check:%cmi_user_name%=!$2! msg! [playerName] The Join and Leaving messages of $2 will now be shown in chat.
  joinleave off:
    Cmds:
    - perm:cmi.command.customalias.joinleaveswap#! check:%cmi_user_name%==$2! asConsole! pex user [playerName] remove cmi.messages.disablequit
    - check:%cmi_user_name%==$2! msg! [playerName] Your Join and Leaving messages will now be hidden from chat.
    - check:%cmi_user_name%=!$2! asConsole! pex user $2 remove cmi.messages.disablequit
    - check:%cmi_user_name%=!$2! msg! [playerName] The Join and Leaving messages of $2 will now be hidden from chat.

after the next server restart they should be shown in tabcomplet
Command useage: /joinleave [on|off] (playerName)

It could be that $2 needs to be replaceced with $1 .. im not 100% if the on/off is coulting as var 1 in this case or not.

[AZFire1]

I use LuckPerms. I tried this, and I also tried it with $1 replacing the $2 but it doesn't seem to be doing anything when I check ingame and console for if it effected anything. This is actually the first time I've seen that CMI can do that much. I actually didn't know it could do this, that's awesome.

Due to the fact that you can do so much with custom aliases, I was wondering if there's a possible way I could do the same or similar things in the eventCommands for the death event. By this I mean, would there be a way I could make a death message that is not just one base death message but one that I could add my own custom reasons per death cause? I was just curious if that can be done.

[CloudeLecaw]

yes you can

[AZFire1]

Awesome. Would you possibly be able to provide an example of one custom death reason so I could see how to do it?

Also, could you please send me some documentation on how this works, so I could figure out how to fix the "joinleave [on/off]" command as, as I previously said I couldn't get it to work.

[CloudeLecaw]

Well if you want i can post you our little eventcommamd.yml we use just the join anf first join events but may it help you to see what is possible :)

Specialized Command Usage
Works with: Ranks, Scheduler, Portals, EventCommands, Interactive Commands, Kits and custom alias.
https://www.zrips.net/cmi/commands/specialized/

firstJoinServer:
  Enabled: true
  Commands:
  - atr reset [playerName]
joinServer:
  Enabled: true
  Commands:
  - msg! [playerName]         Willkommen auf dem Server [playerName]
  - msg! [playerName] &6&l   **********************************************
  - msg! [playerName] &4                  &8۩&8۩&8۩&4Halloween-Event-2020&8۩&8۩&8۩
  - msg! [playerName] &7              Vom 30.10-01.11.2020 feiern wir auf
  - msg! [playerName] &7                        Lululand Halloween
  - msg! [playerName] &4      &8۩&8۩&8۩&fNähere Infos in den Lulu-Wiki News&8۩&8۩&8۩
  - msg! [playerName] &6&l   **********************************************
  - cmi ctext news [playerName]
  - check:%cmi_user_dailyvotecount%==0! msg! [playerName] Du hast in den letzten 24
    Stunden noch nicht einmal für Lululand gevotet. &e☹
  - check:%cmi_user_dailyvotecount%==0! msg! [playerName] &c❤&4♥&fBitte vote für den
    Server&c❤&4♥
  - check:%cmi_user_dailyvotecount%!=0! msg! [playerName] &c❤&4♥&f Du hast in den
    letzten 24 Stunden %cmi_user_dailyvotecount% mal für Lululand gevotet.&c❤&4♥
  - check:%cmi_user_dailyvotecount%==0! cmi ctext voteslogin [playerName]
  - check:%cmi_user_dailyvotecount%!=0! cmi ctext voteslogin2 [playerName]
  - msg! [playerName]
  - check:%cmi_user_name%==Blueeyestar! cmi flyspeed Blueeyestar 5 -s
  - check:%cmi_user_name%!=Blueeyestar! cmi flyspeed [playerName] 1 -s
  - check:%cmi_user_name%==Cloude_Lecaw! cmi broadcast !&6&l⚡ &e&l⚡ &6&l⚡ &e&l⚡ &b&lCloude_Lecaw
    &e&list wieder da! &6&l⚡ &e&l⚡ &6&l⚡ &e&l⚡
  - check:%cmi_user_name%==Opa_Gerd! cmi broadcast !&4&l❤&c&l♥ &4&l❤&c&l♥ &4&l❤&c&l♥
    &e&lHier ist euer Lieblings-&4&lOpa&e&l! &4&l❤&c&l♥ &4&l❤&c&l♥ &4&l❤&c&l♥
  - check:%cmi_user_name%==Trevodor! cmi broadcast !&d&l♫ &6&4♫ &6&l♫ &e&l♫ &e&lTri,
    Tra, Trullala,... Der &9&lTrevodor &e&list wieder da. &a&l♫ &b&l♫ &1&l♫ &5&l♫
  - check:%cmi_user_name%==Heldo44! cmi broadcast !&e&lIst es ein Düsenjäger?✈,,,
    Ist es ein Blitz?⚡....NEIN es ist &d&lHeldo44&e&l!ツ
  - msg! [playerName]
quitServer:
  Enabled: true
  Commands:
  - cmi skin off [playerName] -s
  - cmi nick off [playerName] -s

If you dont know how to desgin it we may could help you. You wrote you wanne work with the death Event. So what should be done there?
You said u want a custom death reason, sounds like custom death meassages. This is not possible like some plugins do it with custom death meassages for different death reason.
Adding custom death meassages was request allready by someone, may it come one day...
What you can do on death is create a msg with a random number in it. After it you can define different commands if this number was 1 or 2 or 3 or 4 or...
Example:

    - msg! [playerName] Your Lucky Rewardnumber is the &e&l%cmi_random_1_5% of 5.
    - check:%cmi_lastrandom_[playerName]%==1! msg! [playerName] Your Number is 1
    - check:%cmi_lastrandom_[playerName]%==2! msg! [playerName] Your Number is 2
    - check:%cmi_lastrandom_[playerName]%==3! msg! [playerName] Your Number is 3
    - check:%cmi_lastrandom_[playerName]%==4! msg! [playerName] Your Number is 4
    - check:%cmi_lastrandom_[playerName]%==5! msg! [playerName] Your Number is 5

[CloudeLecaw]

About the join on off, it first asks if you have the defined permission for it else it breaks up.
If you have the permission it asked for yoir command command Variable. If it was your name then it asked if you have the defined permission cmi.meassage.quitdisabled
If you dont have it then it gives you the permission
If you allready have it then it removes the permission. In both casesnyou get informed. If the command Variable was not your name then it doesnthe same procedure for the defined playername.
If your grouo has the '*' permission its Import that this group has negated the cmi.meassage.quitdisable permission by default to work (else you would allways have it) the command give or removes a player permission and if you give a player permission then this overwrite the Negation you have Set in the group

[AZFire1]

Okay, if I wanted to setup a separate death message for when a player gets killed by a player (which is below the base death message called "PlayerKillPlayer") and I set one up. I'm assuming if I set it up under that message, it will trigger both death messages, from the base death message and the playerkillplayer death message. How would I go about making one for this? Or, would it not trigger the base death message at all and I could just do it through it?

[CloudeLecaw]

No, like you saw allready you have the normal death event and the playerkill event on that list.
The playerkillplayer will executed if u wanne do something if someone killed someone. This can beba meassge too. The kill isbthe playerDisplayName the killednone the source.
If you your using the pvp feature of cmi then you could check onndeath if off the killed one is still actived and execute a msg, else annother meassge.
Problem here would be if hebis in pvp with someone but does not die from a player.. (a zombie from behind?) Then this would trigger the pvpdead meassage
The playerkillplayer Event is good for pvp servers to reward the killer or send a meassage when he killed someone, or good for servers wherebyou wantnto strafe someone for killing annother player

[AZFire1]

I've tried messing with the joinleave command though for whatever reason I haven't been able to get it to work. Also, recently I was wondering if I could make a "/withdraw [amount/all]" with the plugin "Vouchers". I was wondering if CMI could check the users balance, run a command to give that player a voucher, and then take away the money from that player. Is that possible to do to make a sort of "/withdraw" command?

[CloudeLecaw]

you can check the balance with hasmoney and break it up the secene if this is not true
then you can send a moneycost for the execute. of the command (like pay the other)
these can be done silently
After it i suggest adding a msg! to both.

but maybe i went out of the idea..
would be better if you can discripe it step by step (each step with a line) startneach step with -
so we can see betternwhat should happen step by step. But at the moment i would say it possible :e

what i did for example (i replaced a whole server sign shop item with cmi - yes with buying and selling, money checks + feedback msgs

[AZFire1]

"/withdraw (amount)" command:
Step 1: Check if player has money and if withdrawn money is above 0, if not send an error message to player.
Step 2 (Only if has money): Take that exact money away.
Step 3: Execute command to give the voucher which would be "voucher give withdrawmoney (previous amount of money)"
Step 4: Send finishing message.

And, the "/withdraw all" command would just do everything the above did just give you all your money.

[CloudeLecaw]

well just a little idea...

cheque (playerName) [amount]
Convert money into check. Real physical item. By default paper is needed to create one. Right clicking item will deduct money to players accounts

[AZFire1]

I suppose. Added onto this I was wanting to maybe make something that would allow you to withdraw EXP.

[AZFire1]

Which is why I wanted to use CMI with Vouchers to make a money withdraw and an exp.
But that cheque idea could definitely be an option

[CloudeLecaw]

sobyou want to exchange exp for cheque?
thus is possible with a little custom alais script.

• if has xp# give player money amount of - arg1 (its up to you if you give 1Doll, as xpcost
  if he does not have it the customalais breaks up because of #
• step 2 command two would be giving him a cheque about arg1
• step 3 command tree is taking the xp from him

if player usually has no permission to create ancheque you can use bperm:cmi.command.cheque! so players bypass the permission in that case for the customalais.

well its up to you if you take singlen exp or whole level here for one Dollar.

checjs your using here: hasexp:VALUE#! and may if used bperm:cmi.command.cheque!

you could try using expcost:$1! and therefore leaving the takenaway part.. but i dont know if this works.
same for moneycost:$1!
if both work you could design it all a bit. mor simple with just one check command. well test it out ;)
niw u can play arround and add more checks for $1 and handle with break up or with meassage..
usefull checka may if $1 == 0, or $1 =! 0