Week 9 Friday Game resetting if Generation failed.

Week 9 Friday Game resetting if Generation failed.

Yesterday after writing down the algorithm (for the conditions in which the PLG knows the level has failed) I implemented and it worked with the first attempt.
Next up was a way to reset and start again the level generation.
the most painless process is reloading the scene so you reset the variables and make sure all components have been deleted.
 I encountered a problem though after the initial attempt when the scene is reloaded the source light does not seem to work. I thought for some reason the light needed to be in outside the scene. but that did not seem to work. I also realized that the light source would probably change and it is not needed to be placed at the beginning of the scene but way after after the loot and enemy placement.
For visibility though I have scripted so you assign a lightsource prefab that is placed right after we get a good level.

Below is a test run were I have put the exit scan line too far away, so the level can never find preexit rooms so it will never create a good level. As I mention in my previous post, the level checks the density, once it reaches the desired value of density set by the user it begins to check if there is a preexit and attach the exit. If it does not find a exit it sets a counter to 10 which declines every time we try to add another tile. Because of the way we setup our exit scan line (in this example), an exit is never found so the program will add another 10 pieces try again in a endless loop. This is why we break the loop and declare the level as bad. To break the loop one of two things need to happen.

  1.  There are no more OpenExits available.
  2.  The density has now reached our max density. which is a value set in the editor.



Below is the current script, the level starts without a light source, when the level is successful we then add the lightsource.



Next step is capping the outside exits and calculating the path from start to exit.

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