packager VS MythicDungeonTools

Also, GitHub repos can use https://github.com/BigWigsMods/packager instead of curseforge release system to get their dependencies, publish to various sites, and support multiple versions of the game.

Same here. All the addons I've developed are on Wago, Wowinterface, and GitHub, as well as Curse. It's super easy these days to deploy to all three places at once using the BigWigs Packager so the day Overwolf pulls the plug on WowUp my addons should just be transitioned to being downloaded from Wago (if enabled) or Wowinterface (if not).

Mapping changes: * Neltharion's Lair mapping updated (see https://github.com/Nnoggie/MythicDungeonTools/issues/465). Bugfixes: * [\#1739](https://github.com/Wotuu/keystone.guru/issues/1739) When new affixes are added, a hard-reload is no longer required to fetch the latest affixes image. If you didn't do this you'd see the wrong images for the affixes until you did.

This question arose when I tried cloning an addon's github repo in hopes of contributing to it. But I quickly realized it won't run as-is because the libraries aren't part of the repo. Next I tried downloading those libraries and putting them in my AddOns folder, but I still see UI errors because the addon's xml file is attempting to load those libraries from a relative path. If it helps, the particular addon I was attempting this with is https://github.com/Nnoggie/MythicDungeonTools/tree/master/libs Strangely, this addon's repo does include a copy of LibDeflate, but not any of the other libraries it's trying to include from load_libs.xml. So clearly I'm missing something about how addon devs handle dependencies during the actual development.

If you find any wrongly placed npcs or bugs you can report them on GitHub or in Discord.

You can find a full list of changes here.

this release is with data https://github.com/Nnoggie/MythicDungeonTools/releases/tag/v3.3.4 If you still want to user this over ManbabyDungeonTools, which are superior by name.