This repo provides a datapack for handling projectiles which raycast iteratively to mimic /tp motion with higher control and accuracy. For example, instead of teleporting a sword with "^ ^ ^5" which could pass through walls, the slowcast system can achieve the same look while checking every block along the path to ensure it hits all targets and stops when it hits a wall.
- Place the slowcast datapack in your world, or add the namespace to your datapack. If you choose to add the namespace to your pack, include "slowcast:zprivate/init" in your load functions and "slowcast:zprivate/main" in your tick functions.
- Go to the functions folder
- Go to the entity/list file. If you want to add a new entity (other than markers) to become a projectile copy of the lines and paste it below. Change the score check number to a new value which indicates that new projectile and add your entity, including the tags "slowcast" and "slowcast.new". If you need to you can make it run a function instead. NOTE: if this entity is not a marker, armor_stand, or item you will need to add it to the entity tag file.
- Go to the raycast/list file. If you want to edit the behavior during motion you can add a new line with a new score check value indicating how the projectile motion behaves. Copy the "loop" file and name it what you want. Make sure to make the new line in the list file say that name.
- Inside your loop file, #temp slowcast.itt is the value used to count recursions and must be reduced by 1 per function call. When the score is 0 you MUST include a line teleporting "@s" (which refers to the projectile entity) to ~ ~ ~. Anything tagged slowcast.this refers to the projectile, and slowcast.caster refers to the source entity. Feel free to do anything with those, the example loop file uses a hitbox to kill other entities. Finally at the bottom you must include a line that does the recursion. You can also call the "slowcast:stop" function here to stop the raycast under additional criteria such as hitting a wall. At any time the function can be called to stop a projectile.
- Go to the end/list file. Again, copy a line, change a value, and make a new function for it to call. The functions here run commands when the projectile stops. @s will refer to the source entity and it is played at the location the projectile stops at.
Now that you setup how you want the projectile to behave and look like, you can use it very simply.
- Specify the fake players on the slowcast score .type slowcast -> controls what loop to use and what end to use .entity slowcast -> controls which projectile entity to use .recursions slowcast -> specifies how many loops play per tick (like speed) .iterations slowcast -> specified how many recursions will play until it ends (like distance)
- Once these are set, simply call the slowcast:start function as the entity you wish to fire the projectile with and oriented however you want. The namespace "demo" shows an example of using it for throwing a sword.
Extra Help! Some important things to note is that for efficiency purposes, any entity besides players that you wish to make able to use the system must be specified in the entity tag under slowcast/tags/entity_types/casters and any entity for projectiles other than the predefined ones must be added to the entities tag in the same location.
 Cloud Wolf 🔨 |