Plugin won't load

[yumm-dev]

Seems like it's something to do with hooks or gamedata, but it will not run. The logs below show off the errors I got relating to it losing its ability to run, and as you will see, it further causes other plugins to not load (these being from the custom attribute starter pack).

L 08/02/2024 - 16:45:40: [SM] Exception reported: Hook not setup for a detour.
L 08/02/2024 - 16:45:40: [SM] Blaming: tf_ontakedamage.smx
L 08/02/2024 - 16:45:40: [SM] Call stack trace:
L 08/02/2024 - 16:45:40: [SM]   [0] DynamicDetour.Enable
L 08/02/2024 - 16:45:40: [SM]   [1] Line 51, scripting/tf_ontakedamage.sp::OnPluginStart
L 08/02/2024 - 16:45:40: [SM] Unable to load plugin "tf_ontakedamage.smx": Error detected in plugin startup (see error logs)
L 08/02/2024 - 16:45:46: [SM] Unable to load plugin "custom-attr-starter-pack\mod_crit_type_on_hitgroup.smx": Could not find required plugin "tf_ontakedamage"
L 08/02/2024 - 16:45:46: [SM] Unable to load plugin "custom-attr-starter-pack\mod_crit_type_vs_condition.smx": Could not find required plugin "tf_ontakedamage"
L 08/02/2024 - 16:45:46: [SM] Unable to load plugin "custom-attr-starter-pack\mod_crit_type_vs_sentry_targets.smx": Could not find required plugin "tf_ontakedamage"

[nosoop]

The "Hook not setup for a detour." message suggests that you have another plugin with a virtual CTFPlayer::OnTakeDamage() hook configured, which means it's likely an issue that stems from alliedmodders/sourcemod#1879.

Can you search the rest of your gamedata to see which other files it may be conflicting with? That said I'll probably shim this in the short term with the workaround I posted in that issue.

[nosoop]

Actually, that doesn't even use DHooks's gameconf parser.

Did you install all the files listed in the release? tf2.ontakedamage.txt must go in addons/sourcemod/gamedata. Afterwards you should restart the server to ensure that it is loaded in.

Note that at this time the plugin only works on 32-bit server instances.

[yumm-dev]

The server is running on 32-bit, always has and always will (probably).

All the files are installed and in the right places, gamedata included. This has happened every time it reloads the plugin and on startup. Assuming it isn't a gamedata issue on the mod's end, it MAY be a gamedata conflict, though how can I identify if one of the files is the source of the issue?

[nosoop]

My mistake; the latest release was from before the fix was applied during the update. Will push out a new release now, but you can pull the file from the repository.

[nosoop]

New release available now.

[nosoop]

how can I identify if one of the files is the source of the issue?

In case you're affected by this in the future, it would be multiple different files with the exact same name under the "Functions" section. For this plugin only CTFGameRules::ApplyOnDamageModifyRules() would be possibly affected.