Mirrors/PKHeX
2
0
Fork 0
mirror of https://github.com/kwsch/PKHeX synced 2024-11-27 14:30:56 +00:00
Code Issues Projects Releases Packages Wiki Activity
PKHeX/PKHeX.Core/Legality/Verifiers/BallVerifier.cs

255 lines
11 KiB
C#
Raw Normal View History

Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
using System.Collections.Generic;
using System.Linq;
using static PKHeX.Core.LegalityCheckStrings;
namespace PKHeX.Core
{
public class BallVerifier : Verifier
{
protected override CheckIdentifier Identifier => CheckIdentifier.Ball;
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
private CheckResult NONE => GetInvalid(V125);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
public override void Verify(LegalityAnalysis data)
{
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
if (data.pkm.Format <= 2)
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
return; // no ball info saved
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
var result = VerifyBall(data);
data.AddLine(result);
}
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
private CheckResult VerifyBall(LegalityAnalysis data)
{
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
var EncounterMatch = data.EncounterMatch;
var Info = data.Info;
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
// Fixed ball cases -- can be only one ball ever
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (EncounterMatch is MysteryGift g)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallMysteryGift(data, g);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (EncounterMatch is EncounterLink l)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallEquals(data, l.Ball);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (EncounterMatch is EncounterTrade t)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallEquals(data, t.Ball);
if (EncounterMatch is EncounterStatic s && s.Gift)
return VerifyBallEquals(data, s.Ball);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
// Capture / Inherit cases -- can be one of many balls
var pkm = data.pkm;
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (pkm.Species == 292 && Info.Generation > 3) // Shedinja. For gen3, copy the ball from Nincada
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallEquals(data, 4); // Pokeball Only
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
if (pkm.Ball == 0x14 && Legal.AlolanCaptureNoHeavyBall.Contains(EncounterMatch.Species)
&& !EncounterMatch.EggEncounter && pkm.SM) // Heavy Ball, can inherit if from egg (USUM fixed catch rate calc)
return GetInvalid(V116);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
if (EncounterMatch is EncounterStatic e)
return VerifyBallStatic(data, e);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (EncounterMatch is EncounterSlot w)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallWild(data, w);
if (EncounterMatch is EncounterEgg)
return VerifyBallEgg(data);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallEquals(data, 4); // Pokeball
}
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
private CheckResult VerifyBallMysteryGift(LegalityAnalysis data, MysteryGift g)
{
if (g.Gen4 && g.Species == 490 && g.Ball == 0) // there is no ball data in Manaphy Mystery Gift from Gen4
return VerifyBallEquals(data, 4); // Pokeball
return VerifyBallEquals(data, g.Ball);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
private CheckResult VerifyBallStatic(LegalityAnalysis data, EncounterStatic s)
{
if (s.Location == 75 && s.Generation == 5) // Entree Forest (Dream World)
return VerifyBallEquals(data, Legal.DreamWorldBalls);
return VerifyBallEquals(data, Legal.GetWildBalls(data.pkm));
}
private CheckResult VerifyBallWild(LegalityAnalysis data, EncounterSlot w)
{
if (w.Location == 30016 && w.Generation == 7) // Poké Pelago
return VerifyBallEquals(data, 4); // Pokeball
var Info = data.Info;
// For gen3/4 Safari Zones and BCC getValidWildEncounters already filter to not return
// mixed possible encounters between safari, BCC and other encounters
// That means is the first encounter is not safari then there is no safari encounter in the array
if (3 <= Info.Generation && Info.Generation <= 4 && w.Type.IsSafariType())
return VerifyBallEquals(data, 5); // Safari Ball
if (Info.Generation == 4 && w.Type == SlotType.BugContest)
return VerifyBallEquals(data, 0x18); // Sport Ball
return VerifyBallEquals(data, Legal.GetWildBalls(data.pkm));
}
private CheckResult VerifyBallEgg(LegalityAnalysis data)
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
{
var pkm = data.pkm;
if (data.Info.Generation < 6) // No inheriting Balls
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallEquals(data, 4); // Must be Pokéball -- no ball inheritance.
switch (pkm.Ball)
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
{
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
case 0x04: return GetValid(V119); // Poké Ball
case 0x01: return GetInvalid(V117); // Master Ball
case 0x10: return GetInvalid(V120); // Cherish Ball
default: return VerifyBallInherited(data);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
}
private CheckResult VerifyBallInherited(LegalityAnalysis data)
{
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
switch (data.Info.Generation)
{
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
case 6: return VerifyBallEggGen6(data); // Gen6 Inheritance Rules
case 7: return VerifyBallEggGen7(data); // Gen7 Inheritance Rules
default: return NONE;
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
}
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
private CheckResult VerifyBallEggGen6(LegalityAnalysis data)
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
{
var pkm = data.pkm;
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
if (pkm.Gender == 2 || Legal.BreedMaleOnly.Contains(data.EncounterMatch.Species)) // Genderless
return VerifyBallEquals(data, 4); // Must be Pokéball as ball can only pass via mother (not Ditto!)
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
int ball = pkm.Ball;
if (ball >= 26)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V126);
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
int species = data.EncounterMatch.Species;
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (ball == 0x05) // Safari Ball
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!Legal.Inherit_Safari.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V121);
if (pkm.AbilityNumber == 4)
return GetInvalid(V122);
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (0x10 < ball && ball < 0x18) // Apricorn Ball
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!Legal.Inherit_Apricorn6.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V121);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (pkm.AbilityNumber == 4)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V122);
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (ball == 0x18) // Sport Ball
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!Legal.Inherit_Sport.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V121);
if (pkm.AbilityNumber == 4)
return GetInvalid(V122);
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (ball == 0x19) // Dream Ball
{
if (pkm.AbilityNumber == 4 && Legal.Ban_DreamHidden.Contains(pkm.Species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V122);
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (Legal.Inherit_Dream.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
return GetInvalid(V121);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
if (0x0D <= ball && ball <= 0x0F) // Dusk Heal Quick
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
{
if (!Legal.Ban_Gen4Ball_6.Contains(pkm.Species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
return GetInvalid(V121);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (0x02 <= ball && ball <= 0x0C) // Don't worry, Ball # 0x05 was already checked.
{
if (Legal.Ban_Gen3Ball.Contains(pkm.Species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V121);
if (pkm.AbilityNumber == 4 && Legal.Ban_Gen3BallHidden.Contains(pkm.SpecForm))
return GetInvalid(V122);
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (pkm.Species > 650 && pkm.Species != 700) // Sylveon
{
if (Legal.GetWildBalls(pkm).Contains(pkm.Ball))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
return GetInvalid(V121);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return NONE;
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
private CheckResult VerifyBallEggGen7(LegalityAnalysis data)
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
{
var pkm = data.pkm;
if (722 <= pkm.Species && pkm.Species <= 730) // G7 Starters
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallEquals(data, 4);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
int ball = pkm.Ball;
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
int species = data.EncounterMatch.Species;
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (ball == 0x05) // Safari Ball
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!(Legal.Inherit_Safari.Contains(species) || Legal.Inherit_SafariMale.Contains(species)))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V121);
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (pkm.AbilityNumber == 4 && Legal.Ban_SafariBallHidden_7.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V122);
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (0x10 < ball && ball < 0x18) // Apricorn Ball
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!Legal.Inherit_Apricorn7.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V121);
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (pkm.AbilityNumber == 4 && Legal.Ban_NoHidden7Apricorn.Contains(species | pkm.AltForm << 11)) // lineage is 3->2->origin
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V122);
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (ball == 0x18) // Sport Ball
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!Legal.Inherit_Sport.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V121);
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (pkm.AbilityNumber == 4 && (species == 313) || (species == 314)) // Volbeat/Illumise
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V122);
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (ball == 0x19) // Dream Ball
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (Legal.Inherit_Dream.Contains(species) || Legal.Inherit_DreamMale.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
return GetInvalid(V121);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (0x0D <= ball && ball <= 0x0F) // Dusk Heal Quick
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!Legal.Ban_Gen4Ball_7.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
return GetInvalid(V121);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (0x02 <= ball && ball <= 0x0C) // Don't worry, Ball # 0x05 was already checked.
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (!Legal.Ban_Gen3Ball_7.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
return GetInvalid(V121);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
if (ball == 26)
{
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (species == 669 && pkm.AltForm == 3 && pkm.AbilityNumber == 4)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V122); // Can't obtain Flabébé-Blue with Hidden Ability in wild
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if ((species > 731 && species <= 785) || Legal.PastGenAlolanNatives.Contains(species) && !Legal.PastGenAlolanNativesUncapturable.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
Simplify ball/catchrate lineage checks should speed up egg ball checking a bit since we've already computed the original species gen1 catch rate, just move the chain fetch there.
2018-07-01 17:13:26 +00:00
if (Legal.PastGenAlolanScans.Contains(species))
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetValid(V123);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
// next statement catches all new alolans
}
if (pkm.Species > 721)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return VerifyBallEquals(data, Legal.GetWildBalls(pkm));
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
if (ball >= 27)
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return GetInvalid(V126);
return NONE;
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
private CheckResult VerifyBallEquals(LegalityAnalysis data, int ball) => GetResult(ball == data.pkm.Ball);
private CheckResult VerifyBallEquals(LegalityAnalysis data, ICollection<int> balls) => GetResult(balls.Contains(data.pkm.Ball));
private CheckResult GetResult(bool valid)
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
{
Simplify ball check logic fetch a single result and add it to the analysis can probably remove the GetLineage call since the encountermatch stores the original species
2018-06-30 17:34:09 +00:00
return valid ? GetValid(V119) : GetInvalid(V118);
Rework secondary check flow Checks.cs initially started out small, but over the years it has grown to handle multiple types of checks. With all these checks next to eachother, it's hard to see the overall groups. Splitting them up (potentially further?) allows for more focused maintenance & understanding. Not sure if I'm happy with the overall bandaids used (checks no longer done within LegalityAnalysis so variable repointing is excessively used), but I'm happier the way it is now compared to the huge Checks.cs
2018-06-24 05:00:01 +00:00
}
}
}
Reference in a new issue Copy permalink