GAME_LOADER

The loader our own code lives on — which can always see the game, being it or a child of it (on a plugin host this is the plugin loader, whose parent is the server's). Every mcp thread sets its Thread.contextClassLoader to it: a thread inherits that from whoever created it, and the FML worker our init runs on carries the app loader, which sees neither MC nor any mod library — so a library resolving through the context loader fails on our threads and nowhere else. Read off this class, in the root package, so the masking loader delegates and both sides answer with one value.