Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hello! I've checked out the demo and below is some commentary I made along the way. Overall - I enjoyed tinkering with the Ai and I see a lot of potential, so do not get discouraged by whatever you find below: 


(Disclaimer - I do not comment on UI and visuals as I assume them to be placeholderish unless I feel a UX issue. Also - I have a bias due to using Unity Behavior Designer)

  1. Currently, the tutorials provide a detailed description of what each button will do and open, but they do not show the actual screens they describe. Additionally, they go one after another without giving me a chance to engage with what they explain. 
  2. It is a bit hard to interact with the workshop. I purchased a turret, but I am not sure if it was purchased. I go to inventory - there is the turret, but I need to press a greyed-out equip button to actually see it. 
  3. I lack a progressive tutorial that walks me through buying different tank components and assembling them before going to the campaign. And that I need to first visit the AI editor before going to the campaign. 
  4. I do actually love the idea of AI editing. Loved it since Dragon Age: Origins. Gives a much stronger "Me - smart" feeling when it behaves as intended. 
  5. For the true-false, it actually took me quit some time to understand that it does not lead to true or false scenario. Instead what it does is it leads to "true", and if false - it leads back. So perhaps it can be presented in a bit more obvious manner. 
  6. The instructions for editing the AI seem clear. 
  7. "If Enemy" - does it mean seeing the target or seeing the target in range? Later on, I realized it takes into account the cone of vision and the vision range, but it took me a while to realize that, and it caused quite a bit of confusion.  
  8. Lead target - will predict enemy position. The value used - what is it? Seconds? Also - "using it under Fire". Does it mean that If i want to fire with predicting the lead action should "geographically" be positioned under the Fire action? I think typically there is a parallel node used for simultaneous actions. 
  9. It is a bit hard and scary to explore creating new nodes outside those already presented in the original tree. 
  10. It would be nice to be able to select multiple nodes to move them, similar to, for example, Unity Behavior Designer. And creating node on rmb so I do not have to search for from where I can create a node. 
  11. Ah, got it. So the conditions work a bit differently. They don't lead to true or false; they lead only to true, and if false, they go to a different action. Got it. 
  12. Campaign 1 mission 1 - not sure what would give me an edge in the fight from the AI logic standpoint, considering it is an empty field, and it results in just hp-dmg trading 
  13. Not clear how tanks select a target or how to make them prioritize targets 
  14. Overall, for FTUE I suggest a gradual unlock of different nodes as the campaign progresses, not to overwhelm the player and to teach individual nodes 
  15. Flee action behaves very unpredictably - the tank does not flee in the direction I expect, which is away from the enemy, and instead goes on a drive-by course. 
  16. Do tanks shoot backwards? 
  17. Tanks rolling each other over feels unpleasant, as it feels random 
  18. Is there a way to copy AI? 

Overall - feels like a game with a lot of potential. I can easily see how various behaviours and AI nodes can lead to different strategies, and, combined with different map layouts, to different combat scenarios. There is also a decision to make - how detailed you want the AI settings and how much of the behaviour you want to set up from your end. Basically, with higher freedom of setting up UI, my engagement increases logarithmically while the complexity grows exponentially. So a right balance needs to be achieved. However, right now I would recommend focusing on conducting more detailed tests on existing logical nodes and comparing if tank behaviour corresponds with the one expected by players before proceeding with adding new logical nodes. Additionally, I would recommend focusing attention on making tank behavior feel smoother. At the moment, it quite often feels rigid. 

One more thing - tanks have a FoV. I strongly encourage visualizing it, as from the player's perspective it is hard to tell whether a tank sees anyone. So as a player, I see a whole map, and it feels close, so when my tank wanders around aimlessly, it makes me feel as if the tank is at fault while in reality the enemy is just to far or behind my tank. 

Thank you so much for the detailed feedback, and actually trying the AI editor, since I feel it is a pretty big part of the game and I was really needing some eyeballs that are not mine to look at it. Originally I wanted the editor to look like unreal node editor but I couldn't even get a straight line to do what i wanted much less a spline.

