I tested the updates by Sagap, and while they're nice (sort of), There is still no proper addition concerning the herostat setup.
I understand that there is a more advanced version planned. For this version or for ideas to work on, here some suggestions:
Menulocation.cfg setup with the help of OHS*: Call each hero in the herostat.cfg and ask for a user-input for the menu location.
Somehow, the user should know when the limit for a stage (23/27/36/50) is reached.
It would be cool if we also can skip a hero, so we don't have to limit herostat.cfg to (50) heroes.
It would be awesome if skipped heroes are reflected in menulocation.cfg, like this:
or like this:
Basically each hero from herostat.cfg (even if unused, because there are too many heroes in it) will have his/her line in menulocation.cfg
This allows us to re-build herostat.engb with just a double-click next time.
Add support to switch out heroes: In a similar interactive mode, ask for a user-input to select a currently "installed" hero.
The current "installed" heroes would be read from the menulocation.cfg. The user can select the hero by typing it's menu location number. OHS would then list all heroes from herostat.cfg with a number according to their location in herostat.cfg (01 top, 02 second, etc). The user can select the hero by typing it's number. Menulocation.cfg would then be updated by removing the number from the first input and then adding it to the new hero's line.
The current use with menulocation.cfg and herostat.cfg should be kept in any case, because it allows us to use versions for different mod stages of the game and to save roster setups.
*What I miss in OpenHeroSelect, is a userfriendly menulocation setup. Doesn't matter if with a program (even original Hero Select with GUI) or manually in the cfg-files with notepad (or notepad++ or whatever). It takes a while and you don't want to set it up too often. You can save it to use again. BUT, you can just as well set up a herostat.engb. This can also be saved for some custom rosters, no real difference, and you don't even have to compile or decompile anything. The only good thing about it is that you can edit the herostat entry in herostat.cfg and the herostat.engb will be updated with the next build with OHS. But even then, I'm currently faster with manually decompile/edit/re-compile herostat.engb.
I made some brainstorming here
. Basically, I put out the thought of combining HeroSelect with stage selection, because it depends on the stage, how many heroes can be selected. The stage files would have to be part of the setup, either coming with the HeroSelect program or installed already. Preview files of stages are available for most (I think Outsider has collected some empty stage previews too). So it would be cool if there was ever a HeroSelect with GUI again, if it had stage previews with a mask of the hero locations (numbers).