Skip to content

SimGamerJen/FS25_CropControlOverride

BranchesTags

Repository files navigation

FS25 Crop Control Override

Version: 2.0.0
Game: Farming Simulator 25
Status: Stable release
Author: SimGamerJen, Hyper138

Crop Control Override is a per-save crop policy manager for Farming Simulator 25. It allows players to control which crops are permitted for the player, which crops NPC farmers may use, and whether NPC crop planting should be limited by field size.

The mod is designed for players who want tighter control over crop realism, map-specific crop suitability, roleplay save rules, NPC field behaviour, and cleanup of NPC fields that no longer match the active crop policy.

Current stable release

The current recommended release is:

v2.0.0 from the main branch.

Older alpha and beta releases are retained for history only.

Contents

What this mod does

Crop Control Override gives each savegame its own crop policy file. For every crop known to the mod, you can control:

Setting Purpose
Player Permitted Whether the crop is available to the player.
NPC Permitted Whether NPC farmers may use the crop.
Max Field Size Optional maximum field size for NPC use of that crop.
Reset NPC Fields Whether blocked NPC fields of that crop may be reset by the cleanup tools.

This allows you to create map-specific or region-specific crop rules without editing the map directly.

Examples:

  • Disable rice, cotton, sugarcane, or other crops unsuitable for a region.
  • Allow the player to use a crop but stop NPC farmers from planting it.
  • Allow NPC farmers to use a crop only on smaller fields.
  • Validate existing NPC fields after changing policy.
  • Reset or reseed NPC fields that no longer comply with the active rules.

Release highlights

Version 2.0.0 promotes the beta workflow to the stable release and includes the major validation and cleanup workflow update introduced during beta testing.

Key features:

  • FS25-style custom GUI.
  • Per-save XML configuration.
  • Native selector controls for editable rule values.
  • Crop table terminology aligned to the details pane:
    • Player: ON / OFF
    • NPC: Map Default / ON / OFF
    • Loaded: Yes / No
  • NOT LOADED crop visibility toggle.
  • Field-level blocked reset scope.
  • RESET MODE support:
    • CULTIVATED
    • RESEED SEASONAL
  • Seasonal reseed candidate detection using FS25 growth data.
  • GRASS lifecycle reseed support.
  • XML-configurable reseed candidate weights.
  • Weighted deterministic reseed variety.
  • Dry-run before confirm workflow.
  • Diagnostic console commands.

Installation

  1. Download the mod ZIP.
  2. Place the ZIP in your Farming Simulator 25 mods folder.
  3. Enable the mod in your savegame.
  4. Load the save.
  5. Open the Crop Control Override GUI with ALT+C.

Typical Windows mod folder:

Documents/My Games/FarmingSimulator2025/mods

Do not unzip the mod for normal gameplay use.

Opening the GUI

Default keybind:

ALT+C

The keybind can be changed in the Farming Simulator controls menu.

You can also open the GUI from the console:

ccoGui
CCO v2.0.0 all rules

Important concepts

Loaded crops

A crop can exist in the CCO rule list but not be loaded by the current map or mod stack.

The table shows this using the Loaded column:

Loaded Meaning
Yes The crop is currently loaded by the game/map/mod stack.
No The crop is in the CCO config but is not currently loaded.

The NOT LOADED visibility toggle lets you show or hide crops that are present in the XML but not currently active in the save.

Player policy vs NPC policy

Player and NPC permissions are separate.

Example:

Player NPC Meaning
ON Map Default Player can use the crop. NPC behaviour follows map/default behaviour.
ON OFF Player can use the crop. NPCs should not plant it.
OFF OFF Crop is disabled from player and NPC use.

Map Default

Map Default means CCO does not force a specific NPC permission for that crop. The crop follows the map/game/default behaviour unless another CCO rule, field-size rule, or reset workflow applies.

GUI overview

ALL RULES

Shows all configured crop rules.

Use this tab to select a crop and edit its policy in the details pane.

CCO v2.0.0 selected crop

DISABLED

Shows crops where Player Permitted is OFF.

SIZE LIMITED

Shows crops with an NPC Max Field Size greater than zero.

NPC DISABLED

Shows crops where NPC Permitted is OFF.

VALIDATION

Shows NPC fields that violate the active crop policy.

This is the most important tab when changing NPC rules or field-size limits.

CCO v2.0.0 validation blocked fields

