I was writting against 2.1-SNAPSHOT and everything broke last night when I assume someone made a new commit, frustrating but it is SNAPSHOT so w/e. Can someone recommend a version to code against, my ultimate Target is a 1.8 spongeforge server.
Always the latest while 2.1 is in development.
3.0 I believe will be the Beta release so you should be able to stick to that for a while longer (the API won’t break as frequently from this point onwards)
Any tips for coding against a moving target like that? IIRC org.spongepowered.api.util got broken out and pieces of it placed elsewhere which is what caused my issue. Shouldn’t changes like that be reserved for major version changes?
Well that change was one of the most breaking in a long time (possibly since the event refactor).
The only tip I can really give you is to keep watching the commits https://github.com/SpongePowered/SpongeAPI/commits/master and update to the latest build often.
While the API is being tested/implemented etc. it’s likely that people will notice things that should be changed which is why the API is in flux a lot. After beta I believe the release model will change so that it’s not as breaking all the time (I’m not sure on the finer details though)