u/RepresentativeNo42

https://github.com/oliveryasuna/ink-frame

Ink's own box borders are fine for a single box. Put two of them next to each other and the seam between them comes out as ││, two parallel lines instead of one shared edge. That's because a box border is one unbroken line and there's nowhere to hang a ┬ or a ┼ part-way along it. ink-frame sidesteps that by painting every border into a single character grid and resolving each cell once, so a spot where four boxes meet becomes a ┼ and a T-junction becomes a ┬, ┤, and so on, without you ever writing those characters yourself.

┌──────────────────────────────────────┐
│ Frame                                │
├─────────────┬────────────────────────┤
│ fixed width │ grow                   │
│             │ ┌────────────────────┐ │
│             │ │ nested box         │ │
│             │ └────────────────────┘ │
│             │                        │
│             ├────────────┬───────────┤
│             │ two grows  │ what is   │
├─────────────┤ share      │ left      │
│ a pane      │            │           │
├─────────────┴────────────┴───────────┤
│ junctions derived                    │
└──────────────────────────────────────┘

Background: I recently wrote this for a private project, and I thought it was useful enough to share. I hope you find it useful too!

https://github.com/oliveryasuna/ink-frame

Ink's own box borders are fine for a single box. Put two of them next to each other and the seam between them comes out as ││, two parallel lines instead of one shared edge. That's because a box border is one unbroken line and there's nowhere to hang a ┬ or a ┼ part-way along it. ink-frame sidesteps that by painting every border into a single character grid and resolving each cell once, so a spot where four boxes meet becomes a ┼ and a T-junction becomes a ┬, ┤, and so on, without you ever writing those characters yourself.

Background: I recently wrote this for a private project, and I thought it was useful enough to share. I hope you find it useful too!

A copy of this can be found on GitHub: https://github.com/oliveryasuna/Wabbajack-macOS.

Overview

This guide describes a hybrid approach to running a Wabbajack-installed Fallout 4 modlist on macOS using both Parallels (to run Wabbajack) and CrossOver (to play the game). Wabbajack cannot function in CrossOver due to its dependency on Microsoft Edge WebView2, and Mod Organizer 2 does not run reliably in an ARM build of Windows. The solution is to use each tool where it works.

This guide was tested with the following configuration:

• macOS: Tahoe 26.0
• Hardware: M4 MacBook Pro
• CrossOver: 26.1 (Wine 11.0)
• Modlist: Magnum Opus (Fallout 4)

Other Wabbajack modlists for Fallout 4 may work with this approach, but only Magnum Opus has been verified.

---

Prerequisites

• CrossOver (licensed)
• Parallels Desktop with a Windows 10 or 11 VM
• A licensed copy of Fallout 4 on Steam
• A Nexus Mods account (Premium recommended for automated downloads)
• Sufficient disk space for the modlist (Magnum Opus requires approximately 100 GB)

---

Part 1: Set Up the CrossOver Bottle

1. Open CrossOver and create a new bottle. Set the Windows version to Windows 10.
2. In the bottle's advanced graphics settings, select DXMT and ensure MSync is enabled.
3. Install Steam into the bottle using CrossOver's built-in installer.
4. Launch Steam inside the bottle, log in, and install Fallout 4.
5. Launch Fallout 4 once to allow it to download any required content (e.g., Anniversary Edition Creation Club files), then exit the game.
6. Open Wine Configuration for the bottle. Navigate to the Libraries tab. If concrt140 appears in the existing overrides list, select it and click Edit. If it does not appear, type concrt140 in the "New override for library" field and click Add, then select it and click Edit. Set the override to Native (Windows) — not "Native then Builtin." Click Apply, then OK.

---

Part 2: Set Up the Parallels VM

7. Install Windows in Parallels if you have not already done so.
8. Inside the VM, install Steam and log in.
9. Install Fallout 4 inside the VM.
10. Launch Fallout 4 once inside the VM to ensure it initializes correctly, then exit the game.

---

Part 3: Install the Modlist via Wabbajack

11. Inside the VM, download Wabbajack and place it in its own folder on the VM's local C: drive (e.g., C:\Wabbajack\).