SUMMARY

Shows the active configuration path, rule counts, and validation summary.

HELP

Shows in-game guidance.

Crop rule settings

When you select a crop, the right-hand details pane exposes editable settings.

Player Permitted

Values:

OFF / ON

Controls whether the crop is permitted for player use.

NPC Permitted

Values:

Map Default / ON / OFF

Controls whether NPC farmers may use the crop.

Max Field (ha)

Sets a maximum NPC field size for the crop.

  • 0 means no CCO size limit.
  • Any value above 0 limits NPC use to fields at or below that size.
  • The table displays both hectares and acres for readability.

Example:

5.0ha / 12.4ac

Reset NPC Fields

Values:

OFF / ON

Controls whether CCO cleanup tools may reset blocked NPC fields of this crop.

If this is OFF, blocked fields of that crop are not reset by the reset workflow.

Validation and blocked NPC fields

A blocked NPC field is an NPC-owned field that no longer complies with the active CCO rules.

Common causes:

  • The crop has been disabled.
  • NPC use has been disabled for the crop.
  • The crop has a Max Field limit and the field is too large.
  • The crop remains in the field after changing rules.

Validation checks existing NPC fields and reports fields that need attention.

Example validation reason:

field 6.81 ha > max 5.00 ha

The validation screen supports scoped cleanup, so you do not have to reset every blocked field at once.

Reset scopes include:

ALL
CROP: <crop>
FIELD: <field id> <crop>
CCO v2.0.0 reset scope

Reset modes

The Validation screen includes RESET MODE.

Available modes:

CULTIVATED
RESEED SEASONAL

CULTIVATED

Blocked NPC fields are cleared and reset to cultivated state.

This is the safest cleanup behaviour and matches the earlier reset workflow.

Dry-run example:

resetMode=CULTIVATED action=CULTIVATED reseedCandidate=NONE

RESEED SEASONAL

Blocked NPC fields are reset and then reseeded using a replacement crop selected by the seasonal candidate engine.

Dry-run example:

resetMode=RESEED SEASONAL action=RESEED_SEASONAL reseedCandidate=GRASS

If no suitable seasonal candidate is available, CCO falls back to cultivated reset.

Fallback example:

action=CULTIVATED_FALLBACK

If the weighted reseed variety chooses to leave a field cultivated, dry-run reports:

action=CULTIVATED_VARIETY
CCO v2.0.0 reset mode

RESEED SEASONAL and candidate selection

RESEED SEASONAL uses the current game period and crop growth data to find suitable replacement crops.

The seasonal check uses:

growthDataSeasonal.periods[currentPeriod].plantingAllowed

A crop must generally pass:

  • Crop is loaded.
  • Crop is seedable.
  • Crop is allowed by CCO player/NPC policy.
  • Crop passes Max Field limits.
  • Crop is seasonally plantable in the current period.
  • Crop is not in the special exclusion list.

Candidate categories

Candidate diagnostics classify crops as:

Category Meaning
mission Standard seasonal field/mission crop.
lifecycle Lifecycle crop allowed for reseed, currently GRASS.
blocked Not eligible as an automatic reseed candidate.

Example candidate output:

CANOLA OK category=mission reason=allowed seasonal=OK
GRASS  OK category=lifecycle reason=allowed seasonal=OK

Special exclusions

The following crop types are deliberately excluded from automatic reseed candidates for now:

GRAPE
OLIVE
POPLAR
MEADOW
OILSEEDRADISH
RICE
RICELONGGRAIN

These may require special handling and should not be injected into ordinary NPC field cleanup automatically.

Reseed weighting XML

CCO supports XML-configurable reseed weighting.

The default bundled config includes:

<settings>
    <reseedCandidateWeights seasonalMission="5" seasonalLifecycle="5" leaveCultivated="1"/>
</settings>

Meaning:

Attribute Purpose
seasonalMission Weight for normal seasonal mission crops, such as CANOLA.
seasonalLifecycle Weight for lifecycle crops, currently GRASS.
leaveCultivated Weight for leaving a reset field cultivated instead of reseeding it.

Values are clamped from 0 to 20.

Weighted selection is deterministic by field ID. This means the dry-run result should match the confirmed reset result.

Default weighting

<reseedCandidateWeights seasonalMission="5" seasonalLifecycle="5" leaveCultivated="1"/>

