Dungeon Flow Node (Asset) - Revision history

JasX at 22:37, 23 March 2026

2026-03-23T22:37:17Z

← Older revision		Revision as of 22:37, 23 March 2026
Line 127:		Line 127:
	\|[[Game Action (Asset)\|GameAction]]		\|[[Game Action (Asset)\|GameAction]]
	\|		\|
	\|When set, the dungeon generator will try to force the end room with a chest placeholder, and add one of the game actions as the chest game action. Useful for boss loot etc~~. Note: This is ignored unless you also set Force End Encounter~~.		\|When set, the dungeon generator will try to force the end room with a chest placeholder, and add one of the game actions as the chest game action. Useful for boss loot etc.
	\|}		\|}

JasX at 22:36, 23 March 2026

2026-03-23T22:36:12Z

← Older revision		Revision as of 22:36, 23 March 2026
Line 127:		Line 127:
	\|[[Game Action (Asset)\|GameAction]]		\|[[Game Action (Asset)\|GameAction]]
	\|		\|
	\|When set, the dungeon generator will try to force the end room with a chest placeholder, and add one of the game actions as the chest game action. Useful for boss loot etc.		\|When set, the dungeon generator will try to force the end room with a chest placeholder, and add one of the game actions as the chest game action. Useful for boss loot etc. Note: This is ignored unless you also set Force End Encounter.
	\|}		\|}

JasX at 22:34, 23 March 2026

2026-03-23T22:34:48Z

@@ Line 107: / Line 107: @@
 |[[Encounter (Asset)|Encounter]]
+|
-|When set, the first room will get these encounters as its encounters, and one is picked at random.
+|When set, the first room will get these encounters as its encounters.
 |-
 |Force End Encounter
@@ Line 113: / Line 118: @@
+|
 |When set, the last room generated will have its encounters set to this one. And one is picked at random.
 |}

JasX at 13:47, 23 March 2026

2026-03-23T13:47:45Z

← Older revision		Revision as of 13:47, 23 March 2026
Line 112:		Line 112:
	\|[[Encounter (Asset)\|Encounter]]		\|[[Encounter (Asset)\|Encounter]]
	\|		\|
	\|When set, the last room generated will have its encounters set to this one.		\|When set, the last room generated will have its encounters set to this one. And one is picked at random.
	\|}		\|}

JasX at 20:45, 30 August 2025

2025-08-30T20:45:40Z

← Older revision		Revision as of 20:45, 30 August 2025
Line 92:		Line 92:
	\|[[Dungeon Sub Template (Asset)\|Dungeon Sub Template]]		\|[[Dungeon Sub Template (Asset)\|Dungeon Sub Template]]
	\|		\|
	\|When generated, these are shuffled, and only one of these are picked. At least one room must pass conditions and be valid to be used with the dungeon template quest.		\|When generated, these are shuffled, and only one of these are picked. At least one room must pass conditions and be valid to be used with the dungeon template quest. If none are supplied, a condition-free group is used.
	\|-		\|-
	\|Vaible Templates		\|Vaible Templates

JasX at 20:37, 30 August 2025

2025-08-30T20:37:07Z

← Older revision		Revision as of 20:37, 30 August 2025
Line 1:		Line 1:


	A flow node is used to create a general layout for an advanced procedural dungeon. Each node can have multiple condition groups, but only one is ever picked. These condition groups decide which room templates should be available in that group. Such as cave tiles that also support forest tiles etc. These tiles must be specified in Room Templates, and the conditions of the room templates still apply.		A flow node is used to create a general layout for an advanced procedural dungeon. Each node can have multiple condition groups, but only one is ever picked. These condition groups decide which room templates should be available in that group. Such as cave tiles that also support forest tiles etc. These tiles must be specified in Room Templates, and the conditions of the room templates still apply.

			===== Caveats: =====

			* The first flow node used in a dungeon template MUST be able to start at coordinates 0,0,0. Because that's where the entrance room is placed.

	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+

JasX at 14:56, 28 August 2025

2025-08-28T14:56:34Z

@@ Line 17: / Line 17: @@
 |When checked, this flow node may be ignored at random.
 |-
-|Requires Quest
+|Friendly
 |Boolean
 |False
-|When checked, the dungeon template MUST have a quest, and that quest MUST be accepted before the door to this node's area is unlocked.
+|You can use the flowNodeFriendly condition type in the various conditions fields in your dungeon template.
 |-
 |Min Rooms
@@ Line 31: / Line 36: @@
 | -1
 |Maximum nr of rooms to generate. Anything below Min Rooms is clamped at Min Rooms.
 |-
 |Condition Groups
@@ Line 36: / Line 86: @@
+|
 |When generated, these are shuffled, and only one of these are picked. At least one room must pass conditions and be valid to be used with the dungeon template quest.
 |}

JasX: Created page with "A flow node is used to create a general layout for an advanced procedural dungeon. Each node can have multiple condition groups, but only one is ever picked. These condition groups decide which room templates should be available in that group. Such as cave tiles that also support forest tiles etc. These tiles must be specified in Room Templates, and the conditions of the room templates still apply. {| class="wikitable" |+ !Field !Type !Default !Description |- |Name |Stri..."

2025-08-21T15:52:43Z

Created page with "A flow node is used to create a general layout for an advanced procedural dungeon. Each node can have multiple condition groups, but only one is ever picked. These condition groups decide which room templates should be available in that group. Such as cave tiles that also support forest tiles etc. These tiles must be specified in Room Templates, and the conditions of the room templates still apply. {| class="wikitable" |+ !Field !Type !Default !Description |- |Name |Stri..."

New page

A flow node is used to create a general layout for an advanced procedural dungeon. Each node can have multiple condition groups, but only one is ever picked. These condition groups decide which room templates should be available in that group. Such as cave tiles that also support forest tiles etc. These tiles must be specified in Room Templates, and the conditions of the room templates still apply.
{| class="wikitable"
|+
!Field
!Type
!Default
!Description
|-
|Name
|String
|
|Optional, just used in the editor to remind you of the purpose of the flow node, such as "forest".
|-
|Optional
|Boolean
|False
|When checked, this flow node may be ignored at random.
|-
|Requires Quest
|Boolean
|False
|When checked, the dungeon template MUST have a quest, and that quest MUST be accepted before the door to this node's area is unlocked.
|-
|Min Rooms
|Int
|1
|Minimum nr of rooms to generate. A minimum of 1 is enforced.
|-
|Max Rooms
|Int
| -1
|Maximum nr of rooms to generate. Anything below Min Rooms is clamped at Min Rooms.
|-
|Condition Groups
|[[Dungeon Sub Template (Asset)|Dungeon Sub Template]]
|
|When generated, these are shuffled, and only one of these are picked. At least one room must pass conditions and be valid to be used with the dungeon template quest.
|}