Hi,
This week our team did some gameplay testing to see if the game we were making would actually be fun to play.
Unfortunately I had some trouble with getting the online version to work but was able to play test the singleplayer version.
Christophe Degraeve
This week I updated the character , I wrote all the necessary base code for allowing weapon reload functionality , sprinting and health. All the necessary code is now there.
With our latest prototype test we already started tweaking the movement values and have got them about right.
As a help i started writing down my current bugs in a small file so I can get around fixing them when needed.
This week we have done A LOT of play testing. Our devs built a multiplayer prototype so that we can imitate AI behavior ourselves. This thought us a lot about our current gameplay. We were also able to come to a conclusion of how our drones will behave around the player and the environment. Running speed, forrest size, drone speed and aggressiveness and much more now all have values. We can now start building our AI around these values and behavior.
Next week we will migrate our prototype to an actual forrest level. We will then replace the player controlled drones to artificial ones and do a lot more play testing to get our gameplay just right.
After that we will move on to production and implementing the gathering and survival elements.
Stay tuned!
Hey!
This week we had to try out some quick AI behaviour, so we made a prototype were we could take control of a drone. This way we could set restrictions on the movement and behaviour our final ai should be.
We came to the conclusion that we wanted 2 types of drones. One that moves randomly around and one that follows a set path. After the drone sees a player he has to wait 1 or 2 seconds before chasing the player. This wait time is a “scan” to identify the player. It gives the player more breathing room to stay hidden.
After the player is found the drone will get more movespeed and will go to +-5m from the player and ten attack with a zap attack.
If the player goes out of the line of sight, the drone will move to the last known position and return to his normal beaviour after 2 seconds (if the player is lost).
Drones can float to a minimum of 1m above the ground to maximum tree height.
The player can shoot the drone, the first shot will stun the drone (circuit malfunction) for 1 or 2 seconds. the second shot will kill the drone.
This was our test for this week and what we’ve learned from it 🙂
Cheers!
Vermeulen Igor
Greetings!
This week I made AI for our drone enemy. It uses a node system so it can patrol With a behaviourtree it is easy to control when it needs to attack and when it needs to patrol
Cheers!
Vermeulen Igor
Hi!
This week i tested how the Morph target work in unreal engine, i also the grass better and inverted the height. i also worked with christophe to refine the tree’s to let them match the style we are going for.
We decided on using Unreal engine 4 because it would suit our game a lot more then Unity. However , we didn’t have any experience with using mercurial repositories and UE4 yet , so we went in blind.
Needless to say , after 1-2 weeks it felt like crashing into a brick wall.We hadn’t been paying attention to our bucket size , and suddenly it had grown to over 2gig , which is a problem , as bitbucket doesn’t allow repositories bigger then 2gig.
When i noticed that my pushes didn’t want to go through anymore , i decided to investigate and i came to the conclusion pretty fast that this wouldn’t be as easy a fix as you would think it to be. You can’t simply delete files and fix your repository in a further push , as you can not push anymore changes , the only option is to go “backwards” in time and fix your repository in an earlier not-yet-broken commit.
I managed to get our current push to around 50mb in size. However , bitbucket still does not allow this push to go through as we have exceeded 2gb , I fear we will have to start anew with a fresh repository , as i do not know how to revert these pushes.
