Intro Hey everyone
- Thread starter QKD5
- Start date
Hi @QKD5 and welcome! 
Could you tell us a little about your background? Do you like working with code, making content, doing artwork, etc?
Getting the code working is a good step, after that you could check out the list of contributor friendly issues on GitHub and see if any of them stick out to you as doable. That's what those issues are marked for, beginner friendly in some fashion, although at varying difficulties depending on what you're used to
For instance #1198 is an easy tweak to how the "Back" button aligns in places. Or #1144 is about adding more individual options to the graphic settings. Or #520 which would be adding a new label in a corner of the main menu holding the game data directory.
As a general hint "Search" in code is your friend! Usually you can find whatever code relates to something with a few quick searches
Could you tell us a little about your background? Do you like working with code, making content, doing artwork, etc?
Getting the code working is a good step, after that you could check out the list of contributor friendly issues on GitHub and see if any of them stick out to you as doable. That's what those issues are marked for, beginner friendly in some fashion, although at varying difficulties depending on what you're used to
For instance #1198 is an easy tweak to how the "Back" button aligns in places. Or #1144 is about adding more individual options to the graphic settings. Or #520 which would be adding a new label in a corner of the main menu holding the game data directory.
As a general hint "Search" in code is your friend! Usually you can find whatever code relates to something with a few quick searches
QKD5
New Member
Thanks Cervator,
I'm a student in college majoring in Computer Science and I'm looking to get more experience in working with open source projects (Java is my main language). I would enjoy making content but my primary focus right now would just be to help out with whatever I can (maybe small changes here and there at first and working on docs) so I familiarize myself with the codebase.
I'm a student in college majoring in Computer Science and I'm looking to get more experience in working with open source projects (Java is my main language). I would enjoy making content but my primary focus right now would just be to help out with whatever I can (maybe small changes here and there at first and working on docs) so I familiarize myself with the codebase.
Improving Javadoc is a great way to contribute. Find a spot that doesn't look too hard to understand yet lacks javadoc, then document to the best of your ability as you learn the code. Put it all in a pull request on GitHub and we can review and advise if any of it looks like it needs further tweaks
Compiler warnings, Checkstyle warnings, Findbugs issues, deprecation notes etc are another good source of simple quick fixes that may not be specific issues on GitHub. There are TODOs strewn around inside the codebase too. Usually easy to find them all in an IDE, may have to install a plugin or two (such as for Checkstyle or Findbugs)
