BlogNomic: The First Dynasty of Desertfrog

This feels like we’re incentivizing fishing the “regular” Cells disproportionately. You can already get Catches from them, so why add more? The idea is to entice people to move around and spend Energy. Otherwise people will just circle near the Judge’s Hut.

but that’s the thing. right now you can hang out and fish near shore and there really isn’t a huge advantage to go out to the ocean. but the buildup for the stuff near shore would be low, so you’d suddenly get more of a reason to move around to other spots on the map

I think this will actually have the opposite of the intended effect. Under the current rules, the ocean is roughly twice as good as being near the shore, so if you spend energy to get there, it eventually starts being worth it as you spend more and more time there.

In contrast, under the new rules, the near-shore spaces will build up at an equal rate to the ocean so it’ll eventually just have value to just go and collect some of those rather than trekking all the way over to the ocean.

Sure, the ocean will improve just as fast as the near-shore, but as a ratio, the near-shore will look better and better.

It’s interesting but I think there are better ways to entice people to go all the way to the Ocean. 

By the way, I’m still not opposed to changing the random Catches to flat values, or if you want to combine this Proposal idea with changing the random Catches, I’d be ok with that. Maybe remove the Fished and Unfished parts, remove the random Catches from the existing rules, and just have flat “baseline” values with Buildups every Disturbance, where the Ocean gets a higher baseline and slightly more Buildup, and the Disturbance is just a large increase in the Baseline of the Cell that it’s in.

@SignularByte the ocean improves at double the rate of the near-shore. So a place that hasn’t been fished at in X rounds will give you ~X+3 catches near shore and ~2X+5 catches on the ocean. So actually, ration will improve (as it’ll move closer to 2, when right now its only 1.66)

on this specific implementation, but I like the idea. I will propose an alternative.