|
|
马上注册领取绝版勋章
您需要 登录 才可以下载或查看，没有帐号？立即注册
x
本帖最后由 泠叶 于 2021-11-1 19:49 编辑
作者:Tannin - MO2 Team
原址:https://www.nexusmods.com/
Mod 管理器 v2.4 已发布
支持分隔符折叠 也支持赛博朋克2077
机翻开始：安装最新 Visual C++ 2019 redists installed: https://aka.ms/vs/16/release/vc_redist.x64.exe
安装最新 .NET Framework 4.8 installed: https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net48-web-installer
Mod 组织者 2 是社区手中的一个开放项目，存在需要解决的问题以及可以添加的东西。MO2真的需要开发人员，如果你有编程技能和一些空闲时间，你可以真正提高改造社区的经验。
MO2 是非常先进和专门的贝塞斯达游戏。以下是支持的标题列表：
MO2 与更传统的模组管理器的区别在于不以任何方式修改"香草"游戏安装的想法。模组实际上并未安装在游戏文件夹中，而是将每个模组保存在各自的单独文件夹中。游戏 INI 配置文件不被触摸，而是 MO2 使用它自己的设置。
这样，模组只有在游戏从 MO2 开始时才会"活跃"，而如果游戏正常开始，则处于"香草"未模拟状态。
这对用户来说意味着启用/禁用模组实际上不需要任何文件传输，它可以立即
完成。模组"安装"的顺序也可以随时通过拖放进行修改，轻松更改哪些模组正在赢得文件冲突。
用户可以通过使用启用模组的不同配置文件单击来更改整个
设置。每个配置文件都有它自己的模组和插件的顺序， 甚至它自己的一组 Ini 文件， 不同于 MyGames 中保持不变的文件。
用户应使用集成的 INI 编辑器从 MO2 内部更改 INI
设置。如果他们需要一些其他程序来查看已安装的模组，他们可以将其添加到可执行列表中，然后从 MO2 开始，以便显示模组。
长版本：Mod 组织者 （MO） 是管理任意大小的模组集合的工具。
它是专门为喜欢尝试模组的人设计的，因此需要一种简单可靠的安装和卸载方式。
关于 MO2 的特殊事实是，它使用虚拟文件系统 （VFS），而不是实际将您的模组安装到游戏的数据文件夹
中。
MO2 使用它的 VFS 来欺骗游戏和其他程序，让他们以为模组安装在数据文件夹中，而它们实际上安装在自己分离的文件夹中。此 VFS 称为 USVFS（用户空间 VFS），它不同于 MO1 使用的 VFS，因为旧的 VFS 不支持 64 位程序，但它适用于类似的概念。
这意味着，只有通过MO2开始的程序将看到模组，而对于世界其他地方的游戏将保持香草。
VFS 的工作原理是连接目标程序（以及其中任何一个儿童过程），拦截访问文件和文件夹的所有请求，如果这些请求被引用到游戏数据文件夹，那么 USvfs 将进行干预并更改答案，以便它看起来像所有 Mods 文件都位于那里的程序（这种行为类似于某些类型的恶意软件的行为方式，这就是为什么某些防病毒软件会严重标记 USvfs 的原因）。
该系统允许处理不占用空间的特定虚拟文件夹，无需实际移动或复制任何文件即可与之交互。
usvfs 的实现是相当复杂和低水平，因为它去钩Windows API呼叫，保持一个共享的记录，通过挂钩过程中的变化，如添加的文件和删除的
实时。
Usvfs 是一个独立的库，旨在用于 MO2 以外的不同应用程序，因此它不包含 MO1 VFS（挂钩.dll）那样的 MO 特定代码。与Mod组织者
1：MO1和Mo2的差异可以被认为是不同的程序。
两者的主要区别在于 Mo1 使用的虚拟文件系统 （vfs） 不支持 64 位游戏。由于这个MO2有一个全新的vfs库（称为usvfs），这是支持64位程序以及。此库与程序的其余部分更加独立和独立，允许它甚至被其他程序潜在地使用。
另一个主要区别是，Mo1有一个特殊的系统来管理贝塞斯达档案馆（BSAs）。
Tannin（MO1 和 MO2 的创建者）决定不将此功能包含在 MO2 中，因为它颠覆了游戏实际加载档案的方式，导致依赖原始系统工作的工具和模组出现问题。除了使用新的虚拟化库实现该功能并使其与所有支持的游戏配合使用（Mo1 系统基于黑客攻击）之外，还具有纯粹的复杂性。
从他的经验和他与Mo1的所有问题，坦宁得出结论，使用一个特殊的系统BSA管理，没有遵循游戏做了什么是一个错误。
我们同意这一事实，在看到它造成的问题和妥协，该功能将需要。
我们正在努力恢复BSA（和所有其他类型的档案，如BA2）解析冲突
检测。这一次，它将遵循标准的游戏规则，即：
所有存档都按加载它们的插件顺序加载（在 Mo2 中，您无法禁用虚拟插件），之后所有松散的资产都加载在顶部。所以松散的资产不能被档案覆盖。
我们正在寻找最好的方法来直观地显示BSA的冲突，因为他们不再遵循左窗格顺序，而是右窗格。
我们将研究在未来不使用虚拟插件加载BSA的方法。
MO2当然得到社区的积极发展，而Mo1则没有，这意味着MO2中已经并将会有新的
功能。
在这里列出所有内容的时间太长，因此要更好地了解 Mo2 添加的所有内容，请您阅读 LOGS 选项卡下可以找到的更改日志。
以下是 MO2 当前支持的所有游戏的列表：
莫罗温德
遗忘（*）
辐射 3
辐射NV
两个荒地的故事（TTW）
天际
天际赛
天际 VR
辐射 4
辐射 4 VR
恩德拉尔（蒸汽版）
(*)要在 Mo2 中使用 OBSE，您需要按照以下步骤（github.com），否则您无法加载它。
Mo2 是一个 64 位应用程序，因此需要运行 64 位操作系统。
Mod 组织者 2 与绝大多数工具配合使用。这意味着他们可以在"虚拟"数据树上工作。
测试的应用程序包括：OBMM（尽管OMOD脚本可能无法正确编译）、FOMM、MLOX、LOOT、Wrye Bash、FNIS、xEdit、丁多洛德。。。和更多。
如果您发现应用程序不起作用，请向我们
报告。
扰 流 板：显示
问题，问题和建议应报告给开放的不和谐服务器：Mod组织器Dev[discord.gg]或 github 页面（如果它们不是用户特定的）：Github 问题页面 [github.com].
不和谐也是开发构建测试、错误报告和调查、讨论建议等的地方。除了开发人员之外，那里有很多用户愿意帮助人们解决问题，这样他们就不必亲自处理所有问题。
请不要在评论部分发布问题，因为监控这些问题对开发人员来说是非常低效和不方便的。不和谐和 GitHub 提供了更好、更有效的方法来跟踪问题并直接与有问题的用户进行试用。
原文开始：
OFFICIAL MOD ORGANIZER 2 GUIDE BY GAMERPOETS [youtube.com]
Mod Organizer 2 is a mod manager created by Tannin to support 64bit games like Skyrim Special Edition and Fallout 4 in addition to all the 32bit games MO1 already supported.
Tannin discontinued the project when he was hired by the Nexus team to develop their new Vortex mod manager.
MO2 was not completed and was left with many issues. LePresidente managed to fix it to a usable state by himself after SkyrimSE came out, adding support for it, and releasing v2.0.8.
The project took up speed again after a few more coders showed up in late 2017, and an incredible amount of work has been done!
Credits to Tannin, LePresidente, Silarn, erasmux, AL12, LostDragonist, isa, AnyOldName3, Holt59 and many others for the development.
A Special Thanks to all the testers of the discord server and everyone else involved for supporting the project!
MO2 Team:
Spoiler: Show
Mod Organizer v2.4.0 has been released, see the logs section for all the changes.
Mod Organizer 2 Full Changelog [github.com]
Attention! The new version requires the newest Visual C++ 2019 redists installed: https://aka.ms/vs/16/release/vc_redist.x64.exe
Attention! The new version requires .NET Framework 4.8 installed: https://dotnet.microsoft.com/dow ... net48-web-installer
Mod organizer 1 Legacy (thanks enpinion):
Mod Organizer 2 is an open project in the hands of the community, there are problems that need to be solved and things that could be added. MO2 really needs developers and if you have the programming skills and some free time you can really improve the experience of the modding community.
Short Version:
Mod Organizer 2 (MO2) is a feature rich Mod Manager.
MO2 is very advanced and specialized for Bethesda games. Here is the list of supported titles:
What distinguishes MO2 from more traditional mod managers is the idea of not modifying the "vanilla" game installation in any way. Mods are not actually installed in the game folder but instead are kept each in their own separate folders. The game INI configuration files are not touched and instead MO2 uses it's own set.
This way mods are only "active" if the game is started from MO2, while if it's started normally it will be in it's "vanilla" unmodded state.
What this means for users is that enabling/disabling mods doesn't actually require any file transfers, it can be done instantly. The order in which mods are "installed" can also be modified at any moment with drag & drop, easily changing which mods are winning file conflicts.
Users can change the entire setup with a couple of click by using different Profiles of enabled mods. Each profile has it's own order of mods and plugins and even it's own set of INI files, different from the ones in MyGames which are left untouched.
Users should change INI settings from within MO2 by using the integrated INI Editor. If they need some other program to also see the installed mods, they can add it to the list of executables and start it from MO2, so that the mods may be shown.
Long Version:
Mod Organizer (MO) is a tool for managing mod collections of arbitrary size. It is specifically designed for people who like to experiment with mods and thus need an easy and reliable way to install and uninstall them.
The special fact about MO2 is that it uses a Virtual File System (VFS) instead of actually installing your mods into the Data folder of the game.
MO2 uses it's VFS to trick the game and other programs into thinking that the mods are installed in the data folder while they are actually installed in their own separated folders. This VFS is called USVFS (User Space VFS), which is different from the VFS that MO1 used, since the old one did not support 64bit programs, but it works on a similar concept.
Which means that only programs started through MO2 will see the mods, while for the rest of the world the game will remain vanilla.
The VFS works by hooking the target program (and any of it's children processes), intercepting all the requests of accessing files and folders, if those are referred to the game Data folder then usvfs will intervene and change the answer so that it looks to the program like all the Mods files are located there as well (this kind of behavior is similar to how some types of malware behave and that is why some Antivirus will flag usvfs badly).
This system allows for a process specific virtual folder that does not take up space and can be interacted with without having to actually move or copy any files.
The implementation of usvfs is quite complex and low level as it goes and hooks Windows API calls, keeping a shared record across hooked process of the changes such as added files and deleted ones in real time.
Usvfs is a standalone library that is meant to be usable in different applications other than MO2, as such it does not contain MO specific code like the MO1 VFS did (hook.dll).
Differences with Mod Organizer 1:
MO1 and Mo2 can be considered different programs. The main difference between the two is that the virtual file system (vfs) used by Mo1 does did not support 64bit games. Because of this MO2 has a completely new vfs library (called usvfs) that was made to support 64bit programs as well. This library is more separate and independent from the rest of the program allowing for it to be potentially used even by other programs.
Another major difference is that Mo1 had a special system to manage Bethesda Archives (BSAs).
Tannin (the creator of both MO1 and MO2) decided to not include this feature in MO2 for the fact that it subverted how the the game actually loaded the Archives causing problems with tools and mods that relied on the original system to work. That in addition to the sheer complexity of implementing the feature with the new virtualization library and making it work with all the supported games (the Mo1 system was based on a hack).
From his experience and all the problems he had with Mo1, Tannin came to the conclusion that using a special system for BSA management that did not follow what the game did was a mistake.
We agree on that fact, having seen the problems it caused and compromises that the feature would have required.
We are working though in restoring BSA (and all other typs of Archives like BA2) parsing for conflict detection. This time it will follow the standard game rules, which are:
All Archives are loaded in the order of the plugins loading them (in Mo2 you can't disable dummy plugins), and after that all loose assets are loaded on top. So loose assets can't be overwritten by archives.
We are looking for the best ways to visually show the conflicts of BSAs as they don't follow left pane order anymore, but right pane instead.
We will be looking into ways to not use dummy plugins to load BSAs in the future.
MO2 is of course receiving active development from the community while Mo1 does not, which means that there are and will be new features in MO2.
Listing everything here would be too long so to have a better idea of all the things that Mo2 adds you are invited to read the Changelogs that you can find under the LOGS tab.
Here is the list of all the games currently supported by MO2:
Morrowind
Oblivion(*)
Fallout 3
Fallout NV
Tale of Two Wastelands (TTW)
Skyrim
Skyrim SE
Skyrim VR
Fallout 4
Fallout 4 VR
Enderal (Steam Edition)
(*)To use OBSE with Mo2 you need to follow these steps [github.com]as otherwise you can't load it.
Mo2 is a 64bit application and as such it requires a 64bit operating system to run.
Mod Organizer 2 works with the vast majority of tools. What this means is that they can be made to work on the "virtual" data tree.
Among the tested applications are: OBMM (though OMOD scripts may not compile properly), FOMM, MLOX, LOOT, Wrye Bash, FNIS, xEdit, DynDOLOD... and many more.
If you find an application that does not work, please report it to us.
Spoiler: Show
Issues, problems and suggestions should be reported to the open discord server: ModOrganizerDevs [discord.gg] or to the github page (in case they are not user specific): Github issues page [github.com].
Discord is also where dev builds are tested, bugs are reported and investigated, suggestions are discussed etc. There is a good number of users there willing to help people with issues in addition to the Developers, so that they don't have to handle everything personally.
Please don't post issues in the comment section, as monitoring them would be highly inefficient and inconvenient for the developers. Discord and GitHub offer much better and efficient ways to keep track of issues and debug directly with the users that have the problem.
下载
请注意,我发的这个程序是官方的升级程序(用法放到原mo2根目录，启动即可无缝升级，如果初次安装直接启动也行)
|
评分
-
查看全部评分
|
[复制链接]
发表于 2021-2-27 22:06:00
变色卡
千斤顶
