Римворлд ошибка модов

Автор: Ваше имя

Введение

RimWorld — увлекательная и популярная игра, предлагающая игрокам управлять колонией людей, выживающих на неизведанных планетах. Одной из самых привлекательных особенностей RimWorld является его модификационная система, которая позволяет игрокам настраивать и изменять игровой опыт. Однако, при использовании модов нередко возникают ошибки, которые могут негативно сказываться на игровом процессе. В этой статье мы представим подробное руководство по исправлению ошибок модов в RimWorld.

Шаг 1: Определение проблемного мода

Первым шагом в исправлении ошибки мода является определение мода, вызывающего проблемы. Обычно, когда игра выдает ошибку, в сообщении об ошибке указывается название мода, вызывающего проблему. Если это не так, вам потребуется провести некоторые дополнительные действия для выявления проблемного мода.

1. Отключите все моды: Запустите игру с отключенными всеми модами и проверьте, возникает ли ошибка. Если ошибка исчезает, проблемный мод находится среди включенных модификаций.
2. Включайте моды по одному: Включайте моды по одному и после включения каждого мода запускайте игру и проверяйте, возникает ли ошибка. Повторяйте этот процесс, пока не найдете мод, вызывающий проблему.

Шаг 2: Проверка обновлений

После определения проблемного мода, следующим шагом будет проверка наличия обновлений для этого мода. Даже самые популярные моды могут иметь ошибки, которые разработчики исправляют в последующих обновлениях.

1. Проверьте страницу мода в Steam Workshop или на другом ресурсе, где вы его скачали. Обычно, разработчики указывают на наличие новых обновлений и исправления ошибок.
2. Если обновления доступны, загрузите их и установите. Запустите игру и проверьте, исчезла ли ошибка.

Шаг 3: Конфликты между модами

Если обновления мода не помогли, следующим шагом будет проверка наличия конфликтов между модами. Некоторые моды могут быть несовместимыми, что может приводить к ошибкам.

1. Внимательно прочитайте описание и инструкции каждого мода, чтобы убедиться, что они не конфликтуют между собой.
2. Отключите все моды, кроме того, который вызывает ошибку. Запустите игру и проверьте, возникает ли ошибка. Если ошибка исчезает, значит, проблемное взаимодействие возникает между двумя или более модами.
3. Перезагрузите игру, включив по одному моду за раз и проверьте, вызывают ли они ошибку. Продолжайте это делать до тех пор, пока не обнаружите конкретные моды, создающие конфликт.

Шаг 4: Устранение конфликтов

После определения конфликтующих модов, вы можете предпринять следующие действия для устранения проблемы:

1. Проверьте наличие обновлений для конфликтующих модов. Разработчики могут уже выпустить исправления, которые устраняют конфликт.
2. Попробуйте найти альтернативные моды, которые предоставляют похожие функции, но не вызывают конфликт. Обратитесь к сообществу игры или форумам для получения рекомендаций о замене мода.
3. Если вы не можете найти альтернативу для мода, вызывающего конфликт, попробуйте связаться с разработчиком мода и сообщить о проблеме. Возможно, они смогут предложить решение к вопросу.

Заключение

Модификации в RimWorld добавляют уникальные возможности и новые варианты игрового опыта. Однако, иногда возникают ошибки модов, которые могут нарушить игровой процесс. В этой статье было представлено подробное руководство по исправлению ошибок модов в RimWorld. Надеемся, что эта информация поможет вам насладиться игрой без лишних проблем.

RimWorld Conflict Checker v0.0.0.9

Features

• Checks for the same nameDef defined in 2 or more mods
• Lists all core (game default) nameDef’s overwritten by mods
• Finds any DLL existing in 2 or more mods
• Identifies possibly corrupt or incomplete mods (partially implemented)
• Checks versions of all mods against the RimWorld version
• Lists mods load order also showing disabled mods

Instructions
Extract Zip to anywhere.
Run RCC.exe either from Windows or a command line.
When run it will open the UI for you to pick at least 2 paths (RimWorldWin.exe & Mod folder path).
The first 2 folders are required (Mod folder 1 is auto-calculated when you choose the RimWorldWin.exe folder — but it can be changed).
Mod Folder 2 is only needed for Steam users.

It can also be run from the command line with parameters:

Results & Output
All findings are reported to file RCC.txt in the same folder as RCC.exe.
Each check, or main function of the program is delimited by «============»‘s.
Be sure to scroll down RCC.txt, as there are checks all the way through the file.
(new in 0.0.0.3 is a list of mods and a count of the conflicts. Check RCC.txt for all the details).

Limitations

• Windows only (sorry!)
• Will trigger UAC request for bug submission

