AgentTadpole

From what I can tell, this is because Mojang snuck in a ninja update before it fully released 1.6.2, changing the md5 checksum from what Forge believes it should be (the md5 checksum from the prerelease). If this is the problem, there's nothing we can really do about it until Forge updates, at least nothing I know how to do. Don't quote me on that, by the way, that's just what I've gathered from the IRC channel.