Daggerfall Workshop Forums

Here is Part.20 where I:
- Trying to estimate room value/context with rays and physics overlap

Here is Part.21 where I:
- Creating cube objects in Unity editor as visual aid to view approximate size of physics overlaps
- Realizing some stuff about how DFU combines models
- Ways to potentially work around these combined models, at possible cost to performance
- What I'm likely going to do after realizing this limitations involving the "Room Context" generation mechanics

Here is Part.22 where I:
- Use the Unity Editor console for debugging what physics cubes are overlapping

Here is Part.23 where I:
- Explaining how strings and int types are different and why you might want one over the other
- Changing string values to ints for better use later in code

Here is Part.24 where I:
- Adding in filtering process for billboard/flat objects, as well as enemy entities detected by physics overlap

Here is Part.25 where I:
- Combine multiple For-Loops into a single one, for more efficient use and filtering

Here is Part.26 where I:
- Filtering enemy types based on their career index value
- Using this to give ballpark value to our room value mod based on enemies hit by physics overlap

Here is Part.27 where I:
- Filtering billboard flats based on their archive number
- Using this to give ballpark value to our room value mod based on billboard theme within each archive

Here is Part.28 where I:
- Filtering 3D models based on their model ID number as an int value
- Using this to give ballpark value to our room value mod based on what the model in question is
- Also adding some framework stuff so we can actually use our "totalRoomValueMod" to be used in generation formulas

Here is Part.29 where I:
- Rolling dice to determine if a chest should generate in place of a loot-pile, taking room value into consideration
- Some planning for how chest and lock materials will be determined, with a "hat of tickets" approach of choosing