Bugs
NB: Uses opensource library NBug to submit crashes to a Mantis tracker so I can fix any issues.
Feel free to block it if you do not want the reports sent.
Please report bugs here, or on GitHub.
Bug List — Currently none that I know of

Todo
Check XML inheritance: http://ludeon.com/forums/index.php?topic=19499.0″
Check if CCL is compat with RimWorld.
Check if root, tag, defname are valid (by parsing core).
Check if a mod is valid — needs about.xml, at least one XML or dll.
Check if mod exists twice. a) based on folder name & b) based on About.xml name.
Check if a mod’s defname conflicts with another defname of the same mod.
Change output to tabbed tables in a Windows Form.

Source & License
Source: https://github.com/biship/RimworldConflictChecker
License: GPL 3.0 Please do not distribute without credit & without modification.

Versions
0.0.0.9 04/16/17 Better exception handling, fixed case-sensitive bugs, handles missing version.txt or modsconfig.xml
0.0.0.8 12/31/16 Logging for opening & parsing Version.txt, NBUG & Octokit updated
0.0.0.7 12/30/16 ModsConfig.xml picker, command line changes, option to also check all non-enabled mods
0.0.0.6 12/30/16 Tweaks and change. Internal release only
0.0.0.5 12/29/16 Fixed for A16. No longer checks conflicts for non-enabled mods. More bug fixes
0.0.0.4 09/09/16 This tool will now check and notify on updates for it. More info on results form. Loads of bug fixes!
0.0.0.3 09/05/16 Added basic mod conflict form, code cleanup, null checking & bug fixes.
0.0.0.2 09/01/16 Folder picker updates
0.0.0.1 08/31/16 Initial alpha release

---

Basic Troubleshooting Things You Should Do[edit]

«My game broke/crashed/the UI is gone/froze, what do I do?»

You should:

— Verify with Steam (if you use it to run Rimworld).

— Clear your configs (instructions below).

— Check your mod order (instructions also below).

— Make sure no mods updated since you last played, if a game that was running fine suddenly broke the next time you loaded it.

---

Basic Load Order Rules:[edit]

Mods must be loaded beneath any and all dependencies.

eg: most mods depend on Core to function and must load below it

Mods should not/cannot be loaded with other incompatible mods.

How do we know which mods are incompatible? Reading mod descriptions, asking people who know things, and trial/error

In the instance of multiple mods that change the same thing, whichever is loaded last will take precedent

There are some «ifs» and «buts» in this statement, but it’s largely true

Local Mods:[edit]

Windows:
C:\Program Files (x86)\Steam\steamapps\common\RimWorld\Mods

or
C:\Program Files (x86)\RimWorld\Mods

Mac OS X:
Right-click the RimWorld application and show package contents
cd Library/Application\ Support/Steam/steamapps/common/RimWorld

Linux:
~/.steam/steam/steamapps/common/Rimworld/Mods;

Config Files:[edit]

—RimWorld configuration files and most mod settings are kept in this folder, and removing them will reset all settings to default.

—«Clearing configs» refers to deletion of old/all configs in the aforementioned folder

—Old mod config files are not automatically removed and may cause errors.

—Save the «ModsConfig.xml» as this is your mod load order, and if you remove it you will lose your modded load order.
%appdata%\..\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Config

Steam Default Install Location:[edit]

C:\Program Files (x86)\Steam\steamapps\common

Steam Default Mod Install Folder:[edit]

C:\Program Files (x86)\Steam\steamapps\workshop\content\294100

Verify Game Files with Steam:[edit]

> Steam Library

> Right Click RimWorld

> Properties

> Local Files

> Verify Integrity of Game Files…

Change Game Version with Steam:[edit]

> Steam Library

> Right Click RimWorld

> Properties

> Betas

> «Select the beta you would like to opt into:»

Load Order:[edit]

Rimpy is a useful tool that works outside the game, to make it easier to sort your mods. It also has it’s own auto-sort function if you want to see if that will help your issue:

https://steamcommunity.com/sharedfiles/filedetails/?id=1847679158&searchtext=rimpy

There are also a few mod managers out there, both as mods and as external programs.

Another option for sorting your mods is to follow this guide here:

https://rwom.fandom.com/wiki/Mod_Order_Guide

---

An explanation of how this works code wise;

«Keep in mind that not all mod conflicts will be solved by shuffling load order around. Sometimes mods are just incompatible until the mod authors put in effort to fix their mods.

Sometimes mods will just be incompatible.

As with most things, the truth is a bit more fine-grained. It’s true that «Core, Mod 1, Mod 2, Mod 3» is the load order, and the last mod «wins», but the actual load order is a bit different.

— XML

— xpath

— C#

The game first loads all XML (defs, mostly) from Core, Mod 1, Mod 2, Mod 3

Then it applies all xpath patches from Mod 1, Mod 2, Mod 3

