Nimble Localization!

Hey everyone, exciting news!

I've found a way to organize and manage the many localizations/translations of Nimble that people have been asking for. We're using GitLocalize. You'll need a GitHub account, all you'll need to do is send me your git username to be added to the project, and let me know which language you'd like to contribute to (you'll just need to login to gitlocalize with your github account first).

Here's a quick video on how it works (it's pretty easy—you can skip the first 30 seconds or so, the project has already been set up).

How will the localizations be used?

They will be given away for free to anyone who already has purchased Nimble. If there is enough demand for a localized print run, some languages may even get full books in their own native language! (Though that is a long way off currently, if it ever happens.)

Let's get started!

Email me (evan@nimblerpg.com) your github username and language of expertise and I'll add you to the project. I'v also started a post on Discord to discuss further.

Localization Guidance

For non-rules matters, go for "vibes" rather than literal word-for-word translation. Example "Greenthumb" is in English a play on words, as the villain literally is green, but having a "green thumb" is a saying indicating talent in working with plants.

Or with the location "Merivale" you could keep it as "Merivale" if it sounds pleasant enough in your local language, or you could translate to anything similar that has the vibes of "happy valley town"

Of course please change anything that would cause confusion or the wrong idea, for instance the "Bunbun" ancestry sounds cute and rabbit-like in english, but means something not so nice in Portuguese!

For rules text, keep it clear and concise. Nimble follows many 5e customs: Capitalizing game important terms (Poisoned, Prone, Crit); but not all 5e customs: using CAPS or bold to emphasize things that may be easy to miss (actions are recharged at the end of your turn), "save" instead of "saving throw," "armor" instead of "armor class" etc.