is not related to the errors log i posted above. I have also had a very hard getting plugin to package with my project, every i have trouble with plugin it is a coding error of some sort from fresh downloaded files.
I am also aware of engine changes regarding plugins from 4.15.x - 4.18.3. has a lot to do with it.
However despite the condescending ease of use and correctly functioning library of nodes, it does not serve any purpose than to block me from packaging a development build of my project.
The information about Current Engine(4.17 ,4.18, 4.19 (2017-2018)) installation guides and packaging needs to be completely rewritten and re-posted here at the beginning of the thread with a date on it the last the instructions were correct, the information to be found is too far scattered across the forum and information needed is unclear.
I am not disgracing the plugin, as we know the work puts in is legendary, but information format is failing with and the needs to be addressed.
I myself would like to continue to use the plugin but i honestly would be wasting my without updated instructions, regarding the fact that i cant package my work for simple debugging/profiling with it in use.
I will provide accurate information about my specific current at a later once of have run some tests and completely exhausted my faults with documented results and possible repro steps.
Sorry to sound so harsh but your attention is needed and would be greatly appreciated.