Once Developer Capes is in your classpath somehow, you are going to want to add this to your mod when it initialized. It registers a cape config with DeveloperCapes.

Note: The note that was previously here, that said DevCapes didn't have to go in a client proxy, has been redacted. You need to put config registration in the client proxy again

DevCapes.getInstance().registerConfig($CAPES_JSON, $IDENTIFIER);

$CAPES_JSON is the URL (in Object or String form,) InputStream, or File to a text file hosted on a server, Dropbox, or GitHub, that has all the data Developer Capes needs to add your capes formatted in JSON. $IDENTIFIER is a unique mod identifier so DevCapes can keep one mod's groups separate from the other.

The JSON for the config looks like this:

{
    "Group1": {
        "capeUrl": "http://www.example.com/group1_cape.png",
        "users": [
            "JadarMC",
            "MinerID642"
        ]
    },
    "Captain_Shadows": "http://www.example.com/captain_cape.png"
}

You are going to want to make sure there is a comma after every element in the array, or string, etc, -except- when it is the last one in it's scope. If you do the logs will make this very clear.

#####Images: The cape image files are 22x17, and should be of the PNG format. Additionally, Developer Capes supports high definition capes. Those must be of the size that is divisible by 16. The height must be half of the width. So 1024x512, 2048x1024, and so on. Host them on a server, Dropbox, or GitHub.

Thats it! If you have any trouble, make a post in the Minecraft Forums post or make an issue here on GitHub.

####2. I'm getting a NoClassDefFoundError and/or a RuntimeExcption (related to an invalid side) on a dedicated server: See answer to question 1.