Would you say it is better practice to have one seperate Java class file for each defined object/class or would you say it is better to have one file that defines all of the objects/classes and then your main pulls from that.
For example say I was making an old rpg game, would it be better to have:
enemy.java (Contains classes for goblin and orc)
spells.java (Contains classes for fireball and telekenisis)
One file per top-level class always. Also, use proper capitalization for your classes and source files. You should have a class Player in a file named Player.java. Note that you spelled Telekinesis incorrectly.
What makes an Orc or a Goblin so different from the Enemy class that you need separate classes for them?
Don't use plural for class names, unless it's a utility class. Your Spells class should probably be called Spell instead.
Note that elements ending with a "/" in the above are directory names. Also note that except for the "src" directory, the sub-directories are all packagename components. So, for example, Glamdring would contain the following declararation:
Which you could import or request by its fully-qualified classname of com.jamesritchie.fantasygame.weapon.sword.heroic.Glamdring.
Note that even under Windows, all file and directory names are case-sensitive in Java. Also that package name components must start with lower-case. In fact, in Java, only constants (sometimes!) and class names should start with an upper-case letter as a general rule. There are tools that are expecting this practice, even though it's not part of the actual Java specs.
Bjoke: A "Bully Joke". A Statement or action made with malicious intent - unless challenged. At which point it magically transforms into "I was just funnin'" or "What's the matter, can't take a joke?"