[Guide] How to Mod Big Walk (Unity 6 / IL2CPP) on macOS (Apple Silicon / Intel) using Porting Kit

Want to play Big Walk with mods on a Mac? This is the beginner-friendly route that works through Porting Kit and Wine, including Apple Silicon and Intel Macs.

Why native Mac modding usually fails

Big Walk uses Unity 6 and IL2CPP. Many traditional native-Mac modding approaches rely on tools such as plthook, but macOS security protections and the way Unity 6 loads native code can prevent those methods from working reliably.

The easiest route is to run the Windows build through Porting Kit’s Metal/DXMT Wine environment. This gives BepInEx the Windows-style files and loading behavior it expects, while DXMT handles the graphics path on macOS. For most Mac users, this is the simplest and best way to play Big Walk with mods.

Prerequisites / tools needed

1. Porting Kit — free: https://www.porting-kit.com/
2. A Steam account with Big Walk
3. BepInEx 6 IL2CPP Windows x64, Build 733 or newer

Recommended build: BepInEx Unity IL2CPP Windows x64 bleeding-edge Build 733:

https://builds.bepinex.dev/projects/bepinex_be

Step 1: Install Porting Kit and set up Windows Steam

1. Download and install Porting Kit on your Mac.
2. Open Porting Kit.
3. Find and install the Steam port named:

​

Steambuild 32/64bit Metal 

1. This is the Metal/DXMT build. When Porting Kit asks for the Windows environment, use the Windows 10 64-bit setup.
2. Let Porting Kit finish installing Steam, then launch Steam from inside Porting Kit.

Step 2: Download Big Walk inside Windows Steam

1. Sign in to your Steam account in the Porting Kit Steam window.
2. Find Big Walk in your Steam library.
3. Install it normally through this Windows Steam environment.
4. Wait for the download and installation to finish before continuing.

Big Walk’s Steam app ID is:

1478500 

Do not use the native Mac installation for this guide. The modded copy must be the Windows version installed inside the Porting Kit bottle.

Step 3: Download and extract BepInEx 6

1. Open the BepInEx bleeding-edge builds page:

https://builds.bepinex.dev/projects/bepinex_be

1. Download BepInEx 6 Unity IL2CPP Windows x64, Build 733 or newer. The Build 733 filename is:

​

BepInEx-Unity.IL2CPP-win-x64-6.0.0-be.733 

1. Extract the downloaded zip file somewhere easy to find, such as your Desktop or Downloads folder.
2. After extraction, you should see the BepInEx files and folders that need to be copied into the game directory.

Step 4: Copy the BepInEx files into the game folder

You need to copy the files next to Big Walk.exe, not into a separate subfolder.

Find the folder through Porting Kit

1. In Porting Kit, select the Steam port you installed.
2. Open the port’s menu and choose:

​

More -> Open C: Drive 

1. Browse to the Big Walk installation folder.

The usual path is:

drive_c/Program Files (x86)/Steam/steamapps/common/Big Walk/ 

Depending on the Porting Kit version, “Open C: Drive” may open a Finder window directly inside drive_c. From there, follow:

Program Files (x86) -> Steam -> steamapps -> common -> Big Walk 

1. Confirm that this folder contains:

​

Big Walk.exe 

1. From the extracted BepInEx archive, copy these items directly into the Big Walk folder:

​

BepInEx/ dotnet/ doorstop_config.ini winhttp.dll 

When finished, the folder should look roughly like this:

Big Walk/ ├── Big Walk.exe ├── BepInEx/ ├── dotnet/ ├── doorstop_config.ini └── winhttp.dll 

Step 5: Configure the Wine DLL override

This is the most important step. Without the winhttp override, BepInEx may not load and the console window may never appear.

1. In Porting Kit, select your Steam port.
2. Open the port settings/tools menu.
3. Choose Wine Configuration, sometimes shown as WineCfg.
4. Open the Libraries tab.
5. Under New override for library, type:

​

winhttp 

1. Click Add.
2. Check the list of existing overrides. It should show:

​

winhttp (native, builtin) 

1. Click Apply.
2. Click OK to close Wine Configuration.

Do not skip this override. It is the key configuration change for getting BepInEx working through the Porting Kit Wine bottle.

Step 6: Install mods and do the first boot

1. Open the Big Walk game folder again.
2. Open the BepInEx plugins folder:

​

BepInEx/plugins/ 

1. Copy your mod .dll files into that folder. For example:

​

Big Walk/BepInEx/plugins/YourMod.dll 

1. Launch Big Walk from Steam inside Porting Kit.
2. On the first launch, a console window should appear. BepInEx will generate the required IL2CPP interop assemblies using Cpp2IL / interop generation.
3. The first launch can take a while. Do not close the console while generation is running.
4. When interop generation finishes, the game should launch with mod support enabled.

Future launches should normally be faster because the interop assemblies have already been generated.

Troubleshooting

The console does not open or the mods do not load

Check the Wine override first. Open Wine Configuration again and verify that the Libraries tab contains:

winhttp (native, builtin) 

Also confirm that winhttp.dll, doorstop_config.ini, the BepInEx folder, and the dotnet folder are all directly beside Big Walk.exe.

The game crashes on boot

Make sure you installed and are launching Big Walk through the Porting Kit Metal/DXMT port:

Steambuild 32/64bit Metal 

Do not use a different Steam port for this setup. Also verify that you installed the Windows x64 IL2CPP BepInEx build, not Mono or ARM64.

A mod still does not appear in-game

• Confirm the mod file ends in .dll.
• Confirm it is inside BepInEx/plugins/, not just inside BepInEx/.
• Check the first-launch console for a mod loading error.
• Make sure the mod supports the current Big Walk version and IL2CPP.
• Restart Big Walk after adding or changing a mod.

Where are the save files?

The Porting Kit copy of Big Walk uses the Windows/Wine environment’s save location, which is separate from a native Mac installation. The exact location can vary by Steam Cloud settings and the game’s save implementation.

Start by checking the Windows user profile inside the same Porting Kit C: drive, especially locations such as:

drive_c/users/<your-windows-user>/AppData/Local/ drive_c/users/<your-windows-user>/AppData/LocalLow/ drive_c/users/<your-windows-user>/AppData/Roaming/ 

If Big Walk uses Steam Cloud, allow Steam to synchronize the save and verify that the same Steam account is being used in both installations. Before replacing or transferring files, make a backup of both the native Mac save and the Wine save. Native Mac and Wine save formats or paths may not be interchangeable, so transfer saves only after confirming the relevant files for your installation.

Quick checklist

• [ ] Porting Kit is installed.
• [ ] The Steambuild 32/64bit Metal Steam port is installed.
• [ ] Steam is running inside Porting Kit’s Windows 10 64-bit environment.
• [ ] Big Walk is installed inside that Windows Steam library.
• [ ] BepInEx 6 Unity IL2CPP Windows x64 Build 733 or newer is extracted.
• [ ] BepInEx/, dotnet/, doorstop_config.ini, and winhttp.dll are next to Big Walk.exe.
• [ ] WineCfg has winhttp (native, builtin) configured.
• [ ] Mod DLLs are in BepInEx/plugins/.
• [ ] The first-launch interop generation has completed.

That’s it — Big Walk should now be running through Porting Kit with BepInEx and your mods enabled.