From 9666bcc55fd5c19ec525136ea0044add73e53d49 Mon Sep 17 00:00:00 2001 From: Iceman8911 <108531451+Iceman8911@users.noreply.github.com> Date: Tue, 28 Feb 2023 17:57:08 +0100 Subject: [PATCH] Updated Adding Time Based Encounters with a Variable (markdown) --- Adding-Time-Based-Encounters-with-a-Variable.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Adding-Time-Based-Encounters-with-a-Variable.md b/Adding-Time-Based-Encounters-with-a-Variable.md index 085fd24..85caf63 100644 --- a/Adding-Time-Based-Encounters-with-a-Variable.md +++ b/Adding-Time-Based-Encounters-with-a-Variable.md @@ -142,4 +142,5 @@ Those two lines make sure that the encounters will be rechecked(and adjusted if **PS:** * If you want more or less encounter periods, just alter **SetTimeBasedEncounters()** and your encounter groups in Porymap as required. -* If its weather-based encounters you want, you'll want to change the conditionals in **SetTimeBasedEncounters()** (rename that too) to check for the type of weather rather than time(something along `if (gSaveBlock1Ptr->weather == WEATHER_SNOW)`). \ No newline at end of file +* If its weather-based encounters you want, you'll want to change the conditionals in **SetTimeBasedEncounters()** (rename that too) to check for the type of weather rather than time(something along `if (gSaveBlock1Ptr->weather == WEATHER_SNOW)`). +* If for some reason you want to stop or 'freeze' the encounters to a particular group, instead of using `callnative(SetTimeBasedEncounters)`, just hard set it with `setvar VAR_TIME_BASED_ENCOUNTER, `. \ No newline at end of file