Ok, so I’ve seen all this ruckus with the microsoft and bukkit and I’ve really wanted to help, so I’ve decided that I want to start to try coding plugins, but the thing is, I don’t know where to start. So do you guys think you can help me?
Learn Java first. Best way to learn it is by practice IMO. Just go out there, find yourself a tutorial of that basics that suits you and then try making your own projects. If you don’t know something, the interwebz are a great resource, especailly stackoverflow.com. Then when sponge is ready, there will be tutorials out there how to get started. And if you have questions, there is always the Sponge IRC.
Right now there’s no tutorials or anything because the API is incomplete. However I’m sure that when it is officially released and supported there will be a ton of awesome people making tutorials on it.
I assume you’re not going to make pull requests, as they often do require more experience than just creating simple plugins. You’ll have to discuss about API design, wait and… wait more if you make PRs.
Sometimes not everything is documented like bukkits innards, everything reflection reflection that, had to search the forums for days so yeah source code is still the best
let me try putting it back on topic. note that i am assuming you know enough Java to make something simple, and if not then i suggest you do that first. there’re lots of sources of information online and on the youtubs if you don’t feel like buying those 2015-dictionary-sized books
its already well known that sponge is gonna take a little longer to bloom out its full-fledged api, so as a source of practice you might wanna try making some basic sample bukkit plugins and port them over once the api’s out.
it sounds stupid but thinking about it it gives you a chance to learn about how you can make your plugin and the whole refactoring process of porting it over lets you learn more about the sponge api.
@Xemiru@DotDash Exactly! While you guys learned from doing, I learned from reading. I’m the type of person that can read something and then instantly apply it. So I would personally say read the java bible, and text-based- tutorials. I’m also the kind of person to provide pseudo code or a picture of code instead of text code where you can copy & paste. If you are forced to write it you are more likely to remember what you did and why. (Atleast some people are)
I learned a lot by trial and error. I’d try to find my own approach first and if it didn’t work I’d try again. And if I found no solution at all, there were still the interwebs…