Question on Honey Hex's ability to handle many actors

Hi!

I think your problem is much more complex than "honey or not honey"

The fact is that honey does not require a lot of processing power to display is definitevly an advantage but managing many simultaneus actors is challenging and its more of the techniques vs engine question. How would you manage pathfinding for all those actors? would you do something like implementation of A* features? (http://arongranberg.com/astar/) then again you want to have models which animate and all are lit and rendered? All those processes are heavy by itself and if you combine them with "many actors" it grows to something what usually requires experts on the field to do it correctly, and often custom engines!
For example animation could be shared by many actors if you could override this part, the same for grouping pathfinding and making core AI aspects which are done in one place. You need to remember as well that all Unity related stuff is done on one thread, so you need to push as much as you can into pure logic and then spread it to threads. Mabe even decide to do pathfinding rarely and then extrapolate or otherwise smoothen results? Mabe you can preplan movements? Also remember that you cannot do much about what is done on rendering if it have to be produced live but for example all old games used prederended characters and displayed spritesheets instead of animating it live.

This is only tip of the mountain and I wish you best luck if you really want to have simultaneus armies movement, it is definitevly great learning topic with every bit being a challenge

I wish you like honey as well as it uses some tricks of its own to acheve what it does, but sadly it will not help you (nor stop you) toward your target. I found it working faster than even simplest unity terrain for my purposes (about 30% better) so it might be good for those extra clock cycles but your usage might differ.