Shauren

use item id, not name

Quests cannot do that. It is world.gossip_menu_option BoxCoded column (and you have to write a script that implements this function https://github.com/TrinityCore/TrinityCore/blob/3.3.5/src/server/game/AI/CreatureAI.h#L207)

You mean the tag? You clearly did not build the extractor from that tag. WDC3 was introduced much later

You cannot use current version extractors with older client version. You must use the version that existed when your desired client version was current

To get older versions, you need to checkout one of the tags in repository (we have one, "7.3.5/26972") but I will make no guarantees that you will be able to compile it without issues

After you build vmaps by running vmap4assembler, you can delete Buildings directory, everything else is required

In that file you only need to allow '1SLC' (or was it 'CLS1'?) where it currently checks for 'WDC3' But the structures I was talking about was this file https://github.com/TrinityCore/TrinityCore/blob/f759809d9d4364bc1d988e4390d3d5a33d5469e9/src/tools/extractor_common/ExtractorDB2LoadInfo.h

master branch extractor will get you closer but it will not work without any modifications to the code (you will need to update db2 reader to support classic format)

This is because mysql stores table and column names as lowercase on windows (accountid, securitylevel) but on linux they are case sensitive (AccountID, SecurityLevel) Make sure that your exported windows database file has correct names in them (use mysqldump, not any other 3rd party export tool)

You cannot select it manually, it will happen automatically, depending on dungeon/raid difficulty (only works inside instances)

shared auth db - yes shared authserver - no

This spell is intended to do 200% of targets health in damage, what you need to do is use conditions table to prevent it from being used on anything other than its intended quest target

But that builld DOES have a git tag... https://github.com/TrinityCore/TrinityCore/tree/8.3.7/35662

Generally only major patches get tagged with git tags (on their last commit, before update to the next one), minor hotfix builds do not - your best bet is to look at commit history

Use TDB, not whatever empty db you have there