Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cyberpunk fixes for 2.5 #141

Merged
merged 3 commits into from
Apr 12, 2024
Merged

Conversation

ZashIn
Copy link
Contributor

@ZashIn ZashIn commented Feb 29, 2024

Fixes the following in MO 2.5+:

Thx @ junki for the issue reports

The default load order settings are a compromise between default Cyberpunk / mod behavior (load mods alphabetically), backwards compatibility (load mods top to bottom = lower prio wins) and MOs known behavior from Skyrim etc. (highest prio mod wins).

Details about the load order as draft for the wiki:

Load order

With an example mod list

modB (priority 1)  with archive/pc/mod/B.archive
modA (priority 2)  with archive/pc/mod/A.archive
modC (priority 3)  with archive/pc/mod/C.archive

In Cyberpunk the load order of all .archive files and REDmod folders is alphabetically, as named by mod authors.
The first loaded .archive file / mod modifying a game file wins a conflict in CP (in contrast to Skyrim, where esps can overwrite each other), i.e. A.archive wins over B.archive and C.archive (A > B > C).

A custom .archive load order can be specified with a file archive/pc/mod/modlist.txt, which can be generated optionally (setting enforce_archive_load_order = true) by MO in overwrite before game launch (changing load order to B > A > C).
For REDmod, MO passes the load order by default to the precompiler redmod.exe. See Settings below.

Note that the load order of multiple .archive files within a single mod is still always alphabetically, independent of the settings.

In contrast to that, direct file conflicts (same file name) are displayed directly in MOs mod list and here the highest priority always wins.

Settings:

Under Tools/Settings/Plugins/Cyberpunk 2077 Support Plugin:

  • skipStartScreen (default: false): Skips the "Breaching..." start screen on game launch (can also skip loading of GOG rewards)
  • enforce_archive_load_order (default: false): enforce MOs mod load order via generated overwrite/archive/pc/mod/modlist.txt
  • reverse_archive_load_order (default: false): reverse MOs load order in generated modlist.txt
    • false(default): first / lowest priority mod in MO wins a conflict (B > A > C)
    • true: last / highest priority mod in MO wins a conflict (C > A > B)
  • enforce_redmod_load_order (default: true): enforce MOs mod load order by generating overwrite/r6/cache/modded/MO_REDmod_load_order.txt, which is passed to redmod.exe before game launch.
  • reverse_redmod_load_order (default: false): reverse the generated redmod list.
  • ...

…oad_order

True = load last mod (highest prio) first, which wins a conflict in Cyberpunk.
By default (False), first one (lowest prio) is loaded first
(not reversed in archive/pc/mod/modlist.txt).

Makes fix ModOrganizer2#132 optional for backwards compatibility.
@ZashIn ZashIn changed the title Fix for cyberpunk: remove debug return Cyberpunk fixes for 2.5 Mar 2, 2024
@Holt59 Holt59 merged commit 5e21de8 into ModOrganizer2:master Apr 12, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants