Hey M0rica can you please make a datapack with same functions or post this plugin on websites like spigot or papermc as some minecraft server hosting websites like aternos do not allow custom plugins .

Is your feature request related to a problem? Please describe.

Yes, incase of a player having packet loss some packets may arrive out of order making the server have to wait for the packets which should have arrived, during the waiting the player's head position will not be updated and when the packets in the middle finally arrive to the server the server will update player's head position to the latest one in less than a tick causing the player's head to jerk which can affect the player's ability to draw spell patterns.

an oversimplified example:

0. Player tells the server that its head is looking at (0, 0).
1. Server receives player's head position and sets it to (0, 0).

2. The pattern recording code records position (0, 0)

3. Player tells the server that its head is looking at (0.5, 1).
4. The packet with player's position is lost.
5. The server does not get player's head position.

6. Player tells the server that its head is looking at (1, 0).
7. The server's computer gets player's position (1, 0).
8. The server's computer realises that it did not receive a packet which was in the middle so it does not pass the packet to the Minecraft server yet.

9. Player understands that the server did not get the packet.
10. Player resends the packet where its head position is (0.5, 1).

11. Server's computer gets the packet where players position is (0.5, 1)
12. Server's computer sends both packets in the order (0.5, 1), (1, 0) to the Minecraft server.

13. Server receives packet where player's head position is (0.5, 1)
14. the server sets player's position to (0.5, 1)
15. In less than a tick after that the server receives packet where player's head position is (1, 0)
16. the server sets player's position to (1, 0)

17. The pattern recording code records position (1, 0)

18. The player instead of getting a triangle [(0, 0), (0.5, 1), (1, 0)] gets a line [(0, 0), (1, 0)]
19. The player which was unable to cast its spell dies to a zombie which the its spell was supposed to kill.

Describe the solution you'd like

Instead of recording player's position on tick record it when the Minecraft server receives player look packet

Describe alternatives you've considered

Ignore this problem because it requires NMS to solve it.

In the code it generates an int from 0 to 9999 as the active spell id which would mean that there could only be 9999 at a time and if all of the 9999 spells were to be taken the server would just crush.

Even with let's say 9995 active spell ids taken the server might still crush or at least get performance of spell spawning severally dropped because of it trying to generate a random number which is not taken over and over again.

I would recommend changing from int id to UUID, or making the int id not random but instead increased by one every time a spell is spawned and when reaching the int limit just reset to 0. (Even tho reaching the int limit is very unlikely unless the server is running for years without restarting (if a spell were to be cast every second it would take 68 years to run out of ids or if at the rate of 1000 spells per second, it would still take 24 days))

Thank you for reading this short suggestion.

Hello! currently I'm running a 1.17.1 minecraft server, my players really like the server, but at the moment i have been looking through some magic plugins and haven't found ones that have caught my eyes, until i ran into this one, I found the video pretty amazing, and how the system works, and i would like for there to be a 1.17.1 version thank you.

This PR adds a spell casting system to let a player cast spells without needing to type in a command. How it works:

• Cast a spell:

  When a player is holding a stick with the custom name "Magic Wand" in the main hand while sneaking, the system records a point where the player is looking at. Now the player moves his head to draw a pattern in front of him. Once the player stopps sneaking, the system analyses the pattern and tries to map it to a known pattern which will cast a spell. A pattern consists of an infinte sequence of lines with each line being one of 8 types: up, down, left, right, up-left, up-right, down-left or down-right.

• Bind a spell to a custom pattern:

  To bind a spell to a custom pattern, the player needs to typ in the command /spell bind <SpellName>. Now the player just needs to draw the pattern he wants to bind the spell to and after that, the custom pattern will trigger the spell. It is possible to bind the same spell to multiple patterns, however binding a spell to a pattern bound to another spell will override which spell is bound to the pattern.

This PR adds commands for testing purposes/server operators to manipulate varoius variables.

Commands/subcommands added:

• /spell terminate <id>: terminates the spell with given ID
• /spell kill <id>: kills the spell with given ID (skips terminate event)
• /mage <player> <mana/manaMaximum/manaRegeneration> <set/get/add/remove> <amount>: change the according value by the given amount or get the current value
• /removemage <player>: remove the player executing this command or the given player (requires op) from being a mage
• /addmage <player>: add the player executing this command or the given player (requires op) as a mage In addition to that, /spell cast now displays a message in chat with the id of the spell cast to use with the new terminate and kill options.

Is your feature request related to a problem? Please describe. There are no commands that allow to test various aspects of the plugin, such as how much Mana a player can have. These variables are hard-coded right now.

Describe the solution you'd like Add commands that allow for manipulation of different aspects, such as a player's maximum Mana amount, add&remove Mana from/to a player, changing how much Mana a player regenerates per tick, disabling/enabling a player as a Mage, etc.