With CANOLA and GRASS both valid, the weighted pool is effectively:

CANOLA x5
GRASS x5
LEAVE_CULTIVATED x1

This creates a mostly reseeded map while occasionally leaving a field cultivated.

Clean map preset

Always reseed where possible:

<reseedCandidateWeights seasonalMission="5" seasonalLifecycle="5" leaveCultivated="0"/>

Rougher map preset

Leave more fields cultivated after reset:

<reseedCandidateWeights seasonalMission="4" seasonalLifecycle="4" leaveCultivated="2"/>

Prefer arable crops over grass

<reseedCandidateWeights seasonalMission="6" seasonalLifecycle="2" leaveCultivated="1"/>

Prefer grass/lifecycle recovery

<reseedCandidateWeights seasonalMission="3" seasonalLifecycle="6" leaveCultivated="1"/>

Configuration files

CCO uses a template/default config and per-save configs.

The active per-save config is stored under:

modSettings/FS25_CropControlOverride/saves/savegameXX.xml

The template/default config is stored under:

modSettings/FS25_CropControlOverride/config.xml

Per-save behaviour

When a savegame is loaded, CCO uses the per-save XML if it exists. If it does not exist, CCO creates one from the template config.

This prevents rules for one savegame from unexpectedly changing another savegame.

Save Defaults to config.xml

The GUI option SAVE DEFAULTS TO CONFIG.XML writes the current active rule set to the template config.

Existing per-save XML files are not overwritten.

Load Defaults

The GUI option LOAD DEFAULTS loads the template config into the active save config.

Use this carefully because it updates the active save’s CCO XML.

Recommended workflows

Change a crop rule safely

  1. Open the GUI with ALT+C.
  2. Go to ALL RULES.
  3. Select the crop.
  4. Change the desired settings in the details pane.
  5. Click APPLY.
  6. If validation blocks the change, review the warning.
  7. Use FORCE APPLY only if you intend to allow blocked fields temporarily.
  8. Go to VALIDATION to review affected NPC fields.

Reset blocked fields to cultivated

  1. Go to VALIDATION.
  2. Choose RESET SCOPE.
  3. Set RESET MODE to CULTIVATED.
  4. Run RESET BLOCKED DRY-RUN.
  5. Review the output.
  6. Click CONFIRM RESET.

Reseed blocked fields seasonally

  1. Go to VALIDATION.
  2. Choose RESET SCOPE.
  3. Set RESET MODE to RESEED SEASONAL.
  4. Run RESET BLOCKED DRY-RUN.
  5. Confirm the candidates look sensible.
  6. Click CONFIRM RESET.

Expected dry-run example:

field=24 action=RESEED_SEASONAL reseedCandidate=CANOLA
field=65 action=RESEED_SEASONAL reseedCandidate=GRASS
field=77 action=CULTIVATED_VARIETY reseedCandidate=NONE

Expected confirm example:

queued field 24 to reseeded crop CANOLA
queued field 65 to reseeded crop GRASS
queued field 77 to cultivated state

Console commands

GUI and status

ccoGui
ccoStatus
ccoWhichConfig
ccoReload
ccoHelp

Rule listing

ccoListRules [CROP]
ccoListConfigured [CROP]
ccoListDisabled
ccoListBlockedRules
ccoListLimited
ccoListUndiscovered

Validation and scanning

ccoValidateSave
ccoScanFields [CROP]
ccoScanBlocked [CROP]
ccoScanSummary

Reset commands

ccoResetBlocked dryrun
ccoResetBlocked
ccoResetNpcFields [CROP|all] [dryrun]

The GUI reset workflow is preferred for scoped reset and reseed mode control.

Candidate diagnostics

ccoListNpcCandidates <FIELD_ID>
ccoSeasonProbe [CROP]
ccoGrowthProbe [CROP]

Example:

ccoListNpcCandidates 87

Output may include:

CANOLA OK category=mission reason=allowed seasonal=OK
GRASS  OK category=lifecycle reason=allowed seasonal=OK

Crop flags and diagnostics

ccoListFlags [CROP]
ccoFindFruit <namePart>
ccoExplain <CROP>

Troubleshooting

ALT+C does not open the GUI

Check the game log for Lua errors.

If the mod fails to compile or load, the GUI cannot register.

Look for lines like:

Lua compiler error
CCO GUI: custom screen failed
CropControlOverrideMenu class is not available

