7 Days To Die Dev Tracker

Normal stealth checks would not be desirable in the attack volume case as the zeds are often around corners, enclosed or facing the wrong direction and the player may be making little noise which means default unskilled stealth would mostly work, yet the designers want the zeds to attack.

The one time check is to allow stealth to be useful as a skill you can put points into and allowing for variation in the way you entered the volume compared to zed locations.

The attack uses SetAttackTarget, which is a standard way of the tracking you and used in cases like when you hit them or they see you. I am reducing the trigger's call of SetAttackTarget from 60 to 20 seconds, which seems more reasonable for the attack to time out, since it refreshes anyway if they see you.

Maybe a few weeks.

Bandits in vehicles is near the bottom of my list of what they need to do. You know what happens to the bottom of game dev lists? They generally get cut, but it could happen.

The person who made the video did not notice he is in broad daylight when he tested the attack volumes, so yes they saw him as his stealth was horrible.

Not having shadows on also makes it hard to know when you are in sun or moon light!

They do the normal stealth checks and are actually worse at detecting you since they can only hear you and not see you. A sleeper in the open could see and hear you.

It had nothing to do with the map or blocks. It was raycasts failing briefly from mesh colliders updating, so the turret would see "ground" father below and rapidly move to it. The more a mesh was being updated by say damage, the more often it happened. This fix will be in our next experimental.

There are two types of stealth checks that happen.

1 Continuous - A player stealth update calcs their light level, updates noises and sets themself as noise source on AI entities if they are the higher than other player's noise. AI checks players in their vision cone based on distance vs that player light and then target the player. The player noise on the AI, if above a threshold, will wake the AI. Noise will also make it investigate and do a vision check, which could cause it to see a closer player than the one that made the noise.

2 Triggering a sleeper volume - This happens once per AI based on stealth modified light level vs distance and only determines attack vs active. They will go active in any event and continuous stealth checks may hear or see you at any time after that.

Turrets falling was probably the delayed collider mesh baking. Turrets were very sensitive to their sphere cast hitting below what they were sitting on.

Fixed turrets falling through blocks (Start cast higher, delay fall, move linearly, use current pos for entity pos and recheck hit every frame during move).

Next game maybe, but depends on how much of the stupid they fix in DOTS/ECS. We are planning on HDRP next game. I'm looking forward to using it.

They are predefined meshes of different types with tougher versions within the type. Don't know how many changes we will be able to make within a specific version as this is not UMA.

Not likely. That would be a lot of work and we are pushing features towards gold, not wanting to rewrite stuff.