So, I unpacked your mod to see if I could find anything to help you on, and I've come up with a few considerations I hope you will look into:

1) Never overwrite vanilla files whenever possible. For example, your mod overwrites monster.treasurepools (among others). By doing so, your mod breaks any other mod relying on monster.treasurepools that was loaded earlier in the load order (such as my 100% Boss Unique Drops mod is someone subscribes to your mod after mine). Whenever possible, use the .patch method to avoid compatibility issues, as you did with player.config.patch. I will add a patch version in a lower post here to help you along, plus some additional considerations, and a couple tools that will make your life a LOT easier.

2) Whenever creating custom assets, devtag your assets and internal names to make them more unique. For example, the itemname of your weapon is "ancientsword" - not especially unique, meaning there's a pretty good chance that another modder with a little less diligence could create another "ancientsword" causing crashes for anyone that installs both mods at once. Instead, consider using "as_ancientsword" (as=Ancient Sword, mod name) or "dl_ancientsword" (dl=DracoLord) to lower the chance of mod overlap, which can cause mismatched graphics or crashes.