Minecraft Client.

Since everyone seems to be making tutorials encouraging bad coding habits, I decided to make a tutorial on how to make a client that is made according to common java standards and hopefully promote those habits in new coders. Hopefully this will help make it so we won't have anymore of the type of people that post code asking for help that has no indents whatsoever and has variable names like j and k.
The Main Classes
The first thing you want to do when making any client is make the main client class; the class that manages and configures all of the hacks. This class should NOT re-declare the static variable theMinecraft, and instead, it should either directly reference it (Minecraft.getMinecraft()) or make a method that returns a direct reference to it. Duplicating static variables just causes more memory to be used, with no real advantage to make it worthwhile. The class is normally mostly static, because it basically is just a wrapper for all of your hacks and the other features of your client (Keybinds, and GUI mainly.) My preferred way of making the hacks work is using an ArrayList of my abstract hacks class. My Hack class normally looks something like this:
The toggle method allows code to not be repeated in every class, while at the same time allowing hack-specific enable/disable code. The name and description variables are namely for either an ArrayList GUI, or a help message. The onUpdate method has the Minecraft variable passed into it as to avoid redeclaring the static variable Minecraft.theMinecraft;
Now that we got our abstract Hack class done, and we have made our hacks, we should now finish that main class I was talking about in the beginning. Here is a pretty good template for a main class:
This class, as you can see, operates on an ArrayList of the hacks, like I said before. I find this to work well, because in order to toggle something, you don't have to know what your toggling at compile-time, which can simplify a lot of methods, for example your process-command method. I initialize the hacks into the arraylist in a static block, so it is guaranteed to be loaded at runtime. I'm starting to get tired, so I think I am going to split this into 3-parts and get the second part done later.
Post your opinion on this thread please (Constructive criticism allowed.)