It will be really great if players are willing to help out by updating language files for GC3. You would need to do this: 1) Look in all four of the language folders for the different parts of GC3, which are Core, Moon, Mars and Asteroids. https://github.com/micdoodle8/Galac...c/main/resources/assets/galacticraftcore/lang https://github.com/micdoodle8/Galac...c/main/resources/assets/galacticraftmoon/lang https://github.com/micdoodle8/Galac...c/main/resources/assets/galacticraftmars/lang https://github.com/micdoodle8/Galac...n/resources/assets/galacticraftasteroids/lang 2) You are looking to see if your language is there already - and if it is, you will want to look to see if somebody updated it already. The recently updated languages are: Chinese - zh_CN - thanks to sb023612, XZzh, Mrkwtkr and Joccob Chinese (traditional) - zh_TW - thanks to mymagadsl Croatian - hr_HR - thanks to CroComeT Czech - cs_CZ - thanks to hunator English - en_GB - I have that one covered French - fr_FR - thanks to Linyor and bart74 and Mazdallier German - de_DE - thanks to Vexatos with davidpox, Gebatzens and ErrorCraftLP Hungarian - hu_HU - thanks to CaptainTurbomuffin Japanese - jp_JP - thanks to Lapiman Netherlands - nl_NL - thanks to HellThunder Polish - pl_PL - thanks to MrNaxeros Portuguese - pt_BR and pt_PT - thanks to Ezer'Arch Russian - ru_RU - thanks to Adaptivity Spanish - es_ES - thanks to DavidSainz with Juput Swedish - sv_SW - thanks to Space Viking Thai - th_TH - thanks to SteveMCCommander Turkish - tr_TR - thanks to toltol If nobody updated it recently then it will definitely need updating, as plenty more of the Galacticraft text has now been made translatable. These languages need updates please: Finnish - fi_FI Welsh - cy_GB 3) If your language does not exist already in Galacticraft, then check that it's one of the 62 languages which Minecraft recognises and look up the 'Locale Code' here: http://minecraft.gamepedia.com/Language. I don't really see Latin or Quenya as top priorities - I'm really not sure that ancient Romans or Elves have a word for Space Rocket. Even if the planets are all named after Roman gods... 4) You need to end up with 4 lang files which are like the 4 en_US.lang files, but (obviously) with your language after the "=" on each line. The text editor must save in UTF-8 encoding. nice explains from @Wulfyk and @tyrantelf on the old thread http://forum.micdoodle8.com/index.php?posts/5680/ The left side of the lines (before the "=") must be an exact match to the en_US language files. Every line will need to be translated, otherwise players will be missing some translations in your language! But if you're not sure about something, it's probably OK to leave the English text for now, someone can fix it later. And you can skip the "#" comment lines. Lines with a "$" are long lines which can be split across 2 lines when shown as tooltips in the game - you must not use a "$" for lines which do not have a "$" in the en_US - but if there is a "$" in the en_US, you can use as many "$" as you need in your language text, that can be none, or 2 or more Lines with "%s" or "%d" are lines which in the game will have a name or number in place of the "%s" or the "%d" - if it's a name, probably it's a player's name, or maybe a team name or an item name. 5) We sometimes update the en_US language files. It's because new labels get added to the Galacticraft code or someone spotted an old thing which still needs translating. When we change the en_US on Github, we will reference the translators named above by @name - that way if you are 'Watching' the Galacticraft Github using the setting "Be notified when @mentioned" then you will receive a Github notification automatically. We recommend translators use that Github setting instead of the larger "Be notified of all conversations" which will fill your inbox with messages. I will also post here when significant updates to the en_US.lang files are made. Significant updates on July 25 and August 14, 2014. To make things easier for our translators, whenever there are significant updates your language file will be automatically marked '##NEEDS TRANSLATE##' on any new lines which need translation. The US English text will be there as a placeholder meanwhile. 6) When you have lang files which are ready to go into Galacticraft: If you know Github then push the changes to your own fork of Galacticraft then make a pull request. If you don't know Github, just post the lang files online somewhere and give us a link to them and we can do the rest for you (create a new issue in Galacticraft's Github to give us the link) - please name them core, moon, mars and asteroids so we know which is which. 7) For .lang files already in Galacticraft, anyone can actually edit them online on Github, it's pretty easy to do. The steps: a. Go to any page of Galacticraft on Github (links earlier in this post). b. Make a "fork" in Github by pressing the fork button - this fork will be personal to you, so don't worry, you can't break anything by changing stuff in the fork. c. On the main page of the fork you made, look for 'src', then navigate into that and find the .lang files, they are in folder src/main/resources/assets/galacticraftcore/lang, or galacticraftmoon, galacticraftmars, galacticraftasteroids d. Click on the .lang file you want to edit e. Edit the .lang file online (the file on your screen should have an edit button like a pencil, the edit button becomes active if you are working in the Fork you made) f. When you're happy with your changes, "commit" the changes (scroll down the screen to see the 'Commit changes' button) g. When you're done with all the .lang files, go back to your fork main page, hit the Pull Request button, this will notify us your changes are ready to be included in Galacticraft. Edit by @Ezer'Arch: Topic split from here for better reading.