pacid | PostgreSQL Awesome Consisteny and Integrity Differ | Database library

getClass().getResource() is incorrect; the proper syntax is pacman.class.getResource(...) where pacman is your own classname*.

Second point, your exception handling is broken. Exceptions contains 4 useful things (the type, the message, the stack trace, and the causal chain).

You're throwing away 3 out of the 4 things. Don't do that; either actually deal with it (logging or printing errors is NOT dealing with it!), or throw it onwards (put throws IOException on your method/constructor signature), or if that's no good either, go with catch (Whatever e) { throw new RuntimeException(e); } which is not great but a heck of a lot better than e.printStackTrace().

You do not have to import anything; import is aliasing type names (import com.foo.Bar; means: Anytime anywhere in this file Bar is written and indicates a type, imagine it read com.foo.Bar instead. It neither loads the Bar class into memory nor runs any code inside it, and it has nothing to do with resources).

Without a stack trace of the error we can't help you.

IF it is a nullpointerexception on the line that starts with case 1 or the line that starts with case 2, yes, it's because the resource is not found.

Assuming you fixed the above issue (pacman.class.getResource instead of getClass().getResource) and this is still happening: the way getResource works is that it looks relative to the directory that contains pacman.class... even if said class is, say, inside a jar file. So, if you have, say, /home/BotFred/workspace/com.botfred.pacman/build/com/botfred/pacman/pacman.class, then, it expects the image to be at /home/BotFred/workspace/com.botfred.pacman/build/com/botfred/pacman/Images/lolface.png.

If you're not quite sure where pacman class is being loaded from, you can always do this to find out: