Player Stats and Hiding mechanism

Player Stats and Hiding mechanism.


Last week I worked on two scripts, one for giving the player  visibility, noise and smell attributes and one for adding those values to items and hiding spots. These attributes will later be used for the AI to detect the player. I still need to add an increment when the user moves in visibility and noise.

So the player starts with the values of:
Player
Visibility:70
Noise: 0
Smell: 10

The torch when lit has its own set of attributes to add to the players stats
Torch
Visibility:100
Noise: 5
Smell: 5

Hiding space
Visibility:-70
Noise: -10
Smell: -10

There are also hiding spots, which when you hide in them they reduce those values thus far reducing the chances of the AI to spot you.


How Hiding works

When the player approaches a hiding space (is within close proximity) and points to it with the cross hair (later on it will be when pointed by a controller) the hiding area gets highlighted.
when you left click the user controls are locked and the player moves towards a spot determined in the hide-in spot prefab.
For now the character just shrinks in order to fit in the spot. 
Later on with the VR there might be a animation played with the player laying down on his chest and using his elbows to crawl into the space.  moving into  a barrel would need another type of animation.



so the players attributes when hiding would be
Player hiding under ledge
Visibility:70
Noise: 0
Smell: 10

A player hiding with the torch would be
Player hiding under ledge
Visibility:100
Noise: -5
Smell: 5

Each AI will have its own attributes of detecting motion noise and smell.

Comments

Post a Comment

Popular posts from this blog

Player stats and brightness.

Image
Player stats and brightness. Last week I worked a bit more on the player characteristics, decided on min max values, and did the same for the Enemy stats. I split the visibility factor into 2 values, brightness and motion. Motion will be affected by the movement of the player and the movement in the headpiece and controllers. Brightness is a factor indicating how well lit the player is. So the enemy has skill values for detecting motion sound and smell, it also has a detection generic skill value which is linked with the enemies intelligence. So any light source will have attached a brightness script that triggers and sends a brightness value to the player brightness when the player is in range and increase as the player comes closer to the light source. The player value of Brightness is for now a static value, so multiple light sources can affect it. I still need to cast a ray cast from the light source to the player, if it fails to hit the player then that would indicate that ...
Read more

Testing the PLG

Image
Testing the PLG Before I get into the testing section Progress on the tasks remaining Place restrictions on all controls in the room generator editor. So you can't place the replaced rooms outside the level and the scan lines. DONE Fix some conditions in chance the quarter can not find a theme room or it the two theme rooms are too close. *I have decided to ignore this and come back to it if i have time after the documentation. Place the furniture , loot and enemies into the level.  Scan the area and store the points that were hit. - this is for demonstration purposes to show how many times that area has a tile placed, to demonstrate how different the levels are. DONE  Store the seed number, the number of tiles used, the  distance to reach the exit and the exit room location DONE So tomorrow I start working on placing the enemies and loot into the level. Testing Today I ran the PLG in a sequence of 40. I have also added 3 functions at before the PL...
Read more

More work done on the interface, saving data.

Image
More work done on the interface, saving data. I would have liked to say that I started on the loot and enemy randomization, but that is not the case. What I thought would be an hour work job took me half a day. I have now finished with the way the randomizing feed is stored. When a level is complete (PLG state is -off) two buttons appear in the inspector allowing the user to store the seed in a whitelist of black list. When the time comes to generate the level the user has a larger option of choices:  Generate a completely randomly level.  Generate a  completely randomly level but it will never be one of the levels we blacklisted (if we tick on use black list). Generate a specific level from a ID we enter. Load a random level that is included in the whitelist. In order the randomization between levels within the list to be equally random before storing the lvl ID we load the current values and check if the Id already exists, if it does then there i...
Read more