Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Maybe you have a mod that adds some kind of verbose logging showing "add" overwritings as errors?
Maybe you remeber errors when working with arrays? I'll test this again and sorry if my poor sb logging experience caused you nuisance.
The add patch operation does cause a, albeit small and unremarkable, error when a pre-existing value exists which is why I added the test operand (especially since I know there will be idiots who see the error and believe it's the cause of a completely separate, unrelated problem.
It's useful when you have arrays or when you want to replace a value not knowing if the object exist but the original mod and its patches use this [{"op":"add","path":"/disableTimer","value":true}].
As you can see it directly add the object with a single bool value and json patching works so that every subsequent add simply replace the value without creating duplicates.
Adding the test operand simply "slows" -by a negligible amount, but still- the patching process.
There is no possible incompatibility this mod and the test operand use can solve IN THIS CASE, so you are safe to use the original mod and the already existing patches.
As a side note you were right to use it not knowing this, better safe than sorry.
Additionally, Frackin' Universe support when /s