Plowed tiles spreads like other biomes.

[ricky]

While yeah plowing tiles is tedium, and while yeah muh realism, having plowed tiles act as these static objects isn't reasonable either.

Static fields basically negate any farming technology expansion beyond one metal plow and a naked alt. Horse driven plows could be a thing, etc.

[MagicManICT]

Horse driven plows could be a thing, etc.

Yeah, why don't we have this already?

[sMartins]

Was this intended? This farm plot was on claimed land, and your bug fix comment suggested that this would only happen if it were unclaimed.

Hopefully fixed the long-standing bug by which plowed tiles would sometimes spread. This means, instead, that foliage tiles will now spread over plowed land. It may, thus, be a good idea to pave around your unclaimed fields.

Terrain decay happens regardless of claim. I was misinformed. Yes, it was intended. Corrected patch note.

Yeah for me it's even worse now lol ... can you make that this doesn't happen on claimed land at least?

I'll be honest, I wish you could have just made a solution where neither happened, I didn't want to have to pave in all my crop areas, I liked having a natural look to it.
Maybe introduce hedgerows and the spread of the biome stops on either side?

Same thing ... I was asking to solve this to not have paved tiles, but now is even worse ... and paving would be mandatory.
My crops are slowly vanishing ....
P.S. Wait maybe we can use grass to stop the spreading ... I'll test it ...

[MagicManICT]

Last time I looked at the fields across the road from my house when they were left fallow for the year, they reverted back to grasslands pretty fast. Weeds and windblown things first, grasses and other plants that propagate by runners by the end of the summer. So realistic? Yeah. Practical as a game mechanic? I'd rather not have to replow, but whatever. I'm assuming this creeps from the outside in, so no need to replow the entire field between plantings like in legacy.

[Granger]

Simply 'wall' the fields in with something that dosn't spread (pavement) and you should be good.

Thanks @devs for fixing this.

[sMartins]

Last time I looked at the fields across the road from my house when they were left fallow for the year, they reverted back to grasslands pretty fast. Weeds and windblown things first, grasses and other plants that propagate by runners by the end of the summer. So realistic? Yeah. Practical as a game mechanic? I'd rather not have to replow, but whatever. I'm assuming this creeps from the outside in, so no need to replow the entire field between plantings like in legacy.

Yeah, but I mean, we have the claim ... the claim mechanics should mean that you are active in the world and you are taking care of your stuff .... so makes sense that they spread without a claim, but once you have one ( and you keep it active) all the decay related stuff and boring maintance should be gone.
Clearly devs have some problems with spreading biomes priorities and claim ... that probably has something in it that make more difficult than decay.
Tbh at this point it was better before, cause now there is no way to keep your crops without horrible paving ground around.

[Granger]

it was better before

No, it wasn't: Artificial biomes spreading on their own was breaking suspension of disbelief.

[sMartins]

it was better before

No, it wasn't: Artificial biomes spreading on their own was breaking suspension of disbelief.

Yeah, that's true ... but in practice was better, I mean was possible to have crops without paving ... you just needed to wait months before plowing ... waiting for all the decay hits where you flattened the land. Now we can only have paved crops that ìs not optimal too, I'd say, with your suspension of disbelief thingy.

[MagicManICT]

Think of it as a manicured garden such as you'd find at a rich palatial manor instead of random farm in the middle of nowhere, and paving feels perfectly natural.

[Cajoes]

As this bug has finally been resolved (and I will admit I am curious what exactly was causing it since nothing in the code allegedly indicated it initially according to devs), and the bug reporting forum is not the place for discussing feature implementations and changes (thats what critique and ideas are for) I ask for the thread to be closed, locked and possibly dropped into the gimmungagap for good measure.