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
I think this is RNG each month though so not sure whether you can make it stick, I've never tried it.
I was actually looking at that fields.xml file.
Here's a small snippet of my file:
I'm thinking you're right about the RNG with that "UNKNOWN" fruitType.
I have ~170 hrs or so in this save, so I don't want to create any potential game-breaking scenario, but I always back things up before tweaking.
In FS25, the fruit types file points to individual xml files for each crop in data/foliage and those have the data including useForFieldJob, So, mod maps would need copies of each crop that has useForFieldJob changed, plus a maps_fruitTypes.xml that points to the custom crops.
And you can edit fields.xml in the save to change the current state of any field. But you can also use gsSetFieldState in the dev console. They added an interface to the command for FS25 making it easy to pick the various options. If you stand in a field when you enter the command, the dialog opens with the current state of that field.