Bukkit

In reply to Digital_Beast:

 You can store anything per player with /mycmd-playerdata. When you launch

$Script$%Variable%$unique_players_joined+1

add this other line :

  - '$Script$%PlayerData%unique_player_id=$unique_players_joined'

Then you can access to it as a placeholder with : "$PlayerData%unique_player_id%"   or   "$PlayerDataFor%PlayerName%unique_player_id%", there is also a placeholderapi support for playerdata,

%mycommand_playerdatafor_<playername>_<variable_name>%

In reply to Forge_User_80075269:

 I've looked into, but the getBedLocation seems half broken, i need more experimentation, i will find a way.

In reply to Forge_User_80075269:

I was using the wrong method. Anyway, here you go, if you want try it :

Link Removed: https://www.mediafire.com/file/a8ln7oe7fj5jcfh/MyCommand_v5.5.1dev_may27.zip/file

bedlocation_script:
 command: /checkbed
 type: RUN_COMMAND
 runcmd:
 - $Script$%if%$getbedlocation==not found
 - $text$&cCan't find the bed location
 - $Script$%else%
 - $text$&aTeleporting to your bed
 - "%PlayerOptions%teleport: $getbedlocation"

In reply to Forge_User_27476696:

 The command input is the same as the command output, so it creates a loop. I don't know, if the plugin have some aliases built in, you can use them, otherwise i guess, you can add them manually in the Quantumshop plugin.yml file inside the Quantumshop.jar archive. If you want to do that, open plugin.yml and add under the command shop the alias you want. Anyway, anytime the author update the plugin you need to do that again. Try to ask the dev of the plugin if he can add that alias for you.

 commands:
   shop:
     aliases: [new_command]

In reply to pretti_:

 The core of the plugin and most of his functions works on all the versions i've checked as "working". There is a warning in the plugin start who say exactly this. The best i can do is block the unsupported features with a message, so it doesn't give you an error. Anyway, from what i can remember, the API for the Title in 1.8.8 were half broken, and the best it allowed you to do was the same you can do with /title.

In reply to tubbyflumpkins:

 Creating something like this, yes :

'check_perms':
  command: /check_perms
  type: RUN_COMMAND
  runcmd:
  - '$Script$%if%HasPermission==permission.perm1'
  - /dosomething here
  - '$Script$%elseif%HasPermission==permission.perm2'
  - /dosomething here
  - '$Script$%else%'
  - '$text$Error Message'

In reply to jef_is_god:

 I see, i've added something that's allow you to do that on a forgotten feature "%TempVariable%"

Try in the 5.5.0 version, example of use :

  runcmd:
  - "%TempVariable%test1=$iteminhand"
  - "%TempVariable%test1.tolowercase"
  - "$text$&aTemp Variable -&3 test1"

Anyway, there are already some ways to manipulate the iteminhand like :

- "%PlayerOptions%setItemInHandDisplayedName: $arg1"
- "%PlayerOptions%setItemInHandLore: $arg2"

or

setItemInHand: MATERIAL_NAME:AMOUNT:ITEM_META: Enchantments;Level : Displayed Name : Lores;line2;line3...

In reply to jef_is_god:

Cooldown's check are made before the "runcmd" part, so, that's what happen. if you use built in cost features, those checks are made before the cooldown. Of course in your case you can't do that, but you can make a workaround to do what you want.

Create the first command where you check the exp :

ExpThingy:
 command: /exptester
 type: RUN_COMMAND
 runcmd:
 - $Script$%if%$level>=5 
 - /exptester_execute
 - /exp give $player -5l #Takes 5 levels from player
 - $Script$%else% 
 - $text$You don't have enough Experience levels!
 cooldown: 10
 permission-required: false

 Then create a second one with the cooldown on it and lock it under the "execute_mode: FROM_ANOTHER_COMMAND"

'ExpThingy_ex':
  command: /exptester_execute
  execute_mode: FROM_ANOTHER_COMMAND
  type: RUN_COMMAND
  register: true
  runcmd:
  - "/dosomething"


in this way, the second command works only if called from another mycmd command. 

The problem is, it's not perfect anyway, because the cooldown can be applied only on one of the 2 command, and how you can understand, if applied to the first one, if the execution fail, the player need to wait the cooldown anyway, if applied to the second one, the exp get withdraw but if there is the cooldown, the money got wasted.


Anyway, i guess i have to implement something allow you to cancel cooldowns in someway. I'll see if it's possible.

In reply to jef_is_god:

 As i said, i've implemented a sub-command that's allow you to manage active player cooldown's. If you want to try it, i've uploaded an updated 5.5.0 version with that in it.

Link Removed: https://www.mediafire.com/file/b72j57pfpcgg5z5/MyCommand_v5.5.0_alpha_may_3_2019.zip/file

this site don't really love mediafire, it put's file removed before it lol.

Basically that's how you have to use it :

ExpThingy:
 command: /exptester
 type: RUN_CONSOLE
 runcmd:
 - $Script$%if%$level>=5 
 - /do_whatever
 - /exp give $player -5l #Takes 5 levels from player
 - $Script$%else% 
 - $text$You don't have enough Experience levels!
 - /mycmd editcooldown $player ExpThingy 1
 cooldown: 1000
 permission-required: false