I want some insight on this issue. I have had three steps of incompatibilities in the past: - 1060 to 1.8 version - Everything native broke - 1185 - 1240 - Native item stack changed 'damage' to 'data' all of a sudden - 1240 - 1317 - Item stack got a variable pick up delay added Now, I like to maximize the API, but when people complain of 'method not found' error 24/7 it gets kinda annoying. I end up using reflection, try-catching and Class getting to fix these incompatibilities as I can, but come on...there is a limit! So, as for now, here is my misunderstanding - Plugins have to support the latest CB version - Plugins have to support older versions too! (although not stated) - Every developer should just have every version available in a Jenkins-like environment - Those that don't do this end up uploading lots of older versions 5% of the users download I'd say, screw them, let's just remove the older versions and use the latest. But then people start to complain of 'version 1.8 is laggy' so I have to keep the old version up. I eventually add more features, but obviously don't add them to the older version. The 1060 version of TrainCarts, for example, hardly contains any of the features I added in 1185 - 1317. Where does this stop? And now...the Configuration. Ow boy, here we go. I end up splitting the plugins once AGAIN, all because of some friggen' change of mind. I don't think it is bad, the new configuration section system is a lot better, but why mark it as deprecated? I have hundrets of warnings now and can't fix them, all because of version breakage.