Mod Support

What is this page

Modding is a core part of BeamNG, and we want to make it as accessible as possible. This page provides basic troubleshooting tips for common issues you may encounter while creating mods. It is not a full tutorial, but a starting point to help you diagnose and fix problems.

Our community regularly shares content, and newcomers are always welcome, so don’t hesitate to get started.

Office Hours

We aim to respond to support requests within 1 to 2 working days.

Official mod support hours:

Monday to Friday, 10:00 to 15:00 CET

Repository Approval Time

All submitted mods go through manual review. This may take a few working days.

If your mod disappears from “pending approval” and is not published, you will receive a private message explaining what needs to be fixed.

Modding FAQ

1. My mod is broken in multiple ways. How can I fix it?

Start by clearing the cache (see Useful Links). Many issues, especially with materials and models, are caused by outdated cached data.


2. My vehicle does not spawn. What should I do?

Check the console (~ key) for errors. Most spawning issues are related to JBeam problems. See Introduction to JBeam .


3. My mod loads slowly or freezes the game

Open the console (~) and fix any reported errors. Poorly optimized or error heavy mods can cause long load times and freezing.


4. My Automation car was not approved

Make sure you uploaded the exported vehicle from Automation, not just the .car file. The correct export can be found in your BeamNG mods folder. The repository does not support raw .car files. See Common Automation export issues .


5. My mod was rejected for replacing game files

Avoid overwriting original files. Use subfolders inside /vehicles/ and check the console for “duplicate files found” warnings. Check Overwriting game files issues .


6. My vehicle pack is incorrectly packaged

Use a single .zip file containing all vehicles. Each vehicle should have its own folder inside the archive. Automation “art” folders can be placed at the root if needed. For more information see Correctly packing mods .


7. My mod is packaged incorrectly

Always place files inside the proper structure, e.g. /vehicles/yourmod/.

Do not leave files in the root of the zip or add extra unnecessary folder layers. Check Correctly packing mods .


8. My mod shows orange “No Texture” materials

This is usually caused by incorrect paths in main.materials.json.

Check:

  • File paths and typos
  • File extensions
  • Matching material names between your 3D software and material files

Using Texture Cooker is recommended instead of raw PNG textures. See more here .


9. I have JBeam issues (parts disappearing, breaking incorrectly, etc.)

Common causes:

  • Incorrect flexbody names
  • Mismatched beam or deform group names
  • Inconsistent naming across files

Avoid starting names with numbers and keep naming consistent throughout.


10. The game cannot parse my JBeam file

JBeam uses JSON syntax. Even small mistakes will break it.

Tips:

  • Use a code editor like VS Code with JSONC mode
  • Always properly open and close brackets { }
  • Ensure deform and break groups are properly closed

11. My material file overwrites original materials

Use materials.json instead of the deprecated materials.cs.

You can rename your material file (e.g. mymod.materials.json) to avoid conflicts with base game files. Check Overwriting game files issues .


12. My model does not appear, but there are no errors

This is often due to incorrect origin settings.

In your 3D software, set position/rotation/scale correctly and apply transforms (e.g. “Apply All” in Blender). The model origin should be at 0,0,0.


Useful links

How to get support

  • Post in our forum : This is the preferred way, since other users could have the same problem and so we can help more people at the same time.
  • Ask us on our Discord server : Here other users and moderation team can help you with your issues. Since Discord is an instant messaging platform you might get help in shorter amount of time.
Last modified: April 23, 2026

Any further questions?

Join our discord
Our documentation is currently incomplete and undergoing active development. If you have any questions or feedback, please visit this forum thread.