Level 1 can't be finished sometimes

[Vagrant]

As you can see in the gif, bottom planet can't be reached. I suppose the random mission generator misplaced one of the big planet. 

I played this mission more than 10 times, and that was the first anomaly.

I have the updated version of Dyson, wich is offered on your website.

[megagoten]

But it's only level one

[Alex]

Yeah this is a really annoying bug. I'm hoping to find a way to squash it so it will never come back Got an idea or two up my sleeve. It's no good just leaving it like it is, even though it can be fixed in data.

Sorry, for now just play again I guess

[Moonlight]

hmmm, maybe generate the planet's stats first, then take an average of the ranges and set max asteroid distance from neighbor to that, and then generate the field? Wouldn't eliminate it but it would make it much less likely.

[Alex]

At the moment if an asteroid has no other asteroids connecting to it it expands its sending radius so that at least one can send. However, This can still lead to islands in the pathfinding map. So that needs to be fixed too. I'm also not sure when I put in the former fix - single asteroids like that should mesh in with the network somewhere. I guess it's either not working or not present in 1.20. CALL YOURSELF A PROFESSIONAL ALEX

[Rudolf]

I think I simply put the maxasteroidneighbourdistance too low on that level, up it to 6000 and it should be ok?
    <dir name="MAXASTEROIDNEIGHBOURDIST" type="int" value="6000" />

[Vanger]

Well, I never had a separated asteroid on Level 1 in 1.20, but my wife once stuck with half of the belt unreachable.

[Alex]

Yeah there are two bugs here really, and one is kinda hard to fix without changing the code. Next release should see it done