Thanks. So by default multiplayer is disabled n more recent versions of uRTS since Unity is deprecating UNET. If you using older versions you should be able to get version where multiplayer is still not disabled by default. If you seeing #if you can add scripting define symbols in Player Settings and it should work.

Hi there, so I pulled out multiplayer since Unity started to deprecate UNET. But the code is still in the recent version which you can make to work. The code is wrapped in ifdef comments which prevents compiler to see it. You can take a look at the older version of the asset where multiplayer works out of the box. In the most recent version you can pull UNET package from Package Manager and try putting things to work. If you get struggling with some particular points, feel free to ask on forums or email.

Well, at the moment 3D Sprites is a separate project. But you can use LODs in this toolkit which does quite a good work. In particularly if you gave directional lights (such as sun) LODs looks much better I would say. 3D Sprites are better for more uniform lighting. So you can take a look in demo scenes how LOD only models work and you can put your own models with LODs in a similar way. If you need some help with setting up your models or making LODs (i.e. with Blender) feel free to post on forums or email.

Should be documentation.pdf file in the Assets folder.

That's great to hear, you are welcome! I hope you will find the toolkit useful. Feel free also to join discussions on forums if something would be unclear or you would find bugs.

Thanks for a good review and also for testing the toolkit and providing a great feedback. I will definitely keep updating these areas. I am open minded for all further testing, feedback and feature requests, which keeps pushing the toolkit beyond its limits.

Thanks for a great review. Yes, I agree, one of the goals is to make the system more modular. This should start coming up in uRTS step by step when Unity's ECS will become stable and out of its preview state. For now it's a good idea to try disabling unwanted systems and hiding UIs. At some point in future it should be possible to delete most of unwanted systems from the scene without breaking it. Another principle I want to achieve is that users would be able to use uRTS with no need or very little coding. A good example is the economy system upgrade from last year. Battle and diplomacy AIs are the next good candidates for similar upgrades.

The reusing of code depends how you are reusing it. At the moment, different systems are dependent on each other, i.e. there are dependences between battle system, economy, diplomacy, AI and other ones. The rendering system (including LODs) is better separated example at the moment, and can be easier taken from the package for reuse. Other systems still need a bit more work to make the package more modular. At the moment I am practicing with the new Unity entity component system (ECS), which is inherently more modular. But it will take time to convert from the current approach to ECS based. Well, uRTS has been split from 3dSprites for quite a long time in order to reduce the package size. As a result you can get both. Bake 3dSprites and migrate them to uRTS. And then building the project, you don't need to remember to delete 3dSprites from uRTS. 3dSprites is also separate for those who don't need uRTS. So this is why in the description I mentioned just "3dSprites usage". As a result, uRTS is not an upgrade of 3dSprites and is a separate package.

Thanks. Yes, indeed the big advantage is that Toolkit is targeting towards large number of units and big scales. I was always thinking that it's other way around: that documentation is more advanced than videos. However, glad to hear that videos are useful.

Thanks for review. Yes, it's quite full of the features, but because of this there is a tradeoff between the number of features and the number of comments in the code. If I would spend more time to write up comments in the code, there would be less features implemented in the toolkit at the moment. Another thing is that at the moment code keeps changing quite often and comments would need to be rewritten. There are some classes and functions which didn't changed for a while and I agree that they deserves to get descriptions there, so keep tuned - they will be covered in the future releases. The best advice at the moment would be to try understanding the code, as it is relatively simple to read. There is also easy to search for variables, functions and classes if needed. If there are particular questions, it would be most welcome to discuss them on forums.