In previous releases, i18n support wasn't fetching the correct fields to accurately display them when a language is set. This release does not address the wider interface localisation (ie fields like cost, range, etc), or implement language-specific caching.