Week 6-7 Placing the rooms in the labyrinth.

Week 6-7 Placing the rooms in the labyrinth.

This update was written 17/11/17. Week 8.
Unfortunately this part of the PLG took 3 weeks to complete due to a problem encountered.

The first draft of the algorithm was this
Place the rooms
1.    Select randomly a open exit in open_exits List. This will be the exit way we attach the next component.
2.    Select randomly between room or corridor.
3.    Select randomly a open exit from the selected room/corridor.
4.    Rotate the the parent room/corridor so it aligns with the selected open exit.
5.    Move the Room so both exits are in the same location.
6.    Check if the placed room collides with an existing room and if it placed outside the layout area.
7.    If any of the above two statements is true then delete the room/corridor.
8.    If not, remove the selected exit from the open_exits list
9.    Check if any of the remaining exits of the room/corridor are outside the level area, if they are add them to the PossibleExitPoint list, if not then add the room/corridors remaining exits to the list open_exits.
10.  Repeat steps 10-18 until the room density is reached or step 18 has failed 4 times in a row.
Snap Rooms Together and Closing open doorways
11. Check if at least one of the exits from each preset piece is not listed in the open_exits list. Indicating that are preset room is conneceted.
12. If  a preset room is not connected find the nearest open exit and create a corridor attaching it. Repeat for all unattached presets rooms.
13. While the open exits list is in size larger than Y (another number to be determined) find a open exit and connect it to the closest open exit available.
14.  While the open exits list is in size larger than Z (another number to be determined) add a cap room (cap rooms are rooms with only one exit point) to a random exit in openexits list and remove it from the list.
For each of the remaining open exits randomly assign a and place a blocking point prefab. This might be a sealed door a pile of rubble blocking the door.

 Bellow I will mention changes to the current algorithm: 

 Initially I worked to just create a complex of attached rooms ignoring the layout. 

      1. I choose a random exit point from the available exit points, later on I decided to just take the first exit from the list ExitPoints[0].Transform. There is a List (FailedAttemps  <int>, same size as openExits) this list indicates how many times we have tried to attach a room to that point. Every time it fails we increase the value for that point by 1, starting from 0. if the value is greater than 2 then we remove that point from the list and try again at position index=0.

 2. I still select and instantiate randomly between rooms, open areas and corridors, no restriction yet, but there will be a Legendary container where rooms can only be placed once.

 3.    Select randomly a open exit from the selected room/corridor.

 4.    Rotate the the parent room/corridor so it aligns with the selected open exit.

 5.    Move the Room so both exits are in the same location.

 6.    Check if the placed room collides with another room. 

 7.    If collision is detected  the room/corridor , increase the value of failed attempts list, which is the same size of the OpenExits.

 8.    If coliition is detected delete the piece* (to be stored in the future to increase performance) and increase failedattempts[0] by 1. go to step 1.

 9.If no colition was detected.

 9a. Examine if any of the remaining exit points are outside the max area, if yes store them in OutsidePoints List. 

 9b. Examine if any of the  remaining exit points are close to any of our preset pieces exits.
       if yes attach the preset piece to that exit. Remove that preset piece from the preset folder. check if the preset folder is empty if yes then delete it.

 10. Add the remaining exits of the open piece to the OpenExits[]

 11.  Repeat steps 1-10 until the room density is reached or step the NumberOfRooms set is equal to the room counter.

 12. Scan the density of the labyrinth, in steps of 10. if the density is smaller then target density then NumberOfRooms=NumberOfRooms+10 and set the boolean indicator for good density as false.

 13. If the density is good then scan the line for the pre-exit room (same code used when looking for the exit plane.

 14. Add to 50% of the points in OutsidePoints list a random One exit room.

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