1.2.3 Your description of your experience definitely gives me some ideas to make it better, the overload of info right at the start makes sense (as in don't that)

5. the guide does mention that if false it will backtrack, I haven't used the unity behavior designer but the screen shots seem to show similar tree but it goes down instead of to the right.  I guess my question is if the backtrack part mentioned in the guide was missed? if you did that line (maybe you at the time you wrote point 11.) and were still confused ill have to revisit, maybe green output bubble and retry an explicit description. 

7. A visual indicator for tanks vision cone did cross my mind, i dont think it will hurt anything to add that. Did you see the debugs in the top left of screen when you follow a tank?  It shows what ai paths are currently in use.

8. I struggled quite a bit on how to implement leading a target, trying to keep it as modular as possible and not make the text in the node excessive. I think what you are saying is give fire an output and connect lead target to that? is there a reason for fire to ever not use lead target,  instead just make them one node.

9. 14.  As you play through the campaign the shop populates with new AI files to purchase, these files are what the enemies used, nodes dont actually unlock but they do get shown in the later files that enemies use.

10. 18. taking note on QOL features that would be nice, currently the SubAI node can be used to copy another ai tree directly into the open file, allowing modular design.

12. im planning to rework the campaign to start with more tanks, probably 4 as just 1v1 is rather stale.

13. tank selecting targets: i did try to implement a tag system, i need to test it some more.

15. ill have to check on that, in my tests id notice they would start turning to flee but it takes a while. I did not notice them driving the wrong direction so maybe i broke something lol.

16. The turret and body operate independently, the turret can point backwards (and shoot) while the body drives forward, the body cannot drive in reverse currently, only rotates and drives forward, i ran into some issues on backwards driving but might revisit if it makes sense.

17. the ai file can be programmed to mitigate the collisions using wait commands and ifrange, i need to put that into the base files.

you mention smooth feeling tank behavior, im not exactly sure what you mean? like physically the parts of the tank move very rigidly, maybe the body needs a slower acceleration to mimic reality a little more. or do you mean inside the ai editor the constraints on design are too rigid?

Anyways thank you so much for your feedback, I know it takes time but without it we would head down wrong paths and waste our time anyways.

5. The guide does mention that if false, it will backtrack. It did. I saw it and ignored it due to my bias on how this logic node is visualised in the tools I used, so it is not as much the game's fault as it is mine. Although it would be curious to see which method is more obvious to people, when false backtracks or when false leads to the other option forward. 

7. Yes, I saw it, but it is more fun for me to look at the screen where stuff is happening and cheer for my tank rather then look at the corner of the screen and read what is happening :) 

8. Actually, I think your solution of just combining "fire" and "lead" into one node is a very good solution. It simplifies the work without loosing functionality, still give me the depth to set it up and setting it as 0 still allows me to "not use" it. 

9. Got it. In that case - suggest adding indicator to the shop that new stuff is unlocked. (Wild though - allow to purchase new logical nodes in shop)

10. By smooth, I mostly referred to tanks movement. That said, a lot of the jitter of the tank was caused by my own incompetence since my tank would have the logic of "chase if distance > 75" and "flee if distance < 50"  plus a cycle of 5 seconds of if no enemy move to map center or wander around. So that lead to the tank being frequently in the state of constantly switching actions. But as a real player instead of blaming myself for setting up an AI which forces the tank to frequently  change actions I blame the game :) 

NEW: btw - what is the best method to make the tank find another tank? I had relatively frequent cases when at the start of the match tanks will spend quit some time trying to find each other. And since there are no objectives on the map or areas to catch and wander, they wander aimlessly - they do sometimes struggle to find each other. 

5. As far as i know it operates the same way its just to the right instead of down. lets say you have ifenemy and it has two connecting lines from its output with ifrange>100 on top and a ifrange<50 under that, the ai will check the top branch first (>100) and if that is false it will check the (<50) and if that is false it will then backtrack to the next available branch up the tree behind ifenemy. setting up the logic had my head spinning for a while, so i understand lol.

7. that is fair. 

8. i will implement this, i think ill just make it like fire 0 by default and the description will tell you that you can input a number that will lead the target before firing, i think at one point i thought being able to fire without aiming would be useful but cant think of an application now...

9. oh, i could do that. 

10. i believe there is slight acceleration functionality but i may increase it to help smooth out the jerky driving. I do know that tank weights affect speeds and stuff, along with the engine stats, but it may not be noticeable enough, hard to tell unless you have two tanks driving along side each other. You can blame the game, i can take it. all for the effort of making a better product.

I am actively working on some stuff to alleviate the "cant find each other" problem. one solution especially for early levels is to use mapcenter instead of wander for enemy navigation. Also having more than one tank should help fill out the field and provide more vision on the map so less lost puppies. Somewhere at the midpoint the tanks start using COMS node which allows them to see their allies vision and make actions based on that (ie. tank 1 sees enemy, tank 2 vision cant see the enemy but with coms it will chase, or fire at the enemy based on tank 1's vision) penalty for coms currently is slower driving and slower ai node processing (how fast it makes decisions) 

Pushed update for most of the QoL stuff discussed here.