Comparing the old actions to the new custom actions provided in the asset the new ones seem to be using a namespace instead of doing the using DarkTonic.Coregamekit;
Core game kit is also located in the plugins folder so not sure if the namespacing could be triggering the errors, but that's definitely all thats changed with the actions. Also weird that the action browser can see the actions.