You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Encounters with the sos-encounter method have no way of linking back to the mons that are responsible for calling them.
Pokemon can call for pokemon outside their own evolution family.
Pokemon do not always even call for their own species.
Some pokemon don't call for help at all.
With those facts in mind, I only see one way to do this: make an object to point to the original encounter with the following data
A pokemon object like the one that already exists in pokemon_encounters blocks.
An index that points to the relevant encounter_details block within the relevant version_details block. The game version would already be known from the version object in the SOS encounter.
This will require splitting up a handful of encounters into two because some Pokemon change who they call based on time of day. For instance Eevee can call Espeon during the day and Umbreon at night. Variance based on percentages is also feasible.
So imagine there was a table like this (condensed for brevity):
To find who called Pikachu, you would iterate through pokemon_encounters until you find a matching sos-link.pokemon, then iterate through version_details until you find a matching version, then get encounter_details[sos-link.index].
This would remove the need for the sos-from-bubbling-spot method as you would be able to reference the original encounter's method.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Encounters with the
sos-encounter
method have no way of linking back to the mons that are responsible for calling them.With those facts in mind, I only see one way to do this: make an object to point to the original encounter with the following data
pokemon
object like the one that already exists inpokemon_encounters
blocks.encounter_details
block within the relevantversion_details
block. The game version would already be known from theversion
object in the SOS encounter.This will require splitting up a handful of encounters into two because some Pokemon change who they call based on time of day. For instance Eevee can call Espeon during the day and Umbreon at night. Variance based on percentages is also feasible.
So imagine there was a table like this (condensed for brevity):
To find who called Pikachu, you would iterate through
pokemon_encounters
until you find a matchingsos-link.pokemon
, then iterate throughversion_details
until you find a matchingversion
, then getencounter_details[sos-link.index]
.This would remove the need for the
sos-from-bubbling-spot
method as you would be able to reference the original encounter's method.Beta Was this translation helpful? Give feedback.
All reactions