alburdet619

I know this is a really old thread but I want to say that I agree completely that there needs to be some sort of documentation. C# coding is my job and I've produced and worked with many API's. In any API, there is literally no way to know how to use it without documentation. I mean sure, you can spend hours upon hours staring at each class but as it was stated earlier there is even stuff in the base minecraft classes like Item and Block that you don't see unless you know to look. I am new to MC modding and I've been working at it for a couple of weeks now trying to cling to little bits of information I've gleamed from videos and tutorials that I've found here and other places but it isn't a substitute for real documentation. I know it's a pain but it's also good coding practice. My example of why: I created several new ores and such and have added tools for each of them. Well the only way I found before to add to the EnumToolMaterial was to create my own class that mimics the behavior of EnumToolMaterial and set my own values. This of course means to make the sword I have to extend ItemSword, or ItemPickaxe for the pickaxe tools and so on. If I had known about the EnumHelper class before I wouldn't have had to go through that pain. Again though, I just saw this in the little bit of produced documentation and I haven't had a chance to look into it. It may not even do what I think it does. Who knows? So please, don't think I'm saying you're doing a bad job in any way. I think what you've provided here is invaluable for the modding community. My message is just that producing an API should always mean producing documentation on using that API. Do with that information what you will.