Trivial Description
The initialization code in RuntimeInstance uses a /-prefixed resource path to read a class's resource. This is a bad coding idiom in general and the logging message adds to the confusion because it creates a File instance out of the resource...
The problem with '/'-leading paths is that many obfuscators (including maven shade) don't recognize it as a resource path and don't replace it when repackaging.
The attached patch uses the class loader to read the resource (without prefixing it with '/').