ScheduledCommands
ScheduledCommands allows you to execute scheduled commands after a long time period.
Have you ever wanted to have temporary donator ranks? You can use ScheduledCommands for many different things!
Example use:
- Use it together with CommandRank. CommandRank promotes the players and ScheduledCommands demotes them after a specific time.
- Use it to run automatic events and enjoy them instead of always having to be online and typing the event commands.
- Temp-(mute/ban/whitelist/etc.) somebody (Many plugins already have a tempban/tempmute command though)
- Etc.
Features
- Easy to use
- Permissions support
- ScheduledCommands is able to execute commands after a long time period - even after 20 weeks
- Player-check: Some commands are only executed when the named player is online
- API: Developers are able to easily hook into ScheduledCommands and to work with it
Commands
- /tcmd reload - Reloads the config
- /tcmd <time> <cmd> - Executes <cmd> in <time>
- /tcmd <time> <cmd>#<name of player> - Executes <cmd> in <time> as soon as the named player is online
Permissions
- ScheduledCommands.use - Allows to use the /tcmd command
NOTE: This plugin has not been updated since a long time but should still be working fine! Due to circumstances (For example final school year) I am not able to update my plugins anymore. However most of them should still be working fine and besides I have found Maintainers for a few of my projects, who keep these updated. Thanks for your understanding ;-)
Can someone please update this to 1.14? Would be really helpful, because it only executes a command after a restart or reload...
great plugin! how can you make
without having to put the name of player, so it will work for any player?
thanks
is this plugin support placeholder???
Doesn't work AT ALL on spigot 1.8.7. No command executes, sometimes it executes after a restart, but it's not even on time.
Tasks only execute if the plugin is reloaded, or the server is restarted.
Does it support UUIDs? 1.8 compatible?
One problem!If you server accidentally closed! Timed command could not save!How about add a function. (Automatic save and read at regular intervals)
I was wondering if you can make the plugin server timed. What i mean by that is, uses the servers timezone to get the time and being able to change the config so it works with that. If this plugin does use Timed command does it not also need to be able to be timed for every type of time ? and maybe when to start and stop but then again i Say This Is Point less on how the Player will probably use or buy ingame anytime so you just need a Command Timed.
@xdmen62
In the config, like niels1189 was saying, it shows this:
But if you want it to check every second, like I usually have it, use this:
@niels1189 scheduletime: 10
Set it to how many times you want it to check for commands to execute. 10 = 1x every 10 seconds. 1 = 1x every second
@xdmen62
I'm having the same problem
can you make so you can schedule at like 0:00:00 am?
Hello there
I have a problem when I do /bcast 1s bcast or test /tcmd 1s / bcast test, it does not perform the command in 1 second, the fact that much later If you could help me it would be nice :)
Thank you in advance! PS: Sorry for my english, I'm french
Im using spigot 1494, 1.7.9, and the commands don't seem to work, using command like:
/tcmd 1s /bcast test1
plugins/scheduledcommands/config.yml
Great plugin, but where does it store commands?
Hello,
I think the problem with duplicated commands is in some changes in Bukkit 1.7.x, because it worked correctly when we used older version (1.6.x). It's strange that all duplicated commands are always increased by 1 (I mean the key/time value in config.yml ). Because of that I decompiled your plugin and tried to find code which increased the value but I didn't find it... So then I made two changes:
1. removed using of long and changed them to Long
2. modified your method addCommandToConfig to check if the command already exists:
public void addCommandToConfig(Long time, String command)
{
String key = "waiting." + time.toString();
if (this.plugin.getConfig().getString(key) == null)
{
this.plugin.getConfig().set(key, command);
}
}
Combination of these changes works correctly and now we have no duplicities :) Please could you check it and modify your plugin? Maybe it's enough just to change long->Long, maybe there must be both of these changes, I don't know.
This plugin is great, works fine.
Just one problem, how do i delete the repeated commands?
One other thing, where does it store the commands?
Works with 1.7.9 great plugin no problems here
thank you so much for this plugin, been looking for something like this for ages