Raphtalia
/
DungeonGenerationPlus_LethalCompany_Mod
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update Quick Main Paths Setup

Raphtalia 2024-10-22 04:15:35 +00:00
parent 7d43e6291c
commit 773ac70203
1 changed files with 21 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
Quick-Main-Paths-Setup.md

@ -29,43 +29,49 @@ The following is an example if the dungeon generation were to create two main pa
In the `DunGenExtender` asset, set `MainPathCount` to some value above 1.
Set the `MainRoomTilePrefab` to the tile that you want the alternate main paths to start from. This is NOT the fake start tile that many dungeon's like to use. Be sure that this tile has multiple doorways.
Set the `MainRoomTilePrefab` to the tile that you want the alternate main paths to start from. This **CANNOT** be a start tile. Be sure that this tile has multiple doorways.
![](https://i.imgur.com/ZVMeCCo.png)
The `DungenFlow's` node list is replicated onto the alternate main paths. The starting index is based on the `MainPathCopyNodeBehaviour` selected. Any nodes before the starting index will be ignored and not be generated. I suggest you select `Copy From Main Path Position` first, and later decide if `Copy From Node List` is right for your dungeon.
The `DungenFlow's` node list is replicated onto the alternate main paths. The entire list is not replicated; it begins from a starting index based on the `MainPathCopyNodeBehaviour` selected. Any nodes before the starting index will be ignored and not be generated. I suggest you select `Copy From Main Path Position` first, and later decide if `Copy From Node List` is right for your dungeon.
> **NOTE:** Due to how injection tile rules work, they cannot be duplicated to the alternate main paths. They still function properly for the first main path. If you want to force generation of certain tiles, you can achieve a similar effect with the Copy From Node List behaviour and the Archetypes On Normal Nodes feature below.
### Copy From Main Path Position
The starting index is the first node whose position is greater than the `MainRoomTilePrefab's` depth on the first main path.
The starting index is the first node whose position is greater than the `MainRoomTilePrefab's` depth on the first main path. In other words, all nodes whose depth is higher than the `MainRoomTilePrefab's` depth will be replicated.
> **NOTE:** The depth is some number between 0 and 1. As such, you can expect the start node to always be ignored and the end node to always be duplicated on the alternate main paths.
> **:warning: WARNING: :warning:** This behaviour is perfectly safe to use **IF** the node's positions are no where near the `MainRoomTilePrefab's` predicated depth or you don't use nodes besides the start and end node. This behaviour is not safe to use and can lead to funky and broken dungeon generations **IF** the node's position are near the `MainRoomTilePrefab's` depth. In these situations, I recommend using `Copy From Node List` instead.
> **:warning: WARNING: :warning:** Depending on the moon's map multiplier and other factors beyond your control, you cannot predict the length of the main paths. As such, the `MainRoomTilePrefab's` depth is unpredictable. This can potentially lead to dungeon generation issues if not accounted for.
>
> This behaviour is perfectly safe to use **IF** the node's positions are no where near the `MainRoomTilePrefab's` expected depth **OR** you only use the start/end nodes and don't use any additional normal nodes.
>
> This behaviour is not safe to use and can lead to funky and broken dungeon generations **IF** any node's (particularly normal nodes) position are near the `MainRoomTilePrefab's` expected depth. In these situations, I recommend using `Copy From Node List` instead.
| Main Path Length 10 (Good) | Main Path Length 5 (Scary) |
|---|---|
| ![](https://i.imgur.com/uG7RgWs.png) | ![](https://i.imgur.com/hxzikww.png) |
In the picture to the left, the `0.15` node tile is the first node replicated onto the alternate main path as it's the first node whose position is greater than the `MainRoomTilePrefab's` depth of `0.1`.
In the picture to the right, you can see the dangers if the node's positions are near the `MainRoomTilePrefab's` depth. Since the main path's length is 5, the first tile after the start tile would have a depth of `0.2`. This would lead to the node tile generating first before the `MainRoomTilePrefab`. As such, the `0.15` node will not be replicated for the alternate main path. More scary, since the start tile doesn't follow with the `MainRoomTilePrefab`, the dungeon generation may completely break both code-wise and/or visual-wise. See the Copy From Node List section below for how you could address this.
> In the picture to the left, the `0.15` node tile is the first node replicated onto the alternate main path as it's the first node whose position is greater than the `MainRoomTilePrefab's` depth of `0.1`.
>
> In the picture to the right, you can see the dangers if the node's positions are near the `MainRoomTilePrefab's` depth. Since the main path's length is now 5, the first tile after the start tile would have a depth of `0.2`. This would lead to the node tile generating first before the `MainRoomTilePrefab`. As such, the `0.15` node will not be replicated for the alternate main path. More scary, since the start tile doesn't follow with the `MainRoomTilePrefab`, the dungeon generation may completely break both code-wise and/or visual-wise. See the Copy From Node List section below for how you could address this.
### Copy From Node List
The starting index is the first node whose tilesets contain `MainRoomTilePrefab` plus 1. Due to this, the node section MUST contain some node whose tileset contains `MainRoomTilePrefab`.
The starting index is the first node whose tilesets contain `MainRoomTilePrefab` plus 1. By using this behaviour, we are depending on the nodes section to spawn the `MainRoomTilePrefab` tile instead of the vanilla method with the unique door socket.
> **:warning: WARNING: :warning:** The node section **MUST** contain some normal node whose tileset contains `MainRoomTilePrefab`.
![](https://i.imgur.com/36pzD7Q.png)
If you select this behaviour, you may want to enable the Archetypes On Normal Nodes feature below.
> **NOTE:** This behaviour is the only way to guarantee that certain tiles generate in a certain order on the alternate main paths.
![](https://i.imgur.com/W5hNhDG.png)
The following is an example to why you'd want to choose `Copy From Node List`. You can force the interior to generate a sequence of tiles at the start of the main path. You simply list out the sequence in the node list and set their position to all 0. This works perfectly fine for the first main path. However, the nodes after the main tile (which would generate the `MainRoomTilePrefab`) would not replicate onto the alternate main paths. This behaviour occurs with `Copy From Main Path Position`.
If you choose and setup `Copy From Node List` instead, the algorithm will replicate the nodes after the main tile.
>
> The following is an example to why you'd want to choose `Copy From Node List`. You can force the interior to generate a sequence of tiles at the start of the main path. You simply list out the sequence in the node list and set their position to all 0. This works perfectly fine for the first main path. However, the nodes after the main tile (which would generate the `MainRoomTilePrefab`) would not replicate onto the alternate main paths. This behaviour occurs with `Copy From Main Path Position`.
>
> If you choose and setup `Copy From Node List` instead, the algorithm will properly replicate the nodes after the main tile.
| Copy From Main Path Position | Copy From Node List |
|---|---|