sweet235

This is the point where someone should tell the story of how we got here. Let me try. 1. We used to have seperate navmesh files for each class. 2....

> What is the lesson to be learned? I am not sure if I am competent to tell that story. But notice how well we did the automatic navmesh generation,...

Am I facing a rogue maintainer?

This is still required. Here is an example map to test whether it works in your branch: https://users.unvanquished.net/~sweet/pkg/map-voxelhill_1.dpk. Use this file `maps/voxelhill-builderupg.navcon`: ``` navcon 3 296 266 1920 216 10...

Here is a screenshot of the level4 navmesh at this place:  And here is the level0 navmesh:  Notice how the level0 navmesh ends at the upper right corner...

> Is this an artifact of the stair size? is this something that happens in all maps with stairs? I have no idea about the exact cause. But I am...

In `nav.cpp`, there is ``` d_->tcparams.maxTiles = d_->tw * d_->th * EXPECTED_LAYERS_PER_TILE; ``` Multiplying this by 4 seems to solve these problems. What is the proper value?

The `action equip` tries to do that, but it seems this stopped to work at some time. But we can specify which armour to buy explicitely, as I found out....

> there are 3 other cases of buy( WP_BUILD ) And a 4th case: a bot spawns with the ckit. `built.bt` is just a minimal example file right now, we...

Here is your essay: These BT instructions used to make a bot buy armour and ckit: ``` decorator return( STATUS_SUCCESS ) { action equip } action buy( WP_HBUILD ) ```...