hoodierocks/cocktail-spigot

A spigot plugin designed to expand the capabilities of datapacks

Cocktail (spigot) 🍸

Cocktail is a Spigot plugin designed to expand the capabilities of Minecraft Datapacks via useful and powerful commands and utilities.

Requires CommandAPI

Features

Datapack Updater

Update your datapacks in a jiffy! Add your link to the config, and it'll download your datapacks updates on reload or start up

datapack-name-here:
  # Make sure the link either redirects to a download page or is a direct link to a zip of the pack
  url: "https://your-datapack.link/here.zip"

Advanced Commands

Cocktail adds many commands, these commands are accessible to datapacks unlike traditional Spigot commands.

• Use /velocity for velocity manipulation,
• Use /damage to damage exactly the specified damage to an entity,

And many more commands! (see the wiki)

More to come!

Disclaimers

• While this plugin can be used on Paper or its forks (Purpur, Pufferfish, Petal, etc.), Paper is known for causing lots of issues with datapacks (more than Spigot)

cocktail-spigot's Issues

Velocity does not run in functions

/pdata is really buggy, limited and in some cases broken

Velocity's relative positioning is not correct

Suggestion/Feature request: /watch command

Is your feature request related to a problem? Please describe.
Checking for block updates is, for the most part, not realistically possible within a datapack. The best you can get is either scanning blocks for updates, having a tick loop on markers representing blocks, or having a scoreboard set up for checking when a certain block type is placed, and raytracing from the players position. All of them can get really laggy really fast in certain scenarios, and aren't all that fun to set up.

Describe the solution you'd like
The /watch command watches for block updates. An example of a proposed syntax for the /watch command is as follows:

# watches for block updates at a certain position
watch position <x> <y> <z> <function-name> [start|stop]
# watches for block updates anywhere of a specific block type
watch block <block-id> <function-name> [start|stop]
# watches for block updates resulting from direct player interaction (like chest contents or placing/breaking)
watch player <selector> <function-name> [start|stop]

This would allow you to set up events for when a block is modified, and will run the specified function name at the position of the modified block (it would also run it as the entity/player that interacted with the block.