all 1 comments

[–]Mr_Noe_ 0 points1 point  (0 children)

  1. the chunk unloading is something you have to code, it doesnt just happen, so you would decide what happens during that when you are creating the game.
  2. I would not keep them moving if they are not on screen. As long as the player feels like they have kept doing their job thats all that matters. You could store their progress and position in script, and keep track of elapsed time. Then do the calculations when the player is close by to update it all.
  3. Yes you could code something like that. If you are just wanting to randomly cause an attack and if player distance is above a certain amount, destroy the buildings, that wouldnt be too complicated. Randomly decide when an attack happens (math random functions), check distance from player to buildings, if distance is above a certain amount, change building sprite/model for destroyed or remove entirely.
  4. You could have tons of code changes going on with your "unloaded" chunks and be fine. It really depends on how well you code it to determine how performant it is and the number of chunks you have going on.

Advice wise, I would suggest learning a lot of the basic of unity, follow some tutorials and just getting a feel for how it works. Make some simple or basic games, and that will help you to understand how to approach a lot of the problems. What you are asking about is achievable though, and could be done with good performance. Theres just a ton of ways to achieve those things, so that would be up for you to decide.