Fixes conflict with the Fertile Fields patch. Also solves PR #158#163
Open
jptrrs wants to merge 1 commit into
Open
Fixes conflict with the Fertile Fields patch. Also solves PR #158#163jptrrs wants to merge 1 commit into
jptrrs wants to merge 1 commit into
Conversation
Jolanda5
approved these changes
Oct 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As others have pointed out, there's a small conflict with Fertile Fields because the mods patch the same method, but FF goes first and deletes the object you're trying to get the Map property from. It causes an error when a pawn completes the construction job and also results in a momentary stutter for that pawn. The game is able to recover from it and nothing is really lost (in game terms), but multiply that stutter by the amount of times one needs to fertilize their fields and you get a significant impact! This is a one-line solution that simply ensures your patch runs before theirs.