Imbion at 00:35, 18 June 2025

2025-06-18T00:35:32Z

← Older revision		Revision as of 00:35, 18 June 2025
Line 1:		Line 1:
	This is my sandbox. For article draft shenanigans and the like, and also some of my own personal notes on PMDO modding.		This is my sandbox. For article draft shenanigans and the like, and also some of my own personal notes on PMDO modding.

			'''Subpages:''' [[User:Imbion/Sandbox/Dungeon Ref\|Dungeon Ref]]

	== Exiting Dungeon Segments ==		== Exiting Dungeon Segments ==

Imbion: Created page with "This is my sandbox. For article draft shenanigans and the like, and also some of my own personal notes on PMDO modding. == Exiting Dungeon Segments == Once you've created a dungeon, you might notice that when you leave a segment the game simply stops execution. This is because we need to tell the game what to do upon exiting a segment through lua scripting. === Understanding ExitSegment === Contained in the scripting file for your zone, `init.lua`, is the Ex..."

2025-06-04T19:23:06Z

Created page with "This is my sandbox. For article draft shenanigans and the like, and also some of my own personal notes on PMDO modding. == Exiting Dungeon Segments == Once you've created a dungeon, you might notice that when you leave a segment the game simply stops execution. This is because we need to tell the game what to do upon exiting a segment through lua scripting. === Understanding ExitSegment === Contained in the scripting file for your zone, <code>init.lua</code>, is the Ex..."

New page

This is my sandbox. For article draft shenanigans and the like, and also some of my own personal notes on PMDO modding.

== Exiting Dungeon Segments ==
Once you've created a dungeon, you might notice that when you leave a segment the game simply stops execution. This is because we need to tell the game what to do upon exiting a segment through lua scripting.

=== Understanding ExitSegment ===
Contained in the scripting file for your zone, <code>init.lua</code>, is the ExitSegment function. This function is what the game uses to decide what to do when you leave a segment.

This function receives the following information from the game when exiting a segment, storing them in a variable we can reference inside of the function itself:

* <code>zone</code>: The zone we currently exited.
* <code>result</code>: The outcome of the dungeon exploration - Most relevant, this lets us check whenever the segment was cleared or if the player was defeated.
* <code>rescue</code>: Tells us whenever we're rescuing someone or not. This is true if we are rescuing, and false if we are not.
* <code>segmentID</code>: A number that tells us what segment of the dungeon we're exiting from, based on the ordering in the mod editor. It starts at 0 and counts up by one per next segment.
* <code>mapID</code>: Says the map ID that we just exited from. Isn't referenced most of the time.

In order to tell the game what to do, we need to check if these variables have a certain value.

=== An Example ===

Let's take a look at how the <code>ExitSegment</code> function of ''Faded Trail'' works. We use a <code>if...elseif...else</code> block in order to branch through our different choices.

First, we want to check if we are in rescue mode, and succeeded on the rescue:
<pre>
local exited = COMMON.ExitDungeonMissionCheck(result, rescue, zone.ID, segmentID)
if exited == true then
--do nothing
</pre>

You only require this part of the block if your dungeon should support rescues.

If exited is false, then we continue along the statement. This branch is taken if the dungeon was not cleared.:
<pre>
elseif result ~= RogueEssence.Data.GameProgress.ResultType.Cleared then
COMMON.EndDungeonDay(result, SV.checkpoint.Zone, SV.checkpoint.Segment, SV.checkpoint.Map, SV.checkpoint.Entry)
</pre>

The dungeon day is ended, and the player is sent back to their last checkpoint with punishments applied.

If the above is false, then we enter into a branch that holds the results if we cleared the dungeon. So, all other results under this one else assume the player has cleared the dungeon.

''Faded Trail'' is a dungeon with an alternative dungeon segment that the player can take. We would like to do something different if the player clears the alternative segment. The default segment, ''Faded Trail'', is segment 0, while the alternative segment, ''Hidden Trail'', is segment 1.

For segment 0, we just want to send the player to the forest camp:
<pre>
if segmentID == 0 then
COMMON.EndDungeonDay(result, 'guildmaster_island', -1, 4, 0)
</pre>

For segment 1, we want the player to go back to the island entrance and unlock a new dungeon:
<pre>
elseif segmentID == 1 then
COMMON.UnlockWithFanfare('faultline_ridge', true)
COMMON.EndDungeonDay(result, 'guildmaster_island', -1, 1, 3)
</pre>

Finally, we make our last else be a fallback function that sends the player to their last checkpoint:
<pre>
else
PrintInfo("No exit procedure found!")
COMMON.EndDungeonDay(result, SV.checkpoint.Zone, SV.checkpoint.Segment, SV.checkpoint.Map, SV.checkpoint.Entry)
end
</pre>

=== Blueprint ===
Putting it together, we get this psuedocode blueprint of what occurs while running <code>ExitSegment</code>:

<pre>
--first check for rescue flag; if we're in rescue mode then take a different path
local exited = COMMON.ExitDungeonMissionCheck(result, rescue, zone.ID, segmentID) --check if we cleared while doing a rescue
if exited == true then
--do nothing; this is a dummy branch to stop us from going through the other branches
elseif result ~= RogueEssence.Data.GameProgress.ResultType.Cleared then -- resolves true if the dungeon was not cleared
--end the dungeon day by sending the player back to their last checkpoint, since they didn't clear the dungeon
COMMON.EndDungeonDay(result, SV.checkpoint.Zone, SV.checkpoint.Segment, SV.checkpoint.Map, SV.checkpoint.Entry)
else -- we didn't resolve true for being in rescue or losing the dungeon, so we must have cleared the dungeon
-- now we will check what segment we took, so we can make the game do what we want to depending on the segment
if segmentID == 0 then
-- do things for exiting on segment 0
elseif segmentID == 1 then
-- do things for exiting on segment 1
elseif .... -- continue checking likewise for all the segments we have
else -- this is a fallback branch, in case we went through all of the branches and hit nothing (which should not happen!)
PrintInfo("No exit procedure found!")
-- just send the player to their last checkpoint
COMMON.EndDungeonDay(result, SV.checkpoint.Zone, SV.checkpoint.Segment, SV.checkpoint.Map, SV.checkpoint.Entry)
end
end
</pre>

User:Imbion/Sandbox - Revision history

Imbion at 00:35, 18 June 2025