The GUI opens but shows fallback console output

This usually means the XML GUI or GUI class failed to load.

Check:

  • The mod ZIP structure.
  • gui/CropControlOverrideMenu.xml.
  • scripts/gui/CropControlOverrideMenu.lua.
  • The game log for stack traces.

Changes apply to config.xml but not the save XML

The active target should normally be:

modSettings/FS25_CropControlOverride/saves/savegameXX.xml

Use:

ccoWhichConfig

to confirm which file is active.

A crop is not offered as a reseed candidate

Run:

ccoListNpcCandidates <FIELD_ID>

Reasons may include:

  • Crop is not loaded.
  • Crop is not seedable.
  • Crop is blocked by CCO policy.
  • Crop exceeds Max Field limit.
  • Crop is not seasonally plantable.
  • Crop is specially excluded.
  • Crop is valid but loses deterministic weighted selection.

GRASS is valid but not always selected

This is expected.

GRASS is a lifecycle candidate. It participates in weighted deterministic selection alongside seasonal mission crops.

Check the XML weights:

<reseedCandidateWeights seasonalMission="5" seasonalLifecycle="5" leaveCultivated="1"/>

Increase seasonalLifecycle if you want GRASS selected more often.

Dry-run and confirm do not match

This should not happen under normal conditions.

Possible causes:

  • The field state changed between dry-run and confirm.
  • Another mod changed the field.
  • The save was reloaded with different XML weights.
  • The crop candidate set changed.

Run dry-run again immediately before confirm.

Known limitations

  • RESEED SEASONAL only targets blocked NPC fields in the selected reset scope.
  • Player-owned fields are not reset by NPC cleanup.
  • Some crop types are excluded from automatic reseed because they may require special handling.
  • The GUI does not yet expose reseed weights directly; edit XML manually.
  • Console reset commands do not expose the full GUI reset-mode workflow.
  • Candidate weighting is category-based, not per-crop.
  • Seasonal logic depends on FS25 crop growth data being available for the loaded crop.
  • Modded crops may behave differently depending on how their fruit type data is defined.

Screenshot checklist

Use these markers to add screenshots later.

Suggested screenshots

  1. docs/screenshots/cco_all_rules.png

    • Main crop table on ALL RULES.

  2. docs/screenshots/cco_all_rules_selected.png

    • Crop selected, details pane visible.

  3. docs/screenshots/cco_not_loaded_toggle.png

    • NOT LOADED crops shown/hidden.

  4. docs/screenshots/cco_validation_blocked.png

    • VALIDATION tab with blocked fields.

  5. docs/screenshots/cco_reset_scope.png

    • RESET SCOPE button showing ALL / CROP / FIELD.

  6. docs/screenshots/cco_reset_mode.png

    • RESET MODE showing CULTIVATED / RESEED SEASONAL.

  7. docs/screenshots/cco_dry_run_reseed.png

    • Dry-run output with CANOLA / GRASS / CULTIVATED_VARIETY.

  8. docs/screenshots/cco_summary.png

    • SUMMARY tab.

  9. docs/screenshots/cco_help.png

    • HELP tab.

Markdown screenshot marker format

Use this pattern:

<!-- SCREENSHOT: short description -->
<!-- Suggested file: docs/screenshots/example.png -->
![Screenshot placeholder - description](docs/screenshots/example.png)

Changelog

2.0.0

  • Promoted the beta branch to the main stable release.
  • Added native selector controls.
  • Added NOT LOADED crop visibility toggle.
  • Added field-level reset scope.
  • Added RESET MODE.
  • Added RESEED SEASONAL.
  • Added seasonal reseed candidate detection.
  • Added GRASS lifecycle reseed candidate support.
  • Added XML-configurable reseed candidate weights.
  • Added CULTIVATED_VARIETY weighted pseudo-candidate.
  • Added deterministic weighted reseed selection.
  • Updated validation, dry-run, confirm, and diagnostic output.

Disclaimer

Use a backup save when making significant crop policy changes, resetting blocked NPC fields, or using reseed workflows. CCO changes active save configuration and can alter NPC field states when reset tools are confirmed.

About

Farming Simulator 25 mod that overrides crops available in-game

Resources

Readme
Activity

Stars

4 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases 11

2.0.0.0 Latest
Jun 4, 2026
+ 10 releases

Packages

 
 
 

Contributors

Languages