There is a simple version of planting lavender seeds and a complete version. Both are here, in that order.

A result that works but that you cannot explain will not survive the next change. Consistency beats optimisation until you are comfortable, and often after that too. A method that works for everyone is usually slower than one tuned to your situation, and worth it anyway. There is a point where further refinement stops being worth the time, and it arrives early.

Answer first, reasons after

Do the straightforward version first; it solves this for most people, and the detailed section exists for when it does not.

The straightforward version

People often blame the game when the actual cause is a setting they changed weeks ago. It is worth knowing which part of this the game actually enforces and which part is convention. Written notes beat memory when you come back to this in a month. The optimal approach and the reliable approach diverge more than people expect.

Anything presented as a hidden trick for planting lavender seeds is normally a step a popular guide left out. Anything marked optional really is optional, so skip it without guilt. A change that works but that you cannot repeat has not really solved anything.

  • Check which version you are on before trusting any specific numbers.
  • Check whether an update landed since you last played.
  • Note the exact point where things stop matching the guide.
  • Keep the original settings somewhere you can restore them from.
  • Verify the outcome rather than assuming it took effect.

When to stop optimising

Rushing the setup is the single most reliable way to spend longer overall. Details that seem cosmetic occasionally are not, which is why the order is specified. The simplest explanation that accounts for what you are seeing is usually the correct one.

The complicated explanation and the simple one usually describe the same thing at different zoom levels. Doing this without understanding it works fine until something changes, which it will.

Related things worth knowing

Understanding the reason behind a step lets you adapt it when your situation differs. If the explanation feels overcomplicated, it probably is — the working version is usually short. The useful answer is usually one sentence long, and everything else is the reasoning behind it. The community figured most of this out through repetition, and the pattern has held up well.

Where a guide and the game disagree, the game is right and the guide is old. Where a guide and the game disagree about planting lavender seeds, the game is right and the guide is old. Anything described as guaranteed is worth reading twice before you rely on it.

Getting a better result

The second time takes a fraction as long, which makes the first attempt worth doing carefully. The result is consistent once the inputs are, which is less obvious than it sounds. The advice that sounds too simple is usually the part that actually matters.

Where people usually trip up

  • Copying someone else's setup without checking that it fits your situation.
  • Assuming a step took effect without checking.
  • Making a permanent change to answer a question a reversible one would have settled.
  • Following the detailed method when the simple one would have done.

Quick answers

What should I do if I get stuck partway?

Note the exact step, then re-check the one before it. Almost every report of being stuck traces back to a skipped precondition.

What if it does not work for me?

Go back to the first step and confirm each assumption instead of retrying the last one. The failure is almost always earlier than it appears.

Where should I look if this does not cover my case?

The official notes for your version first, then a community thread from the same version. Both together beat either alone.

Come back to this if you hit the same wall on a different save; the shape of the problem rarely changes.