0 of 0
File information
Created by
KellieAtTheLab -- Auska -- BladehawkeUploaded by
KellieAtTheLabVirus scan
Safe to use
Notifications
364 comments
The Detes
You can find the Main Jobs, Fixer Gigs, and Cyberdeck Upgrades in the Description.
Don't be a wilson, read the docs!
The Crew
Mostly Auska (@effs) and Ellie (@E1337Kat) this time around, but we're grateful for the help from both CDPR and Nexus Mods immediately after the REDmodding news dropped - special thanks to @Pickysaurus for even contributing code, and @rfuzzo for bearing with the endlessly meticulous questions about REDmodding implementation minutiae to make sure we'd be able to be 100% compatible! (Pretty sure we hit every remaining bug and quirk in the redmodding tools in this process :innocent:)
As always, thanks to all of you for your feedback, suggestions, bug reports, support, and in this case a little patience too!
Holo at us
Discord: https://discord.gg/redmodding (\#vortex-support on the CP2077 Modding Community server)
Github: https://github.com/E1337Kat/cyberpunk2077_ext_redux
Nexus: https://www.nexusmods.com/site/mods/196
The problem introduced by PL should no longer be an issue, but you may need to clean up your installation for an easier time: just Disable and Purge everything, run Mod Remover, and then update + re-enable mods.
Original message:
2.0 and Phantom Liberty both Introduce Problems with Redmods specifically.
If you're getting a crash right at the first splash screen after deploying from Vortex, you can try:
1. Copy all .bin files from r6/cache/ to r6/cache/modded/ and try again
2. If that didn't work, after deployment and 1. open r6/cache/modded/mods.json and change all mods to "deployedHash": 0 and "deployed": false
It should work from Vortex (use the run with mods enabled button, Dashboard > Tools if it's not visible), but on 2.0 the store launchers at least also work. Not sure about PL functionality yet.
Another alternative is converting everything to archivepcmods. This may be easier in the short term, until redmod and the launchers are fixed.
1. Any mods that were autoconverted, you can right click -> Reinstall (after turning autoconvert off)
2. Any mods that have an archivepcmod version, you can install that over the Redmod version
3. Any mods that only have a Redmod version, and only have archives (or tweaks when they work again), you need to wrap. This is a bit more advanced, but there shouldn't be many of these. Disable the mod first. Then download the mod manually and extract it. If it's just a single .archive, you can dragdrop that to Vortex (there's a dropdown area at the bottom of the mods view.) If there's lots of archives or something else, you need to fix it to correct paths yourself.
As usual, you can find additional help on the CP2077 Modding Community Discord or the Redmodding wiki which has a bunch of troubleshooting guidance.
Mods seem to get enabled/disabled fine.
Edit: After a second look to be sure, I don't get the choice to enable the settings and saves switches for Cyberpunk. They just aren't there. Totally defeats the purpose of different profiles.
They simply do not exist
although with manual installation everything works
does anyone know what the problem is?
Use case: while installing huge Collections, there can be more than 50 such prompts during the install process, which is quite annoying. Often users trigger the installation process and leave it running over night, only to see in the morning that the install stopped after 5 mods due to the fallback installer prompt.
+1
btw, how-to quick fix (monkeypatch): %appdata%/Vortex/plugins/Vortex Extension Update - Cyberpunk 2077 Vortex Support v0.11.1/index.js, open the file with something like vscode (any text redactor), find and replace function
from:
const promptUserToInstallOrCancel = async (api, title, explanation) => {
to:const dialogResponse = await api.showDialog(`question`, title, {
md: (0, util_functions_1.heredoc)(explanation),
}, [{ label: InstallChoices.Cancel }, { label: InstallChoices.Proceed }]);
const installDecision = dialogResponse.action === InstallChoices.Proceed
? installers_types_1.InstallDecision.UserWantsToProceed
: installers_types_1.InstallDecision.UserWantsToCancel;
return installDecision;
};
const promptUserToInstallOrCancel = async (api, title, explanation) => {And reload Vortex after that.return installers_types_1.InstallDecision.UserWantsToProceed;
};
note: do it for your own risk, works for me, may f*ck things for you. All what it doing - remove all dialogs and automatically answer "yes" for all questions.
and it seems installing it anyway doesn't work. i'm trying to get it work.
maybe should i run redmod deploy?
EDIT: after i run redmod deploy and launch the game with redmod enabled, it worked.