Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
In my case i hide the recipe when the "newer/cheaper" one is researched. While this might be a more specific problem to what i'm doing i was
wondering if you'd implement the ingredient check aswell, its as simple as replacing "return true;" in the method AreRecipesDuplicate() with:
HashSet<IngredientCount> usersA = new HashSet<IngredientCount>(recipeA.ingredients);
HashSet<IngredientCount> usersB = new HashSet<IngredientCount>(recipeB.ingredients);
return usersA.SetEquals(usersB);
If not then i can manually harmony patch it myself just fine, just wanted to check in here first.
Or a DefModExtension to be able to selectively ignore certain recipes from being deleted
– https://steamcommunity.com/workshop/discussions/18446744073709551615/600785448933028183/?appid=294100
(ai translate) :p