12. Launch Wabbajack, log in to your Nexus Mods account, and install the desired modlist. Install the modlist to a location on the VM's local C: drive — not to the CrossOver bottle's drive, a shared macOS directory, or a network path. Wabbajack's extractors and BSA builders require local filesystem access to function correctly.

13. Once the installation is complete, copy the entire modlist folder from the VM to the CrossOver bottle's drive_c directory. The bottle's filesystem is located at:

    ~/Library/Application Support/CrossOver/Bottles/<bottle-name>/drive_c/
    

---

Part 4: Launch the Game

14. In CrossOver, use the Run Command feature for your bottle. Set the following environment variable before launching:

    QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu"
    

    Run ModOrganizer.exe from the modlist folder inside the bottle.

15. Inside Mod Organizer 2, select the modlist profile and open the Fallout 4 Launcher from the executables dropdown. Allow the launcher to detect and configure your graphics settings, then close the launcher.

16. Back in Mod Organizer 2, select F4SE from the executables dropdown and click Run.

17. Enjoy the game!

---

Troubleshooting

Mod Organizer 2 will not save executables, citing a missing "CK Output" mod

Some modlists configure the Creation Kit executable to expect a mod named "CK Output" in the mod list. If MO2 displays an error about this when editing executables, create an empty mod in MO2 named CK Output and enable it.

Game crashes with concrt140.dll / _TaskCollection errors

Ensure that the concrt140 DLL override is set to Native (Windows) in Wine Configuration, as described in step 6. The default Wine implementation of concrt140.dll contains unimplemented stubs for the Concurrency Runtime's _TaskCollection class, which will crash mods that depend on it (such as Buffout 4). Using Microsoft's native DLL resolves this. If concrt140.dll is not present in the bottle, see the troubleshooting entry below about the missing DLL.

concrt140.dll is not present in the bottle

If the bottle does not have concrt140.dll in its windows/system32 directory, install the Microsoft Visual C++ 2015-2022 Redistributable (x64) into the bottle. After installation, set the concrt140 DLL override to Native (Windows) as described in step 6.

Mod Organizer 2 crashes on launch with a Qt WebEngine error

Ensure the QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" environment variable is set when launching MO2, as described in step 14. MO2 uses Qt WebEngine for its internal browser panels, and the GPU-accelerated rendering path does not function correctly under Wine on Apple Silicon.

The Fallout 4 Launcher does not detect display resolutions

The launcher may fail to enumerate available resolutions under CrossOver. Edit Fallout4Prefs.ini directly. In MO2, this file is located at:

<modlist folder>/profiles/<profile name>/Fallout4Prefs.ini

Under [Display], set iSize W and iSize H to your desired resolution. For example, on a 14-inch MacBook Pro at the default Retina scaling:

iSize W=1792
iSize H=1120
bFull Screen=1

If fullscreen does not work, use borderless windowed mode instead:

bFull Screen=0
bBorderless=1

Screen flickering or visual artifacts during gameplay

Disable godrays. In the Fallout 4 launcher's graphics settings, set God Rays Quality to Off. Alternatively, if the modlist includes an INI setting for godrays (e.g., bVolumetricLightingEnable in Fallout4Prefs.ini), set it to 0.

Wabbajack fails with a 7z.exe path error in the VM

Wabbajack and its bundled tools must reside on the VM's local filesystem. If Wabbajack is installed on a shared macOS directory or network path, its child processes will fail to resolve UNC paths. Move Wabbajack.exe and its folder to the VM's local C: drive.

Viewing FPS in-game

The Steam FPS overlay does not render correctly under CrossOver — it appears as a black rectangle with no text. If the modlist includes HighFPSPhysicsFix (Magnum Opus does), you can use its built-in FPS counter instead. Edit HighFPSPhysicsFix.ini in Stock Game/Data/F4SE/Plugins/ and enable both EnableOSD and FPS. This will display the framerate on screen without relying on the Steam Overlay.

Uncap FPS

See https://github.com/LivelyDismay/magnum-opus/blob/main/faq.md#how-do-i-capuncap-my-fps.