Okay, this error should now be fixed in version 1.2.1! It was just a condition that checks for a target node that was causing the issue. I also fixed a bunch of the typos in the error message logs, so now they shouldn't be as confusing (no more double negatives).