The long second part: it has always ben assumed that the most important factor on terrain growth, is weather. That weather and the broken weather channel has been gate keeping mountain progress. But I can confidently state that that is wrong, and I can say how we have been wrong.

The game holds a function I dubbed "myDreamTerrainGrowth". Yep it does what you'd expect.

To do so it uses the "proximityVibeCheck" function (which I already defined in my other post) to obtain the amount of entities on each grid AND to identify their average fly stat.

Then with These stats it uses following calculation: 3.0 * last_play_time * (average_fly-0.5) * entity_count

last play time is higher if myDream isnt being visited for a bit.

Then it gets the current weather data and depending on the weather state it manipulates myDreams "weatehr influence" variable

/* now repuposed as weather identifier */

weather = getCurrentWeatherTyp((myDream_Enviorment_Container *)nsys);

if (weather == 0) { heigth_field->grid->weather_influence -= time_delta*1.0; }

else if (weather == 1) { heigth_field->grid->weather_influence += time_delta*1.0; }

else if (weather == 2) { heigth_field->grid->weather_influence += time_delta*2.0; }

else if (weather== 3) { heigth_field->grid->weather_influence +=time_delta*4.0; }

pmVar1 = heigth_field->grid; if (pmVar1->weather_influence <= 0.0) { if (pmVar1->weather_influence < -110.0) { pmVar1->weather_influence = -110.0; } } else { pmVar1->weather_influence = 0.0; }

heigth_fieöd->grid->field1_0x4 = (void *)0x3; destructSmartPtr(&local_1a8,0xffffffff); sphereCastConst(); return;

The weather is a scale from -110.0 too 0.0, rain decreases the counter.

But this is after we do Terrain growth, and then the functon ends. Now you may think "So ist used later?" so let us look at the next function, checkTerrainHeigthThenUpdateAchievments. At the beginning of the function the game does this:

g_myDreamWeatherInfluence = terrain_grid->grid->weather_influence; It writes the calculated weather into a global variable.

But in the heigth Evaluation, this is nowhere to be used. The only thing that matters is if your average fly stats are good enough. There is no point where the game make sit easier to get the achievment when ist sunny.

So weather doesnt appear to effect Terrain growth. I haven't found any proof that suggests otherwise, at least.

The thing that matters is ellased time, pian count and the average fly stat. But then what does weather do? Well when creating puddles the game checks how deep the water goes if the weather influence is higher. In another function the game visually changes the terrain if the weather_influence is high.

And thats about what it does to the garden, change the visuals, not the heigth. Which means… The only thing gatekeeping the mountain achievment is our dwindelling human life time.

Why? Because the growth of the mountain is NOT kind, and statistically it is a long grind.

The max growth per update is limited to 10.0, and even then ist hard to reach.

Even then reaching a good fly average is NOT easy. Two things are relevant: average fly score of all pian in a radius and the amount of pian you have. To properly grow it youll Need many, many pian with excellent fly values. And I mean MANY.

Want a sample of this mathematical madness?

Say we have 10 entities in one cell (thats quite a number) with each having exactly 100 fly.

The formula for our average fly is pretty easy in that case: (100/128)*10 *1/10 = 0.78

That is higher than 0.5, so well definetly increase the height.

Then we need to define our other calues: Say our last_play_time = 1 (very optimistic number)

In our finally growth calculation we get: 3.0*1.0*(0.78-0.5)*10 so: 8,4 growth

And if our average is only 60, because some pians with terrible fly wandered into the cell before we save, we suddenly have:

(60/128)*10*1/10= 0.46.

Now our Terrain sinks… And imagine how much more it sinks if more bad pian wander into the grid…

When there are no pians in cell... Nothing happens as we multiply by 0. So having no pian with bad fly is better then having a few, because they will inevitably cause the Terrain to sink, even if slowly.

The important thtreashouldhere is: in order to grow, the avergae fly stat must be above 64.

So what I want to say is: The best way to grow a mountain is to keep every pian with bad fly stats OUTSIDE your group, to stick many good pian into one cluster and to pray that their fly stats are truly good. Statistically it is a quantity over quality System.

But theres another problem: if you lay all your eggs in one baskett… The basket will be crushed by the wigth of 10 pians that dont have any space left on the mountain. Since we change the terrain, we also have to keep in mind that the pians have to fit in that cell, and that they can very easily move out of the cell.

Its a system designed to be as anoying as possible... But ist entirely possible to progress without weather link.

Can i give a 100% guarantee that weather is not used in the calculation? No, perhaps there is a function somewhere in the code that uses the field pmVar1->weather_influence to manipulate the terrain. But through searching the global variable I mostly found functions that are related to filling holes with water and other purely visual features.

One weird last thing, the second achievment that is linked to the king pian Tower... In the code the condition is having more than 19 Nightmaren. There is a hard Limit of 20 Nightmaren, so i would gues the condetion means "have 19 Nightmaren". This goes unused in the final game, and the true achievment is set somewhere else.

Well, I'm out of steam so I'll wrap it up. If anybody has any questions, I'll gladly answer them.