All translations here! https://es.crowdin.com/project/fnf-mod-installer
Guided engine setup, Google Play update checks, searchable mods and safer installation. See CHANGELOG.md.
Languages: English, Spanish, Indonesian, Brazilian Portuguese, French, German, Japanese, Korean, Simplified Chinese and Traditional Chinese. Full Spanish release history: release-notes/1.0-es.md.
.\gradlew.bat testDebugUnitTest assembleDebug lintDebugTo test alongside the Play Store installation without replacing its data:
.\gradlew.bat assembleDebug -PisolatedPreview=true
adb install -r app/build/outputs/apk/debug/app-debug.apk
adb shell am start -n com.leninasto.fnfmodinstaler.preview/com.leninasto.fnfmodinstaler.MainActivityThe preview application ID is com.leninasto.fnfmodinstaler.preview. Google Play links always use the production application ID.
Check all translations with python tools/check_locales.py. Build a signed production AAB with python tools/build_release.py; credentials are prompted securely and passed only through the build environment.
- Increase
versionCodeand updateversionNamefor each release. Version 1.0.1 uses code 5; confirm this exceeds every code already uploaded to Play Console. - Update
release_notesin each locale andCHANGELOG.md. The local history appears once for each increased installed version code. - Configure
FNF_RELEASE_STORE_FILE,FNF_RELEASE_STORE_PASSWORD,FNF_RELEASE_KEY_ALIASandFNF_RELEASE_KEY_PASSWORDwith the existing Play upload key. Never change the production application ID or publish a debug-signed artifact. - The update checker uses Google Play AppUpdateManager, so availability respects the user/account release track. End-to-end availability must be tested through Play internal testing using a lower installed version code. A manually installed preview can report that checking is unavailable.
- API profiles are intentionally limited to verified official releases. The range
>=0.8.0 <0.9.0was checked inPolymodHandler.hxfor v0.8.1, v0.8.2, v0.8.3 and v0.8.4. ExtendassessApionly after verifying the corresponding release. This checks metadata eligibility, not script/runtime compatibility or the embedded Polymod library version. - Archives are limited to 50,000 entries, 32 path segments, 512 MiB per entry and 2 GiB total decompressed data. Multiple independent mods in one ZIP require separating the archive first.
- The target document provider must support creating folders and writing files. Mods install directly into their final named folder; destination files are not reopened and folders are not renamed after copying. Real write/close errors still fail the installation. Existing mods are preserved with numbered names for duplicates.
- Use Clean up folders on an engine screen to delete unwanted folders, including hidden leftovers from older installations. Review the selected path: deleting a folder removes all of its contents. Failed/cancelled installations attempt recursive cleanup without interrupting that cleanup on cancellation.