More work done on the interface, saving data.

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:

  1.  Generate a completely randomly level.
  2.  Generate a  completely randomly level but it will never be one of the levels we blacklisted (if we tick on use black list).
  3. Generate a specific level from a ID we enter.
  4. 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 is no need to add the ID. This is done so we do not have multiple entries of the same Id in our list. In addition to storing the ID, when we save a level either as a black or white list. It takes a screen shot of the level with the level id as its name. 

The most time consuming process was storing those images in the correct folders. I noticed when unity creates screenshots it has 2 limitations:

  1. The screenshots are stored in the main folder of your project and you can change that.
  2. You cannot take a picture of the editor window only the game window.
So after spending some time realizing that unity will not store the file in subfolders, I found a method to transfer the file like you would transfer files in an old dos command.  Unfortunately that did not work and i had to figure out that "Application.dataPath" is bugged and for some users the code would work on one machine but not the other. So I found a way from ( https://stackoverflow.com/questions/52797/how-do-i-get-the-path-of-the-assembly-the-code-is-in)


public static string AssemblyDirectory
{
    get
    {
        string codeBase = Assembly.GetExecutingAssembly().CodeBase;
        UriBuilder uri = new UriBuilder(codeBase);
        string path = Uri.UnescapeDataString(uri.Path);
        return Path.GetDirectoryName(path);
    }
}



So with some trimming and combining strings I got my initial path then I created the destination path.

Now I had the 2 correct paths but still it would not transfer the file. I narrowed it down to it could not finĪ“ the file, which after many failed attempts led me to the conclusion that  the file was not created as fast as the next line was executed, you can't find something that does not exist yet.
so the class was turned into a ienumerrator  making it wait 5 sec in the background before transferring the file to its desired location.

Also the state machine is very useful as I can dictate which controls are visible in the stages, I found myself  pressing the start level when in edit mode, so I only show the start button if the application is in play mode and the machine state is -Finished.
I also hide the "Add to Whitelist"  and "Add to Blacklist" until the state is finished, to prevent the used taking screenshots of an empty canvas. In general the machine state make it really east and clean to Dictate when components in the editor are displayed.

Next up randomizing the loot and enemies.


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