Custom Car (BakkesMod plugin)

Enables custom cars in Rocket League, for free!

🎥 Video showcase: https://www.youtube.com/watch?v=Ipqlp0zsMZc

✨ Features

• Use custom 3D models for car bodies and toppers
• Spawn and use any car in the game
  • In freeplay: Hitboxes will be accurate
    • Perfect for test-driving cars before purchasing in RL item shop 👍
  • In online games: All spawned cars will have Octane hitbox
    • This is due to the game's online protections: If you don't own your car, you're forced to use a stock Octane (server-side)

💻 Install the plugin

Follow the install steps in the latest release

📂 How to INSTALL custom cars

1. Download (or create) a custom car. You can find some here
2. Extract the .zip file. Somewhere inside will be a .json file and a .upk file
3. Click the Open CustomCars folder button in the plugin, and put the .json file in that folder
4. Open the CookedPCConsole folder of your RL installation, and put the .upk file there
   • An example MyCustomCar.upk installed on Epic (the path be different for Steam users):

     C:\Program Files\Epic Games\rocketleague\TAGame\CookedPCConsole\mods\CustomCars\MyCustomCar.upk
     

   • You can create subfolders to organize your .upk files if you want. As long as the .upk files are somewhere inside the CookedPCConsole folder

🧪 How to MAKE custom cars

Here's a video tutorial: https://youtu.be/OlwnVdYyhbk

• Make sure put the the .json files in bakkesmod\data\CustomCar\CustomCars instead of the acplugin folder shown in the video

🔨 Building

Note

Building requires 64-bit Windows and the MSVC toolchain, due to reliance on the Windows SDK and the need for ABI compatibility with Rocket League

1. Initialize submodules

Run ./scripts/init-submodules.bat to initialize the submodules after cloning the repo

🔍 Why this instead of git submodule update --init --recursive ?

• Avoids downloading 200MB of history for the nlohmann/json library
• Ensures Git can detect updates for the other submodules

2. Build with CMake

Note

Before building with CMake, the MSVC environment must be initialized. This is normally handled automatically by IDEs or certain editor extensions like CMake Tools, but if you're building from the command line, use one of the following methods:

• Use an appropriate Windows terminal profile:
  • Developer PowerShell for VS 2022
  • Developer Command Prompt for VS 2022
• Or run this script once per shell session:

  C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars64.bat
  

0. Install CMake and Ninja
   • If you prefer another build system, just create a CMakeUserPresets.json and specify it there. More info here
1. Run this to configure build files:

   cmake --preset ninja-release
   

   • Other configure presets are available in CMakePresets.json
2. Run this to build:

   cmake --build --preset Ninja-Release
   

   • Other build presets are available in CMakePresets.json
   • The built binaries will be in ./plugins