What about wands with a tiering system, each tier has new spells but is more exensive than the last
Imagine you could look at a mob and type a spell in all caps in chat and it would do it
EDIT: you cant do chat triggers in datapacks i dont think though Maybe shift left click and shift right click to cycle spells and left click to shoot it with a cooldown

make custom utility enchants for underutilized items like a ¨discord¨ enchant for the rod that if the bobber collides with the ground it will teleport you like an enderpearl, or an enchant for the carrot/fungus on a stick that makes the ride mob move faster when equipped

How about custom spell packs

You could add in an amulet that makes it so you can go in a semi-ghost form and haunt someone.
You can sort of fly, but only in short bursts.
You can also teleport to a random player one time per amulate.
One use, lasts for a few minutes, and you can still die.
However, while being in ghost form, you cannot be killed by most wepons, like swords, axes, ect.
You can only be killed by some kind of special mobs/weapons.
And if you die, than when you respawn, you have some negitive effects.

You can add like some elemental wizard staffs like ummmm fire staff, water staff etc. Like their features would be something like: -


(1) Fire staff - works like lava walker, when holding it, when you walk on lava it transforms into basalt block

(2) Fire Staff - When killing a mob while holding it, it gives auto smelted drops

etc

(If you can, then add this to your data pack Flyrr. I think this will function properly in a mod. Your choice)

Its named beta 1.2 but doesnt beta go only till 0.9 or somehting just asking

A huge sign saying BLIP IS SO COOL that is technically a magical mob so it fits

In my opinion, instead of working on features it'd be a better idea to work on your optimization, so that down the line you don't have to spend a lot of time optimizing old code.

Right now you're repeating a ton of tickly @e checks which is not good at all for performance. Instead, you can just do the @e check once and have it lead to a function that runs everything that you were checking for before.

Also, you may want to cut down on NBT checks by using predicates instead of nbt={} to check for the player's held item. NBT checks are very inefficient and get worse as the player's inventory gets more data; if you have a large book such as TCC's Compendium one NBT check can cost you upwards of 5 mspt per player.