Currently, as evidenced by the te4log.txt, connectivity is checked at the end of zone creation - after all entities are resolved. Therefore I get piles upon piles of resolver entries in log only to find a "level unconnected" line later and another pile of resolvers for the next attempt... until it finally connects. Especially egregious if using cavern generator.
A better way to do so - and speed up dungeon generation noticeably in case of multiple tries - would be to check entrance to exit connectivity after terrain is generated and before generating all the other entities.
Check connectivity the moment the terrain is generated?
Moderator: Moderator
Re: Check connectivity the moment the terrain is generated?
DG, you have mail 
)
Also, tried and tested in Veins (mod.class.ZoneI *think* it makes the level generation a little bit faster, too (it took me 39 tries when testing and did not look slower than ~10 tries with old code).
The log was 107 KB for 39 tries while it would be 400 KB+ for ~10 tries with old code.
)