Then it loads the C# from Mod 1, Mod 2, Mod 3

Core doesn’t use xpath or load any C#, so they’re not in that list. The C# for RimWorld is already loaded by that point, roughly speaking.

So if Mod 3 overwrites something in XML, but Mod 2 overwrites it in xpath and Mod 1 overwrites it in C#, it’s Mod 1 that wins — even though Mod 3 and Mod 2 come after it in the load order.

There are a few things that matter with load order:

— Does the mod require a different mod? Examples of that are mods that require HugsLib, Proper Shotguns, Turret Extensions, Alien Races, JecsTools, whatever. If you are missing a dependency, you’ll notice: You get a nice red error saying something like
Could not find type named TurretExtensions.CompProperties_Upgradable from node <A lot of XML> and missing a dependency like that will put the entire game in a corrupted and unplayable state.

And then there is another insidious thing some XML mods do: overwrite (abstract) bases. For that, I refer you to https://github.com/RimWorld-CCL-Reborn/AllYourBase. This is something that’s still unfortunately very frequently done, and it can cause havoc.

The C# summary slightly diverts from the truth. It even depends on how they instantiate the mod; there are two or three possible hooks and they happen at different times. Most mods that mess about with Defs will all have to do it in the second or third hook.

There’s inherit from mod, which happens before Defs are loaded. Generally mods can’t screw around with Defs in there.

There’s the staticconstructoronstartup annotation which happens after Defs are loaded. This is where mods would screw around with Defs, for the most part.

Finally there’s Hugslibs’ ondefsloaded, which is exactly like a staticconstructoronstartup, but it runs after the staticconstructoronstartup utility is done.

and fwiw: that’s just the Defs side of the equation

I won’t even mention the harmony conflicts (which are way harder to detect) or runtime conflicts (which sometimes get logged, but not nearly always)

take the world edit mod: I can’t remember which page it was, but basically if you click next somewhere and from there on you get redirected to world edit’s version of whatever the next screen would’ve been.

There’s like.. almost zero chance of detecting that programmatically»

---

Common things people do that they should be doing differently[edit]

These are the opinions of one particular troubleshooting group, and not of the rest of the maintainers of this article. If you take offense, please direct your fury at the Unofficial Rimworld Discord server, thank you.

-Do not run out of date mods. This means mods that are for a different version of the game than you are running. The only exception is Allyourbase at this time.

-If asked to add and use Allyourbase, do NOT turn on Verbose Logging till you are asked to do so.

-Do not run two copies of the same mod. This causes things to break horribly.

-Do not use modpacks. They are almost always partially out of date, almost always partially broken, and you will be told to make your own list if you present them to a troubleshooter.
Also Samuel Streamer needs to either stop editing around all the dev commands they use, or they need to stop giving people the packs without FIXING them first.

-Do not come into a troubleshooting area with «Can someone help?» and nothing else. Do not even come into such an area with that and a log. Come with a description of your problem, AND a log, so that troubleshooters do not have to spend multiple minutes asking for a description of your problem.

-If a troubleshooter asks you to do something that does not ACTUALLY BREAK LAWS OR PUT YOU IN HARMS WAY, do it. Even if you did it already. You’re not being asked as a delaying tactic, or as a power trip; you are being asked to do that thing so that they can help you fix your game.

-If you come from modding Skyrim or Fallout and you are used to the LOOT filter: Guess what, Rimpy exists, it hasn’t had enough time to get to where LOOT is (though the devs are working on it). Use it.

-Always provide a Hugslog if possible. Yes, even if it has to come from the main menu. Yes, even if it has to come from a restart before the error occurs. It will STILL be useful. (Hugslogs are acquired by adding the Hugslib mod, and then either pressing Ctrl+F12 while in game, or navigating to the dev mode console window and hitting the green «Share Logs» button.)

-It’s (almost always) not Achtung or Rocketman.

   ~Both of these mods check what other mods are doing to try to make bugs easier to notice and fix. They are probably not the cause of whatever they catch.

-YOU NEED HARMONY. AND UNO.[edit]

I’ve been putting together a rather beefy modpack over the last couple days and keep running into mod conflicts that force rimworld to disable all active mods.

I was wondering if anyone had a good way to figure out which mods are conflicting with each other.

I’ve tried Fluffy’s mod manager, it doesn’t catch it.

I’ve tried the Rimworld conflict checker, still no clue.

I’ve scoured my mod list for duplicate functions and removed a bunch but still no luck.

The tracelog from Rimworld itself doesn’t really tell me anything either except that a lot of mods have missing textures.

I don’t really want to have someone tell me what the issue is, I more want to learn how to figure it out myself. I feel that sort of skill would be better in the long term.

That said, where should I look next?