Field pests

[pruby]

Add some pests to fields to make harvesting a little more chaotic. On breaking any RB-controlled crops, a probability can be set (based on the type of crop) for it to spawn a field pest - a seriously weakened silverfish. If a player broke the block, it spawns targeting them. This pull sets the chance at 1/1000 by default.

This is intended to make bulk-farming harder to bot by introducing a tiny chance of spawning slow, weak, minimum health silverfish. A normal player can easily deal with these pests with a single punch, but a bot can only do so by breaching the rules and reacting to the pest.

Hoping the days of trivial bot farming can end...

[ttk2]

this is a really cool idea, I don't think I will have any trouble merging
it, but while we are working on this can we please get a fix for things not
growing right? people continue to complain about it (of course no one will
make an issue)

On Sun, Mar 30, 2014 at 10:55 PM, Tim Goddard notifications@github.comwrote:

Add some pests to fields to make harvesting a little more chaotic. On
breaking any RB-controlled crops, a probability can be set (based on the
type of crop) for it to spawn a field pest - a seriously weakened
silverfish. If a player broke the block, it spawns targeting them. This
pull sets the chance at 1/1000 by default.

This is intended to make bulk-farming harder to bot by introducing a tiny
chance of spawning slow, weak, minimum health silverfish. A normal player
can easily deal with these pests with a single punch, but a bot can only do
so by breaching the rules and reacting to the pest.

Hoping the days of trivial bot farming can end...

You can merge this Pull Request by running

git pull https://github.com/pruby/RealisticBiomes field_pests

Or view, comment on, or merge it at:

#10
Commit Summary

• Add chance of uncovering field pests on breaking crops
• 1/1000 probability of spawning field pests on breaking crops

File Changes

• M config.ymlhttps://github.com/Field pests #10/files#diff-0(1)
• M src/com/untamedears/realisticbiomes/GrowthConfig.javahttps://github.com/Field pests #10/files#diff-1(13)
• M src/com/untamedears/realisticbiomes/RealisticBiomes.javahttps://github.com/Field pests #10/files#diff-2(2)
• A
  src/com/untamedears/realisticbiomes/listener/FieldPestListener.javahttps://github.com/Field pests #10/files#diff-3(46)

Patch Links:

• https://github.com/ttk2/RealisticBiomes/pull/10.patch
• https://github.com/ttk2/RealisticBiomes/pull/10.diff

Reply to this email directly or view it on GitHubhttps://github.com//pull/10
.

[pruby]

Have heard people talking about that. What I believe is happening is that:

• RB grows plants when they have a natural grow update, or when loading the chunk.
• We've just made RB chunks not get unloaded, which means the latter can only happen once per day.
• This leaves the plant growth as the only mechanism.

Solution will be to add a check to grow all plants on chunk load, even if the RB data is already loaded - will take a look a little later today.

[ttk2]

sounds good to me.

From the general opinion on the sub it seems people think that this would
just make botters redesign their farms rather than stop botting at all.

On Mon, Mar 31, 2014 at 2:07 PM, Tim Goddard notifications@github.comwrote:

Have heard people talking about that. What I believe is happening is that:

• RB grows plants when they have a natural grow update, or when
  loading the chunk.
• We've just made RB chunks not get unloaded, which means the latter
  can only happen once per day.
• This leaves the plant growth as the only mechanism.

Solution will be to add a check to grow all plants on chunk load, even if
the RB data is already loaded - will take a look a little later today.

Reply to this email directly or view it on GitHubhttps://github.com//pull/10#issuecomment-39128269
.

[pruby]

Yes, will just force people to produce different designs, and then require more effort than the trivial case. I've had other people suggesting pesticides and such as counter-investments, but would be neat to see whether people come up with simpler emergent solutions.