A BUSSID mod that does not appear in Garage is usually caused by a file or installation issue rather than a permanently broken game. Work through the checks below in order. Changing one thing at a time makes it much easier to identify the real cause.
1. Check what you actually downloaded
Look at the full filename in your file manager. Normal community vehicle packages are often distributed as .bussidmod or .bussidvehicle files. If your download ends in .zip or .rar, open or extract the archive first and look inside for the actual mod file. Do not simply rename the archive extension.
2. Make sure it is a vehicle mod, not a livery image
A JPG or PNG is usually a livery/skin, not a driveable vehicle. Liveries are applied to a compatible bus or vehicle through the game’s paint/livery workflow. See our livery guide if you downloaded an image rather than a mod package.
3. Confirm the storage location or import method
Android versions and file-manager apps do not always show storage in the same way. If your device allows direct folder access, confirm that the mod is in the location BUSSID expects. If Android restricts that folder, use the game’s own import option where available instead of granting unnecessary permissions to an unknown file manager.
4. Fully close and reopen BUSSID
Moving a file while the game is open may not refresh the Garage list immediately. Close BUSSID from recent apps, wait a moment, reopen it, then check the Garage again.
5. Test the newest file by itself
If you installed several mods at the same time, move the newest files out temporarily and add them back one by one. One malformed or incompatible file can make it look as if the whole mod folder is broken.
6. Check whether the creator mentions a required BUSSID version
Mods can stop working after a game update. If the page credits a creator or original source, look there for a newer release. Avoid downloading multiple random reuploads simply because the version number in the filename is newer.
7. Check for a double extension
Some file managers hide known extensions. A file that appears as truck.bussidmod might really be truck.bussidmod.zip. Enable “show file extensions” if your file manager supports it, or inspect the file details.
8. Check available storage
Very low free storage can cause extraction failures, incomplete copies and crashes. Delete unnecessary temporary files or move media elsewhere, then download/extract the mod again from the original source.
9. Do not install an unexpected APK
If you intended to download a BUSSID mod and a site suddenly asks you to install an APK, stop and verify the source. A normal vehicle or map mod should not require you to replace BUSSID with an unrelated application.
10. Reinstall only as a last resort
Reinstalling the whole game can erase local files or settings if they are not backed up. First remove the suspected mod, restart the game, and test a known working vehicle. If the base game works, the problem is probably the added file rather than BUSSID itself.
Quick diagnosis table
- ZIP/RAR downloaded: extract it and locate the actual mod file.
- PNG/JPG downloaded: treat it as a livery and use the livery workflow.
- Correct file but no Garage entry: recheck location/import, restart the game and check version compatibility.
- Game crashes after adding one mod: remove that file and test without it.
- All mods disappear after an update: check whether the update changed compatibility or storage access.
For more context, read BUSSID file types explained and the lag/crash troubleshooting guide.