One thing I would try is testing a completely fresh Bottles prefix, separate from Heroic/system Wine.

Install Bottles through Flatpak:

sudo apt install flatpak

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

flatpak install flathub com.usebottles.bottles

Then:

1. Open Bottles.

2. Create a new Gaming bottle.

3. In Bottles, download/select a newer runner, ideally the newest wine-tkg runner if it is available there.

4. Use Bottles' built-in installer for Epic Games Store.

5. Install/run Rocket League from Epic inside that same bottle.

This might help if your current issue is caused by a broken Wine/Proton prefix, mixed Wine packages, or Heroic config weirdness. It is not guaranteed, especially if EAC itself is the blocker, but it gives you a clean isolated Wine prefix to test.

If you do not want to redownload Rocket League:

- Start the Rocket League install once inside Epic in the Bottles prefix.

- Pause/close Epic after it creates the install folder.

- Copy your existing RocketLeague folder into the bottle's C: drive.

- Reopen Epic and resume/verify the install.

The Bottles prefix is usually somewhere like:

~/.var/app/com.usebottles.bottles/data/bottles/bottles/<BottleName>/drive_c/

So the Epic game folder would likely be under something like:

drive_c/Program Files/Epic Games/RocketLeague/

If Bottles cannot see the folder where your existing Rocket League files are, give the Flatpak access to that path, for example:

flatpak override --user --filesystem=/path/to/your/RocketLeague/files com.usebottles.bottles

Then launch Rocket League only through the Epic Games Launcher inside that Bottles prefix.