Public report of Brionjv/Tomodachi-Life-Save-Editor, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 17:23 UTC · Survey ID cd_9e55d484bd2044659af82b06b76db72d
Brionjv/Tomodachi-Life-Save-Editor
Measured 26 October 2026, 17:22 UTC, at code version 1db5bdf
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Test distribution is not measured: No automated tests.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A very large codebase: 674,821 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 4.1 person-years · Weakest lens: Production Readiness, 12
Findings by how serious they are
47 critical2826 serious41 minor
43 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 17:22 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
32of 32 dimensions measured by tools.
2901of 2914 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
32dimensions across 5 lenses, read from 674,821 lines of product code in 2 projects.
Brionjv/Tomodachi-Life-Save-Editor falls short of our standard for production, in part because the project has no automated tests. It scores 35 out of 100 and is rated Weak, and none of its 47 critical findings concern security.
Production Readiness, at 12, is the weakest lens and counts most in the score. The best first step is adding automated tests, worth about 17 points. Recording design decisions is another step, worth about 14 points. Raising Production Readiness to 70 would lift the score to about 54.
The project has no automated tests, so a change can break it without warning. Forty-six errors are caught and ignored, so failures can go unnoticed. Adding automated tests and handling or logging the ignored errors would close both risks.
The product code is 674,821 lines, about €600,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 12 to 70, the lowest score rated Strong, the score would rise from 35 to about 54.
Code composition: what the lines of code are
Product code 100%
Rebuild cost: about €600,000 · Estimate
Cost to rebuild
€200,000 to €1,000,000, for 3,339 to 10,593 hours of work, about 4.1 person-years for 2 to 8 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 35. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Very large: 674,821 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 17 points · Low effort · Code Coverage
2
Resolve the 1 No tests found finding(s) in Test Distribution.
Raises the score by about 17 points · Low effort · Test Distribution
3
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 14 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €600,000 to build again, about 4.1 person-years of work. Its weakest lens is Production Readiness, at 12 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No automated tests finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 17 points for low effort, because it clears the 1 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.8 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 18% on every change.
How this is estimated: It rests on an assumption of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4)
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
At a glance — Code Health · 75% · Adequate · gated by D1, D2 ·
Begin by establishing foundational testing and documentation practices by resolving the single gaps in code coverage, test distribution, and architectural decision records. Next, address the significant knowledge decay by cleaning up the 29 orphaned files, prioritizing the TLSE_miifoods, TLSE_interactions, and TLSE_miiprofile modules. Finally, institutionalize this discipline by consistently documenting significant design decisions in a dedicated folder to ensure long-term architectural clarity.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.
Per-file score 0–10 — a quality signature. Of 32 files carrying findings, judged against the Production bar: 22% slop · 75% mixed · 3% near-clean.
File
Score
Band
Worst signal
Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb
2.2
Slop
Explicit Debt: EmptyCatchBlock
Version 4.0.0/Tomodachi-Life-Save-Editor/Advanceitemsedit.vb
2.9
Slop
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_hub.vb
2.9
Slop
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_miiprofile.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_dataislandranking.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_datamiiexchange.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_manag_allmiis.vb
3.6
Slop
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_Jrelationships.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_relationships.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_extras.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_interactions.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_miifoods.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_itemsedit.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_miiinventory.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_miistatus.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_travelers_status.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_manag_travelers.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_manag_mii.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_concertedit.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Tomodachi Life Save Editor/TLSE_crcxmodem.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 47
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 2826
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 41
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 43
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 32 of 32 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 32 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2901 of 2914 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D14 License Compliance — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. License scan produced no result — the tool ran but wrote no JSON report (no package reference resolved); the offline NuGet fallback resolved nothing.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 280 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 2 hold 2.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Version 4.0.0/Tomodachi-Life-Save-Editor/Tomodachi-Life-Save-Editor.vbproj' with message: Could not find rule set file "AllRules.ruleset".
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (674,821 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
PF3 Async & latency hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
572 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TL_SaveEditor.Namerelavalu at 5426. A further 102 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being TLSE_miistatus.valu_haircolor_ValueChanged at 65 — they are counted neither in the figure above nor in this dimension's score.
+ 567 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 572 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TL_SaveEditor.Namerelavalu (cyclomatic 5426), TL_SaveEditor.Namerelavalu2 (cyclomatic 5426), TL_SaveEditor.Namerelavalu3 (cyclomatic 5426). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 572 together lifts Cyclomatic Complexity from 0.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 588 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 593 bodies over 15 down to 15 or less in Cognitive Complexity — start with TL_SaveEditor.Namerelavalu (cognitive 7175), TL_SaveEditor.Namerelavalu2 (cognitive 7175), TL_SaveEditor.Namerelavalu3 (cognitive 7175). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 593 together lifts Cognitive Complexity from 0.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.8 / 10Stronggated by 660 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
ClassTooLong: TLSE_dataislandranking · ×9Tomodachi Life Save Editor/TLSE_dataislandranking.vb
What to do
Resolve the 606 MethodTooLong finding(s) in God Classes — start with TLSE_Jrelationships.vb (210), TLSE_relationships.vb (210), Form1.vb (84). — One of this dimension's main actionable groups (606 warning-level).
Resolve the 25 FileTooLong finding(s) in God Classes — start with TLSE_relationships.vb, TLSE_Jrelationships.vb, Form1.vb. — One of this dimension's main actionable groups (25 warning-level).
Resolve the 20 TooManyMethods finding(s) in God Classes — start with Form1.vb, TLSE_relationships.vb, TLSE_Jrelationships.vb. — One of this dimension's main actionable groups (20 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
994 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
Duplicated block (9 lines × 2) · ×605Tomodachi Life Save Editor/TLSE_interactions.vb:5612
Duplicated block (8 lines × 3) · ×200Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20170
Duplicated block (7 lines × 2) · ×101Tomodachi Life Save Editor/TLSE_interactions.vb:5911
Duplicated block (11 lines × 2) · ×7Tomodachi Life Save Editor/TLSE_interactions.vb:6073
Duplicated block (11 lines × 3) · ×4Tomodachi Life Save Editor/TLSE_dataislandranking.vb:857
+ 62 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 605 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with TLSE_Jrelationships.vb (600), TLSE_interactions.vb (2), TLSE_hub.vb. — One of this dimension's main actionable groups (605 warning-level).
Resolve the 200 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with TLSE_Jrelationships.vb (200). — One of this dimension's main actionable groups (200 warning-level).
Resolve the 101 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with TLSE_Jrelationships.vb (100), TLSE_interactions.vb. — One of this dimension's main actionable groups (101 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No automated tests — no test code was found in this repository.
No automated tests
What to do
Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution0.0 / 10Critical✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
46 deducted debt markers + unmeasured dead symbols across 674821 LoC in the .NET projects (0.1/KLoC) → score 9.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
EmptyCatchBlock · ×46Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80026
What to do
Resolve the 46 EmptyCatchBlock finding(s) in Explicit Debt — start with Form1.vb (9), TLSE_hub.vb (3), Advanceitemsedit.vb (3). — One of this dimension's main actionable groups (46 issue-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
2 projects, 37 source files, 674821 hand-written lines of code (674821 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 105024 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges. Measured across 2 solutions loaded as one workspace: `Tomodachi Life Save Editor.sln`, `Version 4.0.0/Tomodachi-Life-Save-Editor.sln`.
✓ On the Gold path — maintain.
Detailed fixes: d18_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
0 of 2 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability7.0 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
99 % of calls cross a namespace and 20 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 7.0/10. — 99 % of calls cross a namespace and 20 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
32 of 32 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Tomodachi Life Save Editor/TLSE_relationships.vb. Counted over 32 of the 37 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×29Tomodachi Life Save Editor/TLSE_miifoods.vb:1
Most significant orphaned file · ×3Tomodachi Life Save Editor/TLSE_relationships.vb:1
Dormant codebase
What to do
Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with TLSE_miifoods.vb, TLSE_interactions.vb, TLSE_miiprofile.vb. — One of this dimension's main actionable groups (29 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with TLSE_relationships.vb, TLSE_Jrelationships.vb, Form1.vb. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
~674.8k production LoC (57 types) across 2 project(s) / 4 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 79 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 2 of 2 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.
For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 80 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D14 License Compliance — Licence collector did not produce a result
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D21 Naming Consistency — Naming consistency is measured on C# only; Visual Basic not measured.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D24 Comment Value — 136 of 136 comment blocks were not judged (136 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Visual Basic code has 679,528 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80026— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_concertedit.vb:119— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_crcxmodem.vb:73— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_creaislandranking.vb:90— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_dataislandranking.vb:192— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1778— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:142— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:978— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_extras.vb:92— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_hub.vb:751— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_hub.vb:862— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_hub.vb:888— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_interactions.vb:592— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_islandconfig.vb:127— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_islandinfo.vb:102— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_islandsettings.vb:93— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_issueslegends.vb:90— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_itemsedit.vb:90— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:91— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_manag_allmiis.vb:98— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_manag_allmiis.vb:644— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_manag_mii.vb:193— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_manag_travelers.vb:143— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_miifoods.vb:100— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Tomodachi Life Save Editor/TLSE_miiinventory.vb:106— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
MethodTooLong: TLSE_Jrelationships.Readfriendlist Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80579— MethodTooLong — Readfriendlist runs 40214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40114 over it, 402.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_relationships.Readfriendlist Tomodachi Life Save Editor/TLSE_relationships.vb:192202— MethodTooLong — Readfriendlist runs 40214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40114 over it, 402.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_Jrelationships.Writefriendlist4 Tomodachi Life Save Editor/TLSE_Jrelationships.vb:165387— MethodTooLong — Writefriendlist4 runs 15674 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15574 over it, 156.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_relationships.Writefriendlist4 Tomodachi Life Save Editor/TLSE_relationships.vb:277010— MethodTooLong — Writefriendlist4 runs 15674 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15574 over it, 156.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_Jrelationships.Writefriendlist2 Tomodachi Life Save Editor/TLSE_Jrelationships.vb:135257— MethodTooLong — Writefriendlist2 runs 15064 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14964 over it, 150.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_Jrelationships.Writefriendlist3 Tomodachi Life Save Editor/TLSE_Jrelationships.vb:150322— MethodTooLong — Writefriendlist3 runs 15064 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14964 over it, 150.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_relationships.Writefriendlist2 Tomodachi Life Save Editor/TLSE_relationships.vb:246880— MethodTooLong — Writefriendlist2 runs 15064 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14964 over it, 150.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_relationships.Writefriendlist3 Tomodachi Life Save Editor/TLSE_relationships.vb:261945— MethodTooLong — Writefriendlist3 runs 15064 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14964 over it, 150.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_Jrelationships.Writefriendlist Tomodachi Life Save Editor/TLSE_Jrelationships.vb:120794— MethodTooLong — Writefriendlist runs 14462 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14362 over it, 144.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_relationships.Writefriendlist Tomodachi Life Save Editor/TLSE_relationships.vb:232417— MethodTooLong — Writefriendlist runs 14462 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14362 over it, 144.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.Namerelavalu Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:53327— MethodTooLong — Namerelavalu runs 11052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10952 over it, 110.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.Namerelavalu2 Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:64405— MethodTooLong — Namerelavalu2 runs 11052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10952 over it, 110.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.Namerelavalu3 Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:75482— MethodTooLong — Namerelavalu3 runs 11052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10952 over it, 110.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.Namerelavalu4 Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:86559— MethodTooLong — Namerelavalu4 runs 11052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10952 over it, 110.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.NamerelavaluUS Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:97636— MethodTooLong — NamerelavaluUS runs 4052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3952 over it, 40.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.NamerelavaluUS2 Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:101689— MethodTooLong — NamerelavaluUS2 runs 4052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3952 over it, 40.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.NamerelavaluUS3 Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:105742— MethodTooLong — NamerelavaluUS3 runs 4052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3952 over it, 40.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.NamerelavaluUS4 Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:109795— MethodTooLong — NamerelavaluUS4 runs 4052 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3952 over it, 40.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TL_SaveEditor.Select_foods_language_SelectedIndexChanged Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:33479— MethodTooLong — Select_foods_language_SelectedIndexChanged runs 3717 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3617 over it, 37.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_miiprofile.Savefileregion Tomodachi Life Save Editor/TLSE_miiprofile.vb:1674— MethodTooLong — Savefileregion runs 3310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3210 over it, 33.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_miiinventory.Savefileregion Tomodachi Life Save Editor/TLSE_miiinventory.vb:3153— MethodTooLong — Savefileregion runs 3207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3107 over it, 32.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_miistatus.Savefileregion Tomodachi Life Save Editor/TLSE_miistatus.vb:1716— MethodTooLong — Savefileregion runs 2807 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2707 over it, 28.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_voicepersonnality.Savefileregion Tomodachi Life Save Editor/TLSE_voicepersonnality.vb:1343— MethodTooLong — Savefileregion runs 2408 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2308 over it, 24.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_travelers_status.Writetravelers Tomodachi Life Save Editor/TLSE_travelers_status.vb:3427— MethodTooLong — Writetravelers runs 2309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2209 over it, 23.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TLSE_Jrelationships.Button_setallrelation_Click Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46585— MethodTooLong — Button_setallrelation_Click runs 2110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2010 over it, 21.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5612— Tomodachi Life Save Editor/TLSE_interactions.vb:5612-5620 | Tomodachi Life Save Editor/TLSE_interactions.vb:5624-5632 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:6043— Tomodachi Life Save Editor/TLSE_interactions.vb:6043-6051 | Tomodachi Life Save Editor/TLSE_interactions.vb:6117-6125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_hub.vb:105— Tomodachi Life Save Editor/TLSE_hub.vb:105-113 | Tomodachi Life Save Editor/TLSE_hub.vb:703-711 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48963— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48963-48971 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48972-48980 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49010— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49010-49018 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49019-49027 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49051— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49051-49059 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49060-49068 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49092— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49092-49100 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49101-49109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49133— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49133-49141 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49142-49150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49174— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49174-49182 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49183-49191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49255— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49255-49263 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49264-49272 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49302— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49302-49310 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49311-49319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49343— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49343-49351 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49352-49360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49384— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49384-49392 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49393-49401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49425— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49425-49433 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49434-49442 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49466— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49466-49474 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49475-49483 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49547— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49547-49555 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49556-49564 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49594— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49594-49602 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49603-49611 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49635— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49635-49643 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49644-49652 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49676— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49676-49684 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49685-49693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49717— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49717-49725 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49726-49734 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49758— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49758-49766 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49767-49775 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49839— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49839-49847 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49848-49856 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49886— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49886-49894 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49895-49903 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49927— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49927-49935 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49936-49944 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49968— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49968-49976 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49977-49985 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20170— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20170-20177 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20178-20185 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20186-20193 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20200— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20200-20207 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20208-20215 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20216-20223 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20199` calls `Select_friend_rela_2_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20207` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20230— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20230-20237 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20238-20245 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20246-20253 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20229` calls `Select_friend_rela_3_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20237` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20260— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20260-20267 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20268-20275 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20276-20283 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20259` calls `Select_friend_rela_4_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20267` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20290— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20290-20297 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20298-20305 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20306-20313 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20289` calls `Select_friend_rela_5_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20297` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20320— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20320-20327 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20328-20335 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20336-20343 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20319` calls `Select_friend_rela_6_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20327` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20350— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20350-20357 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20358-20365 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20366-20373 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20349` calls `Select_friend_rela_7_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20357` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20380— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20380-20387 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20388-20395 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20396-20403 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20379` calls `Select_friend_rela_8_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20387` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20410— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20410-20417 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20418-20425 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20426-20433 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20409` calls `Select_friend_rela_9_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20417` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20440— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20440-20447 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20448-20455 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20456-20463 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20439` calls `Select_friend_rela_10_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20447` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20470— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20470-20477 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20478-20485 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20486-20493 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20469` calls `Select_friend_rela_11_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20477` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20500— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20500-20507 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20508-20515 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20516-20523 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20499` calls `Select_friend_rela_12_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20507` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20530— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20530-20537 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20538-20545 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20546-20553 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20529` calls `Select_friend_rela_13_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20537` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20560— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20560-20567 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20568-20575 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20576-20583 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20559` calls `Select_friend_rela_14_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20567` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20590— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20590-20597 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20598-20605 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20606-20613 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20589` calls `Select_friend_rela_15_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20597` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20620— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20620-20627 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20628-20635 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20636-20643 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20619` calls `Select_friend_rela_16_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20627` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20650— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20650-20657 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20658-20665 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20666-20673 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20649` calls `Select_friend_rela_17_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20657` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20680— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20680-20687 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20688-20695 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20696-20703 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20679` calls `Select_friend_rela_18_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20687` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20710— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20710-20717 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20718-20725 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20726-20733 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20709` calls `Select_friend_rela_19_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20717` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20740— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20740-20747 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20748-20755 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20756-20763 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20739` calls `Select_friend_rela_20_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20747` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20770— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20770-20777 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20778-20785 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20786-20793 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20769` calls `Select_friend_rela_21_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20777` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20800— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20800-20807 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20808-20815 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20816-20823 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20799` calls `Select_friend_rela_22_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20807` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20830— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20830-20837 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20838-20845 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20846-20853 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20829` calls `Select_friend_rela_23_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20837` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20860— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20860-20867 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20868-20875 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20876-20883 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20859` calls `Select_friend_rela_24_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20867` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20890— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20890-20897 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20898-20905 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20906-20913 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20889` calls `Select_friend_rela_25_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20897` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5911— Tomodachi Life Save Editor/TLSE_interactions.vb:5911-5917 | Tomodachi Life Save Editor/TLSE_interactions.vb:6113-6119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48925— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48925-48931 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48934-48940 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49217— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49217-49223 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49226-49232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49509— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49509-49515 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49518-49524 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49801— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49801-49807 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49810-49816 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50093— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50093-50099 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50102-50108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50385— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50385-50391 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50394-50400 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50677— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50677-50683 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50686-50692 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50969— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50969-50975 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50978-50984 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51261— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51261-51267 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51270-51276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51553— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51553-51559 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51562-51568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51845— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51845-51851 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51854-51860 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52137— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52137-52143 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52146-52152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52429— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52429-52435 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52438-52444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52721— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52721-52727 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52730-52736 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53013— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53013-53019 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53022-53028 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53305— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53305-53311 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53314-53320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53597— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53597-53603 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53606-53612 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53889— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53889-53895 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53898-53904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54181— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54181-54187 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54190-54196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54473— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54473-54479 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54482-54488 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54765— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54765-54771 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54774-54780 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55057— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55057-55063 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55066-55072 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55349— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55349-55355 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55358-55364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55641— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55641-55647 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55650-55656 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
FileTooLong: Tomodachi Life Save Editor/TLSE_relationships.vb Tomodachi Life Save Editor/TLSE_relationships.vb— FileTooLong — 292277 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 291777 over it, 584.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_Jrelationships.vb Tomodachi Life Save Editor/TLSE_Jrelationships.vb— FileTooLong — 180656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 180156 over it, 361.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi-Life-Save-Editor/Form1.vb Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb— FileTooLong — 120815 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 120315 over it, 241.63× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_miifoods.vb Tomodachi Life Save Editor/TLSE_miifoods.vb— FileTooLong — 16201 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 15701 over it, 32.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_interactions.vb Tomodachi Life Save Editor/TLSE_interactions.vb— FileTooLong — 12289 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 11789 over it, 24.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_miiinventory.vb Tomodachi Life Save Editor/TLSE_miiinventory.vb— FileTooLong — 6195 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 5695 over it, 12.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_miiprofile.vb Tomodachi Life Save Editor/TLSE_miiprofile.vb— FileTooLong — 5904 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 5404 over it, 11.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_travelers_status.vb Tomodachi Life Save Editor/TLSE_travelers_status.vb— FileTooLong — 5702 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 5202 over it, 11.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_miistatus.vb Tomodachi Life Save Editor/TLSE_miistatus.vb— FileTooLong — 4761 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4261 over it, 9.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_extras.vb Tomodachi Life Save Editor/TLSE_extras.vb— FileTooLong — 4086 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3586 over it, 8.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_voicepersonnality.vb Tomodachi Life Save Editor/TLSE_voicepersonnality.vb— FileTooLong — 3749 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3249 over it, 7.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_itemsedit.vb Tomodachi Life Save Editor/TLSE_itemsedit.vb— FileTooLong — 3341 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2841 over it, 6.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_dataislandranking.vb Tomodachi Life Save Editor/TLSE_dataislandranking.vb— FileTooLong — 2631 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2131 over it, 5.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_manag_mii.vb Tomodachi Life Save Editor/TLSE_manag_mii.vb— FileTooLong — 2134 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1634 over it, 4.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_manag_travelers.vb Tomodachi Life Save Editor/TLSE_manag_travelers.vb— FileTooLong — 1982 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1482 over it, 3.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi-Life-Save-Editor/Advanceitemsedit.vb Version 4.0.0/Tomodachi-Life-Save-Editor/Advanceitemsedit.vb— FileTooLong — 1432 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 932 over it, 2.86× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_datamiiexchange.vb Tomodachi Life Save Editor/TLSE_datamiiexchange.vb— FileTooLong — 1396 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 896 over it, 2.79× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_crcxmodem.vb Tomodachi Life Save Editor/TLSE_crcxmodem.vb— FileTooLong — 1373 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 873 over it, 2.75× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_islandconfig.vb Tomodachi Life Save Editor/TLSE_islandconfig.vb— FileTooLong — 1325 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 825 over it, 2.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_concertedit.vb Tomodachi Life Save Editor/TLSE_concertedit.vb— FileTooLong — 828 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 328 over it, 1.66× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_hub.vb Tomodachi Life Save Editor/TLSE_hub.vb— FileTooLong — 825 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 325 over it, 1.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_islandinfo.vb Tomodachi Life Save Editor/TLSE_islandinfo.vb— FileTooLong — 683 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 183 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_manag_allmiis.vb Tomodachi Life Save Editor/TLSE_manag_allmiis.vb— FileTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 174 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi-Life-Save-Editor/Miimusic_edit.vb Version 4.0.0/Tomodachi-Life-Save-Editor/Miimusic_edit.vb— FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 113 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tomodachi Life Save Editor/TLSE_repairsave.vb Tomodachi Life Save Editor/TLSE_repairsave.vb— FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 110 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: TL_SaveEditor Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb— TooManyMethods — 120811 significant lines (blank, comment-only and punctuation-only lines excluded), 1367 methods. The bar is 30 methods; this is 1337 over it, 45.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_relationships Tomodachi Life Save Editor/TLSE_relationships.vb— TooManyMethods — 292273 significant lines (blank, comment-only and punctuation-only lines excluded), 452 methods. The bar is 30 methods; this is 422 over it, 15.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_Jrelationships Tomodachi Life Save Editor/TLSE_Jrelationships.vb— TooManyMethods — 180654 significant lines (blank, comment-only and punctuation-only lines excluded), 451 methods. The bar is 30 methods; this is 421 over it, 15.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_miiinventory Tomodachi Life Save Editor/TLSE_miiinventory.vb— TooManyMethods — 6191 significant lines (blank, comment-only and punctuation-only lines excluded), 272 methods. The bar is 30 methods; this is 242 over it, 9.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_interactions Tomodachi Life Save Editor/TLSE_interactions.vb— TooManyMethods — 12285 significant lines (blank, comment-only and punctuation-only lines excluded), 238 methods. The bar is 30 methods; this is 208 over it, 7.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_hub Tomodachi Life Save Editor/TLSE_hub.vb— TooManyMethods — 822 significant lines (blank, comment-only and punctuation-only lines excluded), 148 methods. The bar is 30 methods; this is 118 over it, 4.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_miiprofile Tomodachi Life Save Editor/TLSE_miiprofile.vb— TooManyMethods — 5900 significant lines (blank, comment-only and punctuation-only lines excluded), 98 methods. The bar is 30 methods; this is 68 over it, 3.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_itemsedit Tomodachi Life Save Editor/TLSE_itemsedit.vb— TooManyMethods — 3337 significant lines (blank, comment-only and punctuation-only lines excluded), 95 methods. The bar is 30 methods; this is 65 over it, 3.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_islandconfig Tomodachi Life Save Editor/TLSE_islandconfig.vb— TooManyMethods — 1321 significant lines (blank, comment-only and punctuation-only lines excluded), 95 methods. The bar is 30 methods; this is 65 over it, 3.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_miistatus Tomodachi Life Save Editor/TLSE_miistatus.vb— TooManyMethods — 4757 significant lines (blank, comment-only and punctuation-only lines excluded), 90 methods. The bar is 30 methods; this is 60 over it, 3.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Advanceitemsedit Version 4.0.0/Tomodachi-Life-Save-Editor/Advanceitemsedit.vb— TooManyMethods — 1429 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods. The bar is 30 methods; this is 59 over it, 2.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_voicepersonnality Tomodachi Life Save Editor/TLSE_voicepersonnality.vb— TooManyMethods — 3745 significant lines (blank, comment-only and punctuation-only lines excluded), 79 methods. The bar is 30 methods; this is 49 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_settings Tomodachi Life Save Editor/TLSE_settings.vb— TooManyMethods — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_concertedit Tomodachi Life Save Editor/TLSE_concertedit.vb— TooManyMethods — 824 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_islandsettings Tomodachi Life Save Editor/TLSE_islandsettings.vb— TooManyMethods — 475 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_travelers_status Tomodachi Life Save Editor/TLSE_travelers_status.vb— TooManyMethods — 5698 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_miifoods Tomodachi Life Save Editor/TLSE_miifoods.vb— TooManyMethods — 16197 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_islandinfo Tomodachi Life Save Editor/TLSE_islandinfo.vb— TooManyMethods — 679 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_extras Tomodachi Life Save Editor/TLSE_extras.vb— TooManyMethods — 4082 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TLSE_savefilesettings Tomodachi Life Save Editor/TLSE_savefilesettings.vb— TooManyMethods — 344 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_dataislandranking Tomodachi Life Save Editor/TLSE_dataislandranking.vb— ClassTooLong — 2627 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 2227 over it, 6.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_manag_mii Tomodachi Life Save Editor/TLSE_manag_mii.vb— ClassTooLong — 2130 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 1730 over it, 5.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_manag_travelers Tomodachi Life Save Editor/TLSE_manag_travelers.vb— ClassTooLong — 1978 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 1578 over it, 4.95× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_datamiiexchange Tomodachi Life Save Editor/TLSE_datamiiexchange.vb— ClassTooLong — 1392 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 992 over it, 3.48× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_crcxmodem Tomodachi Life Save Editor/TLSE_crcxmodem.vb— ClassTooLong — 1369 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 969 over it, 3.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_manag_allmiis Tomodachi Life Save Editor/TLSE_manag_allmiis.vb— ClassTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 270 over it, 1.68× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Miimusic_edit Version 4.0.0/Tomodachi-Life-Save-Editor/Miimusic_edit.vb— ClassTooLong — 612 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 212 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_repairsave Tomodachi Life Save Editor/TLSE_repairsave.vb— ClassTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 206 over it, 1.52× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TLSE_creaislandranking Tomodachi Life Save Editor/TLSE_creaislandranking.vb— ClassTooLong — 426 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 26 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (11 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:6073— Tomodachi Life Save Editor/TLSE_interactions.vb:6073-6083 | Tomodachi Life Save Editor/TLSE_interactions.vb:6087-6097 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:839— Tomodachi Life Save Editor/TLSE_dataislandranking.vb:839-849 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:489-499 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5509— Tomodachi Life Save Editor/TLSE_interactions.vb:5509-5519 | Tomodachi Life Save Editor/TLSE_interactions.vb:5655-5665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:6053— Tomodachi Life Save Editor/TLSE_interactions.vb:6053-6063 | Tomodachi Life Save Editor/TLSE_interactions.vb:6067-6077 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5719— Tomodachi Life Save Editor/TLSE_interactions.vb:5719-5729 | Tomodachi Life Save Editor/TLSE_interactions.vb:5739-5749 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) Tomodachi Life Save Editor/TLSE_extras.vb:623— Tomodachi Life Save Editor/TLSE_extras.vb:623-633 | Tomodachi Life Save Editor/TLSE_extras.vb:1025-1035 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) Tomodachi Life Save Editor/TLSE_hub.vb:948— Tomodachi Life Save Editor/TLSE_hub.vb:948-958 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:129-139 — before extracting anything, compare `Tomodachi Life Save Editor/TLSE_hub.vb` and `Tomodachi Life Save Editor/TLSE_issueslegends.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:857— Tomodachi Life Save Editor/TLSE_dataislandranking.vb:857-867 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1058-1068 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1259-1269 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:507— Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:507-517 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:608-618 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:709-719 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) Tomodachi Life Save Editor/TLSE_interactions.vb:4993— Tomodachi Life Save Editor/TLSE_interactions.vb:4993-5003 | Tomodachi Life Save Editor/TLSE_interactions.vb:5226-5236 | Tomodachi Life Save Editor/TLSE_interactions.vb:5332-5342 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) Tomodachi Life Save Editor/TLSE_interactions.vb:5523— Tomodachi Life Save Editor/TLSE_interactions.vb:5523-5533 | Tomodachi Life Save Editor/TLSE_interactions.vb:5539-5549 | Tomodachi Life Save Editor/TLSE_interactions.vb:5555-5565 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5450— Tomodachi Life Save Editor/TLSE_interactions.vb:5450-5459 | Tomodachi Life Save Editor/TLSE_interactions.vb:5462-5471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5636— Tomodachi Life Save Editor/TLSE_interactions.vb:5636-5645 | Tomodachi Life Save Editor/TLSE_interactions.vb:5648-5657 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48900— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48900-48909 | Tomodachi Life Save Editor/TLSE_extras.vb:1469-1478 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) Tomodachi Life Save Editor/TLSE_crcxmodem.vb:558— Tomodachi Life Save Editor/TLSE_crcxmodem.vb:558-567 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:962-971 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 58) Tomodachi Life Save Editor/TLSE_interactions.vb:9288— Tomodachi Life Save Editor/TLSE_interactions.vb:9288-9295 | Tomodachi Life Save Editor/TLSE_interactions.vb:9296-9303 | Tomodachi Life Save Editor/TLSE_interactions.vb:9304-9311 | Tomodachi Life Save Editor/TLSE_interactions.vb:9312-9319 | Tomodachi Life Save Editor/TLSE_interactions.vb:9320-9327 | Tomodachi Life Save Editor/TLSE_interactions.vb:9328-9335 | Tomodachi Life Save Editor/TLSE_interactions.vb:9336-9343 | Tomodachi Life Save Editor/TLSE_interactions.vb:9344-9351 | Tomodachi Life Save Editor/TLSE_interactions.vb:9352-9359 | Tomodachi Life Save Editor/TLSE_interactions.vb:9360-9367 | Tomodachi Life Save Editor/TLSE_interactions.vb:9368-9375 | Tomodachi Life Save Editor/TLSE_interactions.vb:9376-9383 | Tomodachi Life Save Editor/TLSE_interactions.vb:9384-9391 | Tomodachi Life Save Editor/TLSE_interactions.vb:9392-9399 | Tomodachi Life Save Editor/TLSE_interactions.vb:9400-9407 | Tomodachi Life Save Editor/TLSE_interactions.vb:9408-9415 | Tomodachi Life Save Editor/TLSE_interactions.vb:9416-9423 | Tomodachi Life Save Editor/TLSE_interactions.vb:9424-9431 | Tomodachi Life Save Editor/TLSE_interactions.vb:9432-9439 | Tomodachi Life Save Editor/TLSE_interactions.vb:9440-9447 | Tomodachi Life Save Editor/TLSE_interactions.vb:9448-9455 | Tomodachi Life Save Editor/TLSE_interactions.vb:9456-9463 | Tomodachi Life Save Editor/TLSE_interactions.vb:9464-9471 | Tomodachi Life Save Editor/TLSE_interactions.vb:9472-9479 | Tomodachi Life Save Editor/TLSE_interactions.vb:9480-9487 | Tomodachi Life Save Editor/TLSE_interactions.vb:9488-9495 | Tomodachi Life Save Editor/TLSE_interactions.vb:9496-9503 | Tomodachi Life Save Editor/TLSE_interactions.vb:9504-9511 | Tomodachi Life Save Editor/TLSE_interactions.vb:9512-9519 | Tomodachi Life Save Editor/TLSE_interactions.vb:9520-9527 | Tomodachi Life Save Editor/TLSE_interactions.vb:9528-9535 | Tomodachi Life Save Editor/TLSE_interactions.vb:9536-9543 | Tomodachi Life Save Editor/TLSE_interactions.vb:9544-9551 | Tomodachi Life Save Editor/TLSE_interactions.vb:9552-9559 | Tomodachi Life Save Editor/TLSE_interactions.vb:9560-9567 | Tomodachi Life Save Editor/TLSE_interactions.vb:9568-9575 | Tomodachi Life Save Editor/TLSE_interactions.vb:9576-9583 | Tomodachi Life Save Editor/TLSE_interactions.vb:9584-9591 | Tomodachi Life Save Editor/TLSE_interactions.vb:9592-9599 | Tomodachi Life Save Editor/TLSE_interactions.vb:9600-9607 | Tomodachi Life Save Editor/TLSE_interactions.vb:9608-9615 | Tomodachi Life Save Editor/TLSE_interactions.vb:9616-9623 | Tomodachi Life Save Editor/TLSE_interactions.vb:9624-9631 | Tomodachi Life Save Editor/TLSE_interactions.vb:9632-9639 | Tomodachi Life Save Editor/TLSE_interactions.vb:9640-9647 | Tomodachi Life Save Editor/TLSE_interactions.vb:9648-9655 | Tomodachi Life Save Editor/TLSE_interactions.vb:9656-9663 | Tomodachi Life Save Editor/TLSE_interactions.vb:9664-9671 | Tomodachi Life Save Editor/TLSE_interactions.vb:9672-9679 | Tomodachi Life Save Editor/TLSE_interactions.vb:9680-9687 | Tomodachi Life Save Editor/TLSE_interactions.vb:9688-9695 | Tomodachi Life Save Editor/TLSE_interactions.vb:9696-9703 | Tomodachi Life Save Editor/TLSE_interactions.vb:9704-9711 | Tomodachi Life Save Editor/TLSE_interactions.vb:9712-9719 | Tomodachi Life Save Editor/TLSE_interactions.vb:9720-9727 | Tomodachi Life Save Editor/TLSE_interactions.vb:9728-9735 | Tomodachi Life Save Editor/TLSE_interactions.vb:9736-9743 | Tomodachi Life Save Editor/TLSE_interactions.vb:9744-9751 — all 58 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 58) Tomodachi Life Save Editor/TLSE_interactions.vb:9754— Tomodachi Life Save Editor/TLSE_interactions.vb:9754-9761 | Tomodachi Life Save Editor/TLSE_interactions.vb:9762-9769 | Tomodachi Life Save Editor/TLSE_interactions.vb:9770-9777 | Tomodachi Life Save Editor/TLSE_interactions.vb:9778-9785 | Tomodachi Life Save Editor/TLSE_interactions.vb:9786-9793 | Tomodachi Life Save Editor/TLSE_interactions.vb:9794-9801 | Tomodachi Life Save Editor/TLSE_interactions.vb:9802-9809 | Tomodachi Life Save Editor/TLSE_interactions.vb:9810-9817 | Tomodachi Life Save Editor/TLSE_interactions.vb:9818-9825 | Tomodachi Life Save Editor/TLSE_interactions.vb:9826-9833 | Tomodachi Life Save Editor/TLSE_interactions.vb:9834-9841 | Tomodachi Life Save Editor/TLSE_interactions.vb:9842-9849 | Tomodachi Life Save Editor/TLSE_interactions.vb:9850-9857 | Tomodachi Life Save Editor/TLSE_interactions.vb:9858-9865 | Tomodachi Life Save Editor/TLSE_interactions.vb:9866-9873 | Tomodachi Life Save Editor/TLSE_interactions.vb:9874-9881 | Tomodachi Life Save Editor/TLSE_interactions.vb:9882-9889 | Tomodachi Life Save Editor/TLSE_interactions.vb:9890-9897 | Tomodachi Life Save Editor/TLSE_interactions.vb:9898-9905 | Tomodachi Life Save Editor/TLSE_interactions.vb:9906-9913 | Tomodachi Life Save Editor/TLSE_interactions.vb:9914-9921 | Tomodachi Life Save Editor/TLSE_interactions.vb:9922-9929 | Tomodachi Life Save Editor/TLSE_interactions.vb:9930-9937 | Tomodachi Life Save Editor/TLSE_interactions.vb:9938-9945 | Tomodachi Life Save Editor/TLSE_interactions.vb:9946-9953 | Tomodachi Life Save Editor/TLSE_interactions.vb:9954-9961 | Tomodachi Life Save Editor/TLSE_interactions.vb:9962-9969 | Tomodachi Life Save Editor/TLSE_interactions.vb:9970-9977 | Tomodachi Life Save Editor/TLSE_interactions.vb:9978-9985 | Tomodachi Life Save Editor/TLSE_interactions.vb:9986-9993 | Tomodachi Life Save Editor/TLSE_interactions.vb:9994-10001 | Tomodachi Life Save Editor/TLSE_interactions.vb:10002-10009 | Tomodachi Life Save Editor/TLSE_interactions.vb:10010-10017 | Tomodachi Life Save Editor/TLSE_interactions.vb:10018-10025 | Tomodachi Life Save Editor/TLSE_interactions.vb:10026-10033 | Tomodachi Life Save Editor/TLSE_interactions.vb:10034-10041 | Tomodachi Life Save Editor/TLSE_interactions.vb:10042-10049 | Tomodachi Life Save Editor/TLSE_interactions.vb:10050-10057 | Tomodachi Life Save Editor/TLSE_interactions.vb:10058-10065 | Tomodachi Life Save Editor/TLSE_interactions.vb:10066-10073 | Tomodachi Life Save Editor/TLSE_interactions.vb:10074-10081 | Tomodachi Life Save Editor/TLSE_interactions.vb:10082-10089 | Tomodachi Life Save Editor/TLSE_interactions.vb:10090-10097 | Tomodachi Life Save Editor/TLSE_interactions.vb:10098-10105 | Tomodachi Life Save Editor/TLSE_interactions.vb:10106-10113 | Tomodachi Life Save Editor/TLSE_interactions.vb:10114-10121 | Tomodachi Life Save Editor/TLSE_interactions.vb:10122-10129 | Tomodachi Life Save Editor/TLSE_interactions.vb:10130-10137 | Tomodachi Life Save Editor/TLSE_interactions.vb:10138-10145 | Tomodachi Life Save Editor/TLSE_interactions.vb:10146-10153 | Tomodachi Life Save Editor/TLSE_interactions.vb:10154-10161 | Tomodachi Life Save Editor/TLSE_interactions.vb:10162-10169 | Tomodachi Life Save Editor/TLSE_interactions.vb:10170-10177 | Tomodachi Life Save Editor/TLSE_interactions.vb:10178-10185 | Tomodachi Life Save Editor/TLSE_interactions.vb:10186-10193 | Tomodachi Life Save Editor/TLSE_interactions.vb:10194-10201 | Tomodachi Life Save Editor/TLSE_interactions.vb:10202-10209 | Tomodachi Life Save Editor/TLSE_interactions.vb:10210-10217 — all 58 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Tomodachi Life Save Editor/TLSE_interactions.vb:10221` calls `valu_target2_ValueChanged` and `Tomodachi Life Save Editor/TLSE_interactions.vb:9762` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 58) Tomodachi Life Save Editor/TLSE_interactions.vb:10428— Tomodachi Life Save Editor/TLSE_interactions.vb:10428-10435 | Tomodachi Life Save Editor/TLSE_interactions.vb:10436-10443 | Tomodachi Life Save Editor/TLSE_interactions.vb:10444-10451 | Tomodachi Life Save Editor/TLSE_interactions.vb:10452-10459 | Tomodachi Life Save Editor/TLSE_interactions.vb:10460-10467 | Tomodachi Life Save Editor/TLSE_interactions.vb:10468-10475 | Tomodachi Life Save Editor/TLSE_interactions.vb:10476-10483 | Tomodachi Life Save Editor/TLSE_interactions.vb:10484-10491 | Tomodachi Life Save Editor/TLSE_interactions.vb:10492-10499 | Tomodachi Life Save Editor/TLSE_interactions.vb:10500-10507 | Tomodachi Life Save Editor/TLSE_interactions.vb:10508-10515 | Tomodachi Life Save Editor/TLSE_interactions.vb:10516-10523 | Tomodachi Life Save Editor/TLSE_interactions.vb:10524-10531 | Tomodachi Life Save Editor/TLSE_interactions.vb:10532-10539 | Tomodachi Life Save Editor/TLSE_interactions.vb:10540-10547 | Tomodachi Life Save Editor/TLSE_interactions.vb:10548-10555 | Tomodachi Life Save Editor/TLSE_interactions.vb:10556-10563 | Tomodachi Life Save Editor/TLSE_interactions.vb:10564-10571 | Tomodachi Life Save Editor/TLSE_interactions.vb:10572-10579 | Tomodachi Life Save Editor/TLSE_interactions.vb:10580-10587 | Tomodachi Life Save Editor/TLSE_interactions.vb:10588-10595 | Tomodachi Life Save Editor/TLSE_interactions.vb:10596-10603 | Tomodachi Life Save Editor/TLSE_interactions.vb:10604-10611 | Tomodachi Life Save Editor/TLSE_interactions.vb:10612-10619 | Tomodachi Life Save Editor/TLSE_interactions.vb:10620-10627 | Tomodachi Life Save Editor/TLSE_interactions.vb:10628-10635 | Tomodachi Life Save Editor/TLSE_interactions.vb:10636-10643 | Tomodachi Life Save Editor/TLSE_interactions.vb:10644-10651 | Tomodachi Life Save Editor/TLSE_interactions.vb:10652-10659 | Tomodachi Life Save Editor/TLSE_interactions.vb:10660-10667 | Tomodachi Life Save Editor/TLSE_interactions.vb:10668-10675 | Tomodachi Life Save Editor/TLSE_interactions.vb:10676-10683 | Tomodachi Life Save Editor/TLSE_interactions.vb:10684-10691 | Tomodachi Life Save Editor/TLSE_interactions.vb:10692-10699 | Tomodachi Life Save Editor/TLSE_interactions.vb:10700-10707 | Tomodachi Life Save Editor/TLSE_interactions.vb:10708-10715 | Tomodachi Life Save Editor/TLSE_interactions.vb:10716-10723 | Tomodachi Life Save Editor/TLSE_interactions.vb:10724-10731 | Tomodachi Life Save Editor/TLSE_interactions.vb:10732-10739 | Tomodachi Life Save Editor/TLSE_interactions.vb:10740-10747 | Tomodachi Life Save Editor/TLSE_interactions.vb:10748-10755 | Tomodachi Life Save Editor/TLSE_interactions.vb:10756-10763 | Tomodachi Life Save Editor/TLSE_interactions.vb:10764-10771 | Tomodachi Life Save Editor/TLSE_interactions.vb:10772-10779 | Tomodachi Life Save Editor/TLSE_interactions.vb:10780-10787 | Tomodachi Life Save Editor/TLSE_interactions.vb:10788-10795 | Tomodachi Life Save Editor/TLSE_interactions.vb:10796-10803 | Tomodachi Life Save Editor/TLSE_interactions.vb:10804-10811 | Tomodachi Life Save Editor/TLSE_interactions.vb:10812-10819 | Tomodachi Life Save Editor/TLSE_interactions.vb:10820-10827 | Tomodachi Life Save Editor/TLSE_interactions.vb:10828-10835 | Tomodachi Life Save Editor/TLSE_interactions.vb:10836-10843 | Tomodachi Life Save Editor/TLSE_interactions.vb:10844-10851 | Tomodachi Life Save Editor/TLSE_interactions.vb:10852-10859 | Tomodachi Life Save Editor/TLSE_interactions.vb:10860-10867 | Tomodachi Life Save Editor/TLSE_interactions.vb:10868-10875 | Tomodachi Life Save Editor/TLSE_interactions.vb:10876-10883 | Tomodachi Life Save Editor/TLSE_interactions.vb:10884-10891 — all 58 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Tomodachi Life Save Editor/TLSE_interactions.vb:10895` calls `Select_target1_foodEU_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_interactions.vb:10436` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 58) Tomodachi Life Save Editor/TLSE_interactions.vb:10896— Tomodachi Life Save Editor/TLSE_interactions.vb:10896-10903 | Tomodachi Life Save Editor/TLSE_interactions.vb:10904-10911 | Tomodachi Life Save Editor/TLSE_interactions.vb:10912-10919 | Tomodachi Life Save Editor/TLSE_interactions.vb:10920-10927 | Tomodachi Life Save Editor/TLSE_interactions.vb:10928-10935 | Tomodachi Life Save Editor/TLSE_interactions.vb:10936-10943 | Tomodachi Life Save Editor/TLSE_interactions.vb:10944-10951 | Tomodachi Life Save Editor/TLSE_interactions.vb:10952-10959 | Tomodachi Life Save Editor/TLSE_interactions.vb:10960-10967 | Tomodachi Life Save Editor/TLSE_interactions.vb:10968-10975 | Tomodachi Life Save Editor/TLSE_interactions.vb:10976-10983 | Tomodachi Life Save Editor/TLSE_interactions.vb:10984-10991 | Tomodachi Life Save Editor/TLSE_interactions.vb:10992-10999 | Tomodachi Life Save Editor/TLSE_interactions.vb:11000-11007 | Tomodachi Life Save Editor/TLSE_interactions.vb:11008-11015 | Tomodachi Life Save Editor/TLSE_interactions.vb:11016-11023 | Tomodachi Life Save Editor/TLSE_interactions.vb:11024-11031 | Tomodachi Life Save Editor/TLSE_interactions.vb:11032-11039 | Tomodachi Life Save Editor/TLSE_interactions.vb:11040-11047 | Tomodachi Life Save Editor/TLSE_interactions.vb:11048-11055 | Tomodachi Life Save Editor/TLSE_interactions.vb:11056-11063 | Tomodachi Life Save Editor/TLSE_interactions.vb:11064-11071 | Tomodachi Life Save Editor/TLSE_interactions.vb:11072-11079 | Tomodachi Life Save Editor/TLSE_interactions.vb:11080-11087 | Tomodachi Life Save Editor/TLSE_interactions.vb:11088-11095 | Tomodachi Life Save Editor/TLSE_interactions.vb:11096-11103 | Tomodachi Life Save Editor/TLSE_interactions.vb:11104-11111 | Tomodachi Life Save Editor/TLSE_interactions.vb:11112-11119 | Tomodachi Life Save Editor/TLSE_interactions.vb:11120-11127 | Tomodachi Life Save Editor/TLSE_interactions.vb:11128-11135 | Tomodachi Life Save Editor/TLSE_interactions.vb:11136-11143 | Tomodachi Life Save Editor/TLSE_interactions.vb:11144-11151 | Tomodachi Life Save Editor/TLSE_interactions.vb:11152-11159 | Tomodachi Life Save Editor/TLSE_interactions.vb:11160-11167 | Tomodachi Life Save Editor/TLSE_interactions.vb:11168-11175 | Tomodachi Life Save Editor/TLSE_interactions.vb:11176-11183 | Tomodachi Life Save Editor/TLSE_interactions.vb:11184-11191 | Tomodachi Life Save Editor/TLSE_interactions.vb:11192-11199 | Tomodachi Life Save Editor/TLSE_interactions.vb:11200-11207 | Tomodachi Life Save Editor/TLSE_interactions.vb:11208-11215 | Tomodachi Life Save Editor/TLSE_interactions.vb:11216-11223 | Tomodachi Life Save Editor/TLSE_interactions.vb:11224-11231 | Tomodachi Life Save Editor/TLSE_interactions.vb:11232-11239 | Tomodachi Life Save Editor/TLSE_interactions.vb:11240-11247 | Tomodachi Life Save Editor/TLSE_interactions.vb:11248-11255 | Tomodachi Life Save Editor/TLSE_interactions.vb:11256-11263 | Tomodachi Life Save Editor/TLSE_interactions.vb:11264-11271 | Tomodachi Life Save Editor/TLSE_interactions.vb:11272-11279 | Tomodachi Life Save Editor/TLSE_interactions.vb:11280-11287 | Tomodachi Life Save Editor/TLSE_interactions.vb:11288-11295 | Tomodachi Life Save Editor/TLSE_interactions.vb:11296-11303 | Tomodachi Life Save Editor/TLSE_interactions.vb:11304-11311 | Tomodachi Life Save Editor/TLSE_interactions.vb:11312-11319 | Tomodachi Life Save Editor/TLSE_interactions.vb:11320-11327 | Tomodachi Life Save Editor/TLSE_interactions.vb:11328-11335 | Tomodachi Life Save Editor/TLSE_interactions.vb:11336-11343 | Tomodachi Life Save Editor/TLSE_interactions.vb:11344-11351 | Tomodachi Life Save Editor/TLSE_interactions.vb:11352-11359 — all 58 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_interactions.vb:10895` calls `Select_target1_foodEU_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_interactions.vb:10903` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 25) Tomodachi Life Save Editor/TLSE_interactions.vb:8673— Tomodachi Life Save Editor/TLSE_interactions.vb:8673-8680 | Tomodachi Life Save Editor/TLSE_interactions.vb:8681-8688 | Tomodachi Life Save Editor/TLSE_interactions.vb:8689-8696 | Tomodachi Life Save Editor/TLSE_interactions.vb:8697-8704 | Tomodachi Life Save Editor/TLSE_interactions.vb:8705-8712 | Tomodachi Life Save Editor/TLSE_interactions.vb:8713-8720 | Tomodachi Life Save Editor/TLSE_interactions.vb:8721-8728 | Tomodachi Life Save Editor/TLSE_interactions.vb:8729-8736 | Tomodachi Life Save Editor/TLSE_interactions.vb:8737-8744 | Tomodachi Life Save Editor/TLSE_interactions.vb:8745-8752 | Tomodachi Life Save Editor/TLSE_interactions.vb:8753-8760 | Tomodachi Life Save Editor/TLSE_interactions.vb:8761-8768 | Tomodachi Life Save Editor/TLSE_interactions.vb:8769-8776 | Tomodachi Life Save Editor/TLSE_interactions.vb:8777-8784 | Tomodachi Life Save Editor/TLSE_interactions.vb:8785-8792 | Tomodachi Life Save Editor/TLSE_interactions.vb:8793-8800 | Tomodachi Life Save Editor/TLSE_interactions.vb:8801-8808 | Tomodachi Life Save Editor/TLSE_interactions.vb:8809-8816 | Tomodachi Life Save Editor/TLSE_interactions.vb:8817-8824 | Tomodachi Life Save Editor/TLSE_interactions.vb:8825-8832 | Tomodachi Life Save Editor/TLSE_interactions.vb:8833-8840 | Tomodachi Life Save Editor/TLSE_interactions.vb:8841-8848 | Tomodachi Life Save Editor/TLSE_interactions.vb:8849-8856 | Tomodachi Life Save Editor/TLSE_interactions.vb:8857-8864 | Tomodachi Life Save Editor/TLSE_interactions.vb:8865-8872 — all 25 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 25) Tomodachi Life Save Editor/TLSE_interactions.vb:8879— Tomodachi Life Save Editor/TLSE_interactions.vb:8879-8886 | Tomodachi Life Save Editor/TLSE_interactions.vb:8887-8894 | Tomodachi Life Save Editor/TLSE_interactions.vb:8895-8902 | Tomodachi Life Save Editor/TLSE_interactions.vb:8903-8910 | Tomodachi Life Save Editor/TLSE_interactions.vb:8911-8918 | Tomodachi Life Save Editor/TLSE_interactions.vb:8919-8926 | Tomodachi Life Save Editor/TLSE_interactions.vb:8927-8934 | Tomodachi Life Save Editor/TLSE_interactions.vb:8935-8942 | Tomodachi Life Save Editor/TLSE_interactions.vb:8943-8950 | Tomodachi Life Save Editor/TLSE_interactions.vb:8951-8958 | Tomodachi Life Save Editor/TLSE_interactions.vb:8959-8966 | Tomodachi Life Save Editor/TLSE_interactions.vb:8967-8974 | Tomodachi Life Save Editor/TLSE_interactions.vb:8975-8982 | Tomodachi Life Save Editor/TLSE_interactions.vb:8983-8990 | Tomodachi Life Save Editor/TLSE_interactions.vb:8991-8998 | Tomodachi Life Save Editor/TLSE_interactions.vb:8999-9006 | Tomodachi Life Save Editor/TLSE_interactions.vb:9007-9014 | Tomodachi Life Save Editor/TLSE_interactions.vb:9015-9022 | Tomodachi Life Save Editor/TLSE_interactions.vb:9023-9030 | Tomodachi Life Save Editor/TLSE_interactions.vb:9031-9038 | Tomodachi Life Save Editor/TLSE_interactions.vb:9039-9046 | Tomodachi Life Save Editor/TLSE_interactions.vb:9047-9054 | Tomodachi Life Save Editor/TLSE_interactions.vb:9055-9062 | Tomodachi Life Save Editor/TLSE_interactions.vb:9063-9070 | Tomodachi Life Save Editor/TLSE_interactions.vb:9071-9078 — all 25 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_interactions.vb:8878` calls `Select_target2_SelectedIndexChanged` and `Tomodachi Life Save Editor/TLSE_interactions.vb:8886` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 25) Tomodachi Life Save Editor/TLSE_interactions.vb:9085— Tomodachi Life Save Editor/TLSE_interactions.vb:9085-9092 | Tomodachi Life Save Editor/TLSE_interactions.vb:9093-9100 | Tomodachi Life Save Editor/TLSE_interactions.vb:9101-9108 | Tomodachi Life Save Editor/TLSE_interactions.vb:9109-9116 | Tomodachi Life Save Editor/TLSE_interactions.vb:9117-9124 | Tomodachi Life Save Editor/TLSE_interactions.vb:9125-9132 | Tomodachi Life Save Editor/TLSE_interactions.vb:9133-9140 | Tomodachi Life Save Editor/TLSE_interactions.vb:9141-9148 | Tomodachi Life Save Editor/TLSE_interactions.vb:9149-9156 | Tomodachi Life Save Editor/TLSE_interactions.vb:9157-9164 | Tomodachi Life Save Editor/TLSE_interactions.vb:9165-9172 | Tomodachi Life Save Editor/TLSE_interactions.vb:9173-9180 | Tomodachi Life Save Editor/TLSE_interactions.vb:9181-9188 | Tomodachi Life Save Editor/TLSE_interactions.vb:9189-9196 | Tomodachi Life Save Editor/TLSE_interactions.vb:9197-9204 | Tomodachi Life Save Editor/TLSE_interactions.vb:9205-9212 | Tomodachi Life Save Editor/TLSE_interactions.vb:9213-9220 | Tomodachi Life Save Editor/TLSE_interactions.vb:9221-9228 | Tomodachi Life Save Editor/TLSE_interactions.vb:9229-9236 | Tomodachi Life Save Editor/TLSE_interactions.vb:9237-9244 | Tomodachi Life Save Editor/TLSE_interactions.vb:9245-9252 | Tomodachi Life Save Editor/TLSE_interactions.vb:9253-9260 | Tomodachi Life Save Editor/TLSE_interactions.vb:9261-9268 | Tomodachi Life Save Editor/TLSE_interactions.vb:9269-9276 | Tomodachi Life Save Editor/TLSE_interactions.vb:9277-9284 — all 25 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 25) Tomodachi Life Save Editor/TLSE_interactions.vb:10222— Tomodachi Life Save Editor/TLSE_interactions.vb:10222-10229 | Tomodachi Life Save Editor/TLSE_interactions.vb:10230-10237 | Tomodachi Life Save Editor/TLSE_interactions.vb:10238-10245 | Tomodachi Life Save Editor/TLSE_interactions.vb:10246-10253 | Tomodachi Life Save Editor/TLSE_interactions.vb:10254-10261 | Tomodachi Life Save Editor/TLSE_interactions.vb:10262-10269 | Tomodachi Life Save Editor/TLSE_interactions.vb:10270-10277 | Tomodachi Life Save Editor/TLSE_interactions.vb:10278-10285 | Tomodachi Life Save Editor/TLSE_interactions.vb:10286-10293 | Tomodachi Life Save Editor/TLSE_interactions.vb:10294-10301 | Tomodachi Life Save Editor/TLSE_interactions.vb:10302-10309 | Tomodachi Life Save Editor/TLSE_interactions.vb:10310-10317 | Tomodachi Life Save Editor/TLSE_interactions.vb:10318-10325 | Tomodachi Life Save Editor/TLSE_interactions.vb:10326-10333 | Tomodachi Life Save Editor/TLSE_interactions.vb:10334-10341 | Tomodachi Life Save Editor/TLSE_interactions.vb:10342-10349 | Tomodachi Life Save Editor/TLSE_interactions.vb:10350-10357 | Tomodachi Life Save Editor/TLSE_interactions.vb:10358-10365 | Tomodachi Life Save Editor/TLSE_interactions.vb:10366-10373 | Tomodachi Life Save Editor/TLSE_interactions.vb:10374-10381 | Tomodachi Life Save Editor/TLSE_interactions.vb:10382-10389 | Tomodachi Life Save Editor/TLSE_interactions.vb:10390-10397 | Tomodachi Life Save Editor/TLSE_interactions.vb:10398-10405 | Tomodachi Life Save Editor/TLSE_interactions.vb:10406-10413 | Tomodachi Life Save Editor/TLSE_interactions.vb:10414-10421 — all 25 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_interactions.vb:10221` calls `valu_target2_ValueChanged` and `Tomodachi Life Save Editor/TLSE_interactions.vb:10229` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 4) Tomodachi Life Save Editor/TLSE_concertedit.vb:643— Tomodachi Life Save Editor/TLSE_concertedit.vb:643-653 | Tomodachi Life Save Editor/TLSE_concertedit.vb:666-676 | Tomodachi Life Save Editor/TLSE_concertedit.vb:680-690 | Tomodachi Life Save Editor/TLSE_concertedit.vb:694-704 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) Tomodachi Life Save Editor/TLSE_itemsedit.vb:702— Tomodachi Life Save Editor/TLSE_itemsedit.vb:702-712 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:905-915 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1100-1110 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1311-1321 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) Tomodachi Life Save Editor/TLSE_itemsedit.vb:2893— Tomodachi Life Save Editor/TLSE_itemsedit.vb:2893-2903 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2964-2974 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3035-3045 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3102-3112 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) Tomodachi Life Save Editor/TLSE_creaislandranking.vb:386— Tomodachi Life Save Editor/TLSE_creaislandranking.vb:386-395 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:410-419 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:425-434 — before extracting anything, compare `Tomodachi Life Save Editor/TLSE_creaislandranking.vb` and `Tomodachi Life Save Editor/TLSE_islandinfo.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80463— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80463-80472 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:1381-1390 | Tomodachi Life Save Editor/TLSE_interactions.vb:4950-4959 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (10 lines × 3) Tomodachi Life Save Editor/TLSE_interactions.vb:5509— Tomodachi Life Save Editor/TLSE_interactions.vb:5509-5518 | Tomodachi Life Save Editor/TLSE_interactions.vb:5643-5652 | Tomodachi Life Save Editor/TLSE_interactions.vb:5655-5664 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) Tomodachi Life Save Editor/TLSE_interactions.vb:5444— Tomodachi Life Save Editor/TLSE_interactions.vb:5444-5452 | Tomodachi Life Save Editor/TLSE_interactions.vb:5842-5850 | Tomodachi Life Save Editor/TLSE_interactions.vb:5884-5892 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48700— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48700-48708 | Tomodachi Life Save Editor/TLSE_extras.vb:1064-1072 | Tomodachi Life Save Editor/TLSE_extras.vb:1267-1275 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) Tomodachi Life Save Editor/TLSE_islandconfig.vb:1412— Tomodachi Life Save Editor/TLSE_islandconfig.vb:1412-1420 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:719-727 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:530-538 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (11 lines × 5) Tomodachi Life Save Editor/TLSE_interactions.vb:5955— Tomodachi Life Save Editor/TLSE_interactions.vb:5955-5965 | Tomodachi Life Save Editor/TLSE_interactions.vb:5975-5985 | Tomodachi Life Save Editor/TLSE_interactions.vb:5995-6005 | Tomodachi Life Save Editor/TLSE_interactions.vb:6015-6025 | Tomodachi Life Save Editor/TLSE_interactions.vb:6035-6045 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 5) Tomodachi Life Save Editor/TLSE_concertedit.vb:643— Tomodachi Life Save Editor/TLSE_concertedit.vb:643-653 | Tomodachi Life Save Editor/TLSE_concertedit.vb:666-676 | Tomodachi Life Save Editor/TLSE_concertedit.vb:680-690 | Tomodachi Life Save Editor/TLSE_concertedit.vb:694-704 | Tomodachi Life Save Editor/TLSE_concertedit.vb:706-716 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5515— Tomodachi Life Save Editor/TLSE_interactions.vb:5515-5527 | Tomodachi Life Save Editor/TLSE_interactions.vb:5531-5543 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5931— Tomodachi Life Save Editor/TLSE_interactions.vb:5931-5943 | Tomodachi Life Save Editor/TLSE_interactions.vb:6123-6135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 4) Tomodachi Life Save Editor/TLSE_interactions.vb:5895— Tomodachi Life Save Editor/TLSE_interactions.vb:5895-5903 | Tomodachi Life Save Editor/TLSE_interactions.vb:5905-5913 | Tomodachi Life Save Editor/TLSE_interactions.vb:5915-5923 | Tomodachi Life Save Editor/TLSE_interactions.vb:5925-5933 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) Tomodachi Life Save Editor/TLSE_itemsedit.vb:527— Tomodachi Life Save Editor/TLSE_itemsedit.vb:527-535 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:714-722 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:917-925 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1112-1120 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 20) Tomodachi Life Save Editor/TLSE_interactions.vb:4750— Tomodachi Life Save Editor/TLSE_interactions.vb:4750-4754 | Tomodachi Life Save Editor/TLSE_interactions.vb:4755-4759 | Tomodachi Life Save Editor/TLSE_interactions.vb:4760-4764 | Tomodachi Life Save Editor/TLSE_interactions.vb:4765-4769 | Tomodachi Life Save Editor/TLSE_interactions.vb:4770-4774 | Tomodachi Life Save Editor/TLSE_interactions.vb:4775-4779 | Tomodachi Life Save Editor/TLSE_interactions.vb:4780-4784 | Tomodachi Life Save Editor/TLSE_interactions.vb:4785-4789 | Tomodachi Life Save Editor/TLSE_interactions.vb:4790-4794 | Tomodachi Life Save Editor/TLSE_interactions.vb:4795-4799 | Tomodachi Life Save Editor/TLSE_interactions.vb:4800-4804 | Tomodachi Life Save Editor/TLSE_interactions.vb:4805-4809 | Tomodachi Life Save Editor/TLSE_interactions.vb:4810-4814 | Tomodachi Life Save Editor/TLSE_interactions.vb:4815-4819 | Tomodachi Life Save Editor/TLSE_interactions.vb:4820-4824 | Tomodachi Life Save Editor/TLSE_interactions.vb:4825-4829 | Tomodachi Life Save Editor/TLSE_interactions.vb:4830-4834 | Tomodachi Life Save Editor/TLSE_interactions.vb:4835-4839 | Tomodachi Life Save Editor/TLSE_interactions.vb:4840-4844 | Tomodachi Life Save Editor/TLSE_interactions.vb:4845-4849 — all 20 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 20) Tomodachi Life Save Editor/TLSE_interactions.vb:4849— Tomodachi Life Save Editor/TLSE_interactions.vb:4849-4853 | Tomodachi Life Save Editor/TLSE_interactions.vb:4854-4858 | Tomodachi Life Save Editor/TLSE_interactions.vb:4859-4863 | Tomodachi Life Save Editor/TLSE_interactions.vb:4864-4868 | Tomodachi Life Save Editor/TLSE_interactions.vb:4869-4873 | Tomodachi Life Save Editor/TLSE_interactions.vb:4874-4878 | Tomodachi Life Save Editor/TLSE_interactions.vb:4879-4883 | Tomodachi Life Save Editor/TLSE_interactions.vb:4884-4888 | Tomodachi Life Save Editor/TLSE_interactions.vb:4889-4893 | Tomodachi Life Save Editor/TLSE_interactions.vb:4894-4898 | Tomodachi Life Save Editor/TLSE_interactions.vb:4899-4903 | Tomodachi Life Save Editor/TLSE_interactions.vb:4904-4908 | Tomodachi Life Save Editor/TLSE_interactions.vb:4909-4913 | Tomodachi Life Save Editor/TLSE_interactions.vb:4914-4918 | Tomodachi Life Save Editor/TLSE_interactions.vb:4919-4923 | Tomodachi Life Save Editor/TLSE_interactions.vb:4924-4928 | Tomodachi Life Save Editor/TLSE_interactions.vb:4929-4933 | Tomodachi Life Save Editor/TLSE_interactions.vb:4934-4938 | Tomodachi Life Save Editor/TLSE_interactions.vb:4939-4943 | Tomodachi Life Save Editor/TLSE_interactions.vb:4944-4948 — all 20 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Appears unstructured (no recognised architecture) — ~674.8k production LoC (57 types) across 2 project(s) / 4 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
TL_SaveEditor.Namerelavalu (cyclomatic 5426) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:53327— TL_SaveEditor.Namerelavalu has cyclomatic complexity 5426 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu2, TL_SaveEditor.Namerelavalu3, TL_SaveEditor.Namerelavalu4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Namerelavalu2 (cyclomatic 5426) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:64405— TL_SaveEditor.Namerelavalu2 has cyclomatic complexity 5426 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu, TL_SaveEditor.Namerelavalu3, TL_SaveEditor.Namerelavalu4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Namerelavalu3 (cyclomatic 5426) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:75482— TL_SaveEditor.Namerelavalu3 has cyclomatic complexity 5426 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu, TL_SaveEditor.Namerelavalu2, TL_SaveEditor.Namerelavalu4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Namerelavalu4 (cyclomatic 5426) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:86559— TL_SaveEditor.Namerelavalu4 has cyclomatic complexity 5426 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu, TL_SaveEditor.Namerelavalu2, TL_SaveEditor.Namerelavalu3) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS (cyclomatic 1926) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:97636— TL_SaveEditor.NamerelavaluUS has cyclomatic complexity 1926 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS2, TL_SaveEditor.NamerelavaluUS3, TL_SaveEditor.NamerelavaluUS4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS2 (cyclomatic 1926) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:101689— TL_SaveEditor.NamerelavaluUS2 has cyclomatic complexity 1926 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS, TL_SaveEditor.NamerelavaluUS3, TL_SaveEditor.NamerelavaluUS4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS3 (cyclomatic 1926) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:105742— TL_SaveEditor.NamerelavaluUS3 has cyclomatic complexity 1926 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS, TL_SaveEditor.NamerelavaluUS2, TL_SaveEditor.NamerelavaluUS4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS4 (cyclomatic 1926) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:109795— TL_SaveEditor.NamerelavaluUS4 has cyclomatic complexity 1926 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS, TL_SaveEditor.NamerelavaluUS2, TL_SaveEditor.NamerelavaluUS3) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Button_setallrelation_Click (cyclomatic 708) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46585— TLSE_Jrelationships.Button_setallrelation_Click has cyclomatic complexity 708 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_relationships.Button_setallrelation_Click (cyclomatic 708) Tomodachi Life Save Editor/TLSE_relationships.vb:46588— TLSE_relationships.Button_setallrelation_Click has cyclomatic complexity 708 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Button_setallrelation_Click (cyclomatic 708) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17736— TL_SaveEditor.Button_setallrelation_Click has cyclomatic complexity 708 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_extras.settummyfullempt (cyclomatic 604) Tomodachi Life Save Editor/TLSE_extras.vb:2499— TLSE_extras.settummyfullempt has cyclomatic complexity 604 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.settummyfullempt (cyclomatic 604) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:7123— TL_SaveEditor.settummyfullempt has cyclomatic complexity 604 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_interactions.valu_target1_ValueChanged (cyclomatic 566) Tomodachi Life Save Editor/TLSE_interactions.vb:9084— TLSE_interactions.valu_target1_ValueChanged has cyclomatic complexity 566 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.valu_target1_ValueChanged (cyclomatic 566) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:27489— TL_SaveEditor.valu_target1_ValueChanged has cyclomatic complexity 566 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_relationships.valu_friend_rela_1_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:48919— TLSE_relationships.valu_friend_rela_1_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, TLSE_relationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_2_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:50327— TLSE_relationships.valu_friend_rela_2_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, TLSE_relationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_3_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:51735— TLSE_relationships.valu_friend_rela_3_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_4_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:53143— TLSE_relationships.valu_friend_rela_4_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_5_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:54551— TLSE_relationships.valu_friend_rela_5_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_6_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:55959— TLSE_relationships.valu_friend_rela_6_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_7_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:57367— TLSE_relationships.valu_friend_rela_7_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_8_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:58775— TLSE_relationships.valu_friend_rela_8_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_9_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:60183— TLSE_relationships.valu_friend_rela_9_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_10_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:61591— TLSE_relationships.valu_friend_rela_10_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_11_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:62999— TLSE_relationships.valu_friend_rela_11_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_12_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:64407— TLSE_relationships.valu_friend_rela_12_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_13_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:65815— TLSE_relationships.valu_friend_rela_13_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_14_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:67223— TLSE_relationships.valu_friend_rela_14_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_15_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:68631— TLSE_relationships.valu_friend_rela_15_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_16_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:70039— TLSE_relationships.valu_friend_rela_16_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_17_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:71447— TLSE_relationships.valu_friend_rela_17_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_18_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:72855— TLSE_relationships.valu_friend_rela_18_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_19_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:74263— TLSE_relationships.valu_friend_rela_19_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_20_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:75671— TLSE_relationships.valu_friend_rela_20_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_21_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:77079— TLSE_relationships.valu_friend_rela_21_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_22_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:78487— TLSE_relationships.valu_friend_rela_22_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_23_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:79895— TLSE_relationships.valu_friend_rela_23_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_24_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:81303— TLSE_relationships.valu_friend_rela_24_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_25_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:82711— TLSE_relationships.valu_friend_rela_25_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_26_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:84119— TLSE_relationships.valu_friend_rela_26_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_27_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:85527— TLSE_relationships.valu_friend_rela_27_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_28_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:86935— TLSE_relationships.valu_friend_rela_28_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_29_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:88343— TLSE_relationships.valu_friend_rela_29_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_30_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:89751— TLSE_relationships.valu_friend_rela_30_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_31_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:91159— TLSE_relationships.valu_friend_rela_31_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_32_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:92567— TLSE_relationships.valu_friend_rela_32_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_33_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:93975— TLSE_relationships.valu_friend_rela_33_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_34_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:95383— TLSE_relationships.valu_friend_rela_34_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_35_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:96791— TLSE_relationships.valu_friend_rela_35_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_36_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:98199— TLSE_relationships.valu_friend_rela_36_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_37_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:99607— TLSE_relationships.valu_friend_rela_37_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_38_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:101015— TLSE_relationships.valu_friend_rela_38_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_39_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:102423— TLSE_relationships.valu_friend_rela_39_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_40_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:103831— TLSE_relationships.valu_friend_rela_40_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_41_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:105239— TLSE_relationships.valu_friend_rela_41_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_42_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:106647— TLSE_relationships.valu_friend_rela_42_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_43_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:108055— TLSE_relationships.valu_friend_rela_43_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_44_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:109463— TLSE_relationships.valu_friend_rela_44_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_45_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:110871— TLSE_relationships.valu_friend_rela_45_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_46_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:112279— TLSE_relationships.valu_friend_rela_46_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_47_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:113687— TLSE_relationships.valu_friend_rela_47_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_48_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:115095— TLSE_relationships.valu_friend_rela_48_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_49_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:116503— TLSE_relationships.valu_friend_rela_49_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_50_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:117911— TLSE_relationships.valu_friend_rela_50_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_51_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:119319— TLSE_relationships.valu_friend_rela_51_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_52_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:120727— TLSE_relationships.valu_friend_rela_52_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_53_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:122135— TLSE_relationships.valu_friend_rela_53_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_54_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:123543— TLSE_relationships.valu_friend_rela_54_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_55_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:124951— TLSE_relationships.valu_friend_rela_55_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_56_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:126359— TLSE_relationships.valu_friend_rela_56_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_57_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:127767— TLSE_relationships.valu_friend_rela_57_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_58_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:129175— TLSE_relationships.valu_friend_rela_58_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_59_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:130583— TLSE_relationships.valu_friend_rela_59_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_60_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:131991— TLSE_relationships.valu_friend_rela_60_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_61_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:133399— TLSE_relationships.valu_friend_rela_61_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_62_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:134807— TLSE_relationships.valu_friend_rela_62_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_63_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:136215— TLSE_relationships.valu_friend_rela_63_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_64_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:137623— TLSE_relationships.valu_friend_rela_64_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_65_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:139031— TLSE_relationships.valu_friend_rela_65_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_66_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:140439— TLSE_relationships.valu_friend_rela_66_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_67_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:141847— TLSE_relationships.valu_friend_rela_67_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_68_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:143255— TLSE_relationships.valu_friend_rela_68_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_69_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:144663— TLSE_relationships.valu_friend_rela_69_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_70_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:146071— TLSE_relationships.valu_friend_rela_70_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_71_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:147479— TLSE_relationships.valu_friend_rela_71_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_72_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:148887— TLSE_relationships.valu_friend_rela_72_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_73_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:150295— TLSE_relationships.valu_friend_rela_73_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_74_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:151703— TLSE_relationships.valu_friend_rela_74_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_75_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:153111— TLSE_relationships.valu_friend_rela_75_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_76_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:154519— TLSE_relationships.valu_friend_rela_76_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_77_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:155927— TLSE_relationships.valu_friend_rela_77_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_78_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:157335— TLSE_relationships.valu_friend_rela_78_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_79_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:158743— TLSE_relationships.valu_friend_rela_79_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_80_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:160151— TLSE_relationships.valu_friend_rela_80_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_81_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:161559— TLSE_relationships.valu_friend_rela_81_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_82_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:162967— TLSE_relationships.valu_friend_rela_82_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_83_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:164375— TLSE_relationships.valu_friend_rela_83_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_84_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:165783— TLSE_relationships.valu_friend_rela_84_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_85_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:167191— TLSE_relationships.valu_friend_rela_85_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_86_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:168599— TLSE_relationships.valu_friend_rela_86_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_87_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:170007— TLSE_relationships.valu_friend_rela_87_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_88_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:171415— TLSE_relationships.valu_friend_rela_88_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_89_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:172823— TLSE_relationships.valu_friend_rela_89_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_90_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:174231— TLSE_relationships.valu_friend_rela_90_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_91_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:175639— TLSE_relationships.valu_friend_rela_91_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_92_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:177047— TLSE_relationships.valu_friend_rela_92_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_93_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:178455— TLSE_relationships.valu_friend_rela_93_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_94_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:179863— TLSE_relationships.valu_friend_rela_94_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_95_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:181271— TLSE_relationships.valu_friend_rela_95_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_96_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:182679— TLSE_relationships.valu_friend_rela_96_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_97_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:184087— TLSE_relationships.valu_friend_rela_97_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_98_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:185495— TLSE_relationships.valu_friend_rela_98_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_99_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:186903— TLSE_relationships.valu_friend_rela_99_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_100_ValueChanged (cyclomatic 560) Tomodachi Life Save Editor/TLSE_relationships.vb:188311— TLSE_relationships.valu_friend_rela_100_ValueChanged has cyclomatic complexity 560 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_fav_1_ValueChanged (cyclomatic 467) Tomodachi Life Save Editor/TLSE_miifoods.vb:6145— TLSE_miifoods.valu_fav_1_ValueChanged has cyclomatic complexity 467 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TLSE_miifoods.valu_fav_2_ValueChanged, TLSE_miifoods.valu_fav_3_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_fav_2_ValueChanged (cyclomatic 467) Tomodachi Life Save Editor/TLSE_miifoods.vb:7086— TLSE_miifoods.valu_fav_2_ValueChanged has cyclomatic complexity 467 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TLSE_miifoods.valu_fav_1_ValueChanged, TLSE_miifoods.valu_fav_3_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_fav_3_ValueChanged (cyclomatic 467) Tomodachi Life Save Editor/TLSE_miifoods.vb:8027— TLSE_miifoods.valu_fav_3_ValueChanged has cyclomatic complexity 467 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TLSE_miifoods.valu_fav_1_ValueChanged, TLSE_miifoods.valu_fav_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_allfav_1_ValueChanged (cyclomatic 465) Tomodachi Life Save Editor/TLSE_miifoods.vb:4271— TLSE_miifoods.valu_allfav_1_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_2_ValueChanged, TLSE_miifoods.valu_worst_1_ValueChanged, TLSE_miifoods.valu_worst_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_allfav_2_ValueChanged (cyclomatic 465) Tomodachi Life Save Editor/TLSE_miifoods.vb:5208— TLSE_miifoods.valu_allfav_2_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_1_ValueChanged, TLSE_miifoods.valu_worst_1_ValueChanged, TLSE_miifoods.valu_worst_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_worst_1_ValueChanged (cyclomatic 465) Tomodachi Life Save Editor/TLSE_miifoods.vb:8968— TLSE_miifoods.valu_worst_1_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_1_ValueChanged, TLSE_miifoods.valu_allfav_2_ValueChanged, TLSE_miifoods.valu_worst_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_worst_2_ValueChanged (cyclomatic 465) Tomodachi Life Save Editor/TLSE_miifoods.vb:9905— TLSE_miifoods.valu_worst_2_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_1_ValueChanged, TLSE_miifoods.valu_allfav_2_ValueChanged, TLSE_miifoods.valu_worst_1_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_allfav_1_ValueChanged (cyclomatic 465) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:40473— TL_SaveEditor.valu_allfav_1_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, TL_SaveEditor.valu_fav_2_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_allfav_2_ValueChanged (cyclomatic 465) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:41407— TL_SaveEditor.valu_allfav_2_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, TL_SaveEditor.valu_fav_2_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_fav_1_ValueChanged (cyclomatic 465) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:42341— TL_SaveEditor.valu_fav_1_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_2_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_fav_2_ValueChanged (cyclomatic 465) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:43275— TL_SaveEditor.valu_fav_2_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_fav_3_ValueChanged (cyclomatic 465) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:44209— TL_SaveEditor.valu_fav_3_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_worst_1_ValueChanged (cyclomatic 465) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:45143— TL_SaveEditor.valu_worst_1_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_worst_2_ValueChanged (cyclomatic 465) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:46077— TL_SaveEditor.valu_worst_2_ValueChanged has cyclomatic complexity 465 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.readfriendlist (cyclomatic 404) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:49416— TL_SaveEditor.readfriendlist has cyclomatic complexity 404 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_itemsedit.Writehatsitems (cyclomatic 332) Tomodachi Life Save Editor/TLSE_itemsedit.vb:1325— TLSE_itemsedit.Writehatsitems has cyclomatic complexity 332 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Writehatsitems (cyclomatic 332) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:10837— TL_SaveEditor.Writehatsitems has cyclomatic complexity 332 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_interactions.Select_target1_foodUS_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_interactions.vb:10427— TLSE_interactions.Select_target1_foodUS_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_interactions.Select_target1_foodEU_SelectedIndexChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.Select_target1_foodEU_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_interactions.vb:10895— TLSE_interactions.Select_target1_foodEU_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_interactions.Select_target1_foodUS_SelectedIndexChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_1_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_miifoods.vb:1935— TLSE_miifoods.Select_fav_1_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, TLSE_miifoods.Select_fav_1US_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_2_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_miifoods.vb:2403— TLSE_miifoods.Select_fav_2_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, TLSE_miifoods.Select_fav_1US_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_3_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_miifoods.vb:2871— TLSE_miifoods.Select_fav_3_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_1US_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_1US_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_miifoods.vb:14855— TLSE_miifoods.Select_fav_1US_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_2US_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_miifoods.vb:15323— TLSE_miifoods.Select_fav_2US_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_3US_SelectedIndexChanged (cyclomatic 233) Tomodachi Life Save Editor/TLSE_miifoods.vb:15791— TLSE_miifoods.Select_fav_3US_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:28832— TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:29300— TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:30203— TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:30671— TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_US1_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:31139— TL_SaveEditor.Select_fav_US1_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_US2_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:31607— TL_SaveEditor.Select_fav_US2_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_US3_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:32075— TL_SaveEditor.Select_fav_US3_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_US1_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:32543— TL_SaveEditor.Select_worst_US1_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_US2_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:33011— TL_SaveEditor.Select_worst_US2_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_1_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:37197— TL_SaveEditor.Select_allfav_1_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_2_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:37665— TL_SaveEditor.Select_allfav_2_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_1_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:38133— TL_SaveEditor.Select_fav_1_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_2_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:38601— TL_SaveEditor.Select_fav_2_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_3_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:39069— TL_SaveEditor.Select_fav_3_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_1_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:39537— TL_SaveEditor.Select_worst_1_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_2_SelectedIndexChanged (cyclomatic 233) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:40005— TL_SaveEditor.Select_worst_2_SelectedIndexChanged has cyclomatic complexity 233 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_1_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:1003— TLSE_miifoods.Select_allfav_1_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, TLSE_miifoods.Select_worst_2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_2_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:1469— TLSE_miifoods.Select_allfav_2_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, TLSE_miifoods.Select_worst_2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_1_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:3339— TLSE_miifoods.Select_worst_1_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_2_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:3805— TLSE_miifoods.Select_worst_2_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_1US_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:12991— TLSE_miifoods.Select_allfav_1US_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_2US_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:13457— TLSE_miifoods.Select_allfav_2US_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_1US_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:13923— TLSE_miifoods.Select_worst_1US_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_2US_SelectedIndexChanged (cyclomatic 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:14389— TLSE_miifoods.Select_worst_2US_SelectedIndexChanged has cyclomatic complexity 232 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_extras.Check_resetmiiapart_CheckedChanged (cyclomatic 210) Tomodachi Life Save Editor/TLSE_extras.vb:227— TLSE_extras.Check_resetmiiapart_CheckedChanged has cyclomatic complexity 210 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_extras.Check_resetrelationship_CheckedChanged (cyclomatic 210) Tomodachi Life Save Editor/TLSE_extras.vb:1551— TLSE_extras.Check_resetrelationship_CheckedChanged has cyclomatic complexity 210 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Readmii (cyclomatic 208) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:48419— TL_SaveEditor.Readmii has cyclomatic complexity 208 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Patchfriendlist (cyclomatic 206) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:51702— TL_SaveEditor.Patchfriendlist has cyclomatic complexity 206 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miiprofile.Savefileregion (cyclomatic 204) Tomodachi Life Save Editor/TLSE_miiprofile.vb:1674— TLSE_miiprofile.Savefileregion has cyclomatic complexity 204 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.resetmiiapart (cyclomatic 204) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:5322— TL_SaveEditor.resetmiiapart has cyclomatic complexity 204 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Resetallrela (cyclomatic 204) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:6169— TL_SaveEditor.Resetallrela has cyclomatic complexity 204 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_crcxmodem.readmiidata (cyclomatic 203) Tomodachi Life Save Editor/TLSE_crcxmodem.vb:163— TLSE_crcxmodem.readmiidata has cyclomatic complexity 203 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_voicepersonnality.Savefileregion (cyclomatic 203) Tomodachi Life Save Editor/TLSE_voicepersonnality.vb:1343— TLSE_voicepersonnality.Savefileregion has cyclomatic complexity 203 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.valu_miiapart_ValueChanged (cyclomatic 203) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:26604— TL_SaveEditor.valu_miiapart_ValueChanged has cyclomatic complexity 203 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miifoods.Savefileregion (cyclomatic 202) Tomodachi Life Save Editor/TLSE_miifoods.vb:10909— TLSE_miifoods.Savefileregion has cyclomatic complexity 202 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miiinventory.Savefileregion (cyclomatic 202) Tomodachi Life Save Editor/TLSE_miiinventory.vb:3153— TLSE_miiinventory.Savefileregion has cyclomatic complexity 202 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miistatus.Savefileregion (cyclomatic 202) Tomodachi Life Save Editor/TLSE_miistatus.vb:1716— TLSE_miistatus.Savefileregion has cyclomatic complexity 202 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_itemsedit.Writessclothesitems (cyclomatic 201) Tomodachi Life Save Editor/TLSE_itemsedit.vb:524— TLSE_itemsedit.Writessclothesitems has cyclomatic complexity 201 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Writessclothesitems (cyclomatic 201) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:10036— TL_SaveEditor.Writessclothesitems has cyclomatic complexity 201 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.WritesavedataArc (cyclomatic 193) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:4160— TL_SaveEditor.WritesavedataArc has cyclomatic complexity 193 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.NamerelavaluJP (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:113848— TL_SaveEditor.NamerelavaluJP has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, TL_SaveEditor.NamerelavaluJP4, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluJP2 (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:114226— TL_SaveEditor.NamerelavaluJP2 has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP3, TL_SaveEditor.NamerelavaluJP4, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluJP3 (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:114604— TL_SaveEditor.NamerelavaluJP3 has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP4, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluJP4 (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:114982— TL_SaveEditor.NamerelavaluJP4 has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:115360— TL_SaveEditor.NamerelavaluKR has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR2 (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:115738— TL_SaveEditor.NamerelavaluKR2 has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR3 (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:116116— TL_SaveEditor.NamerelavaluKR3 has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR4 (cyclomatic 176) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:116494— TL_SaveEditor.NamerelavaluKR4 has cyclomatic complexity 176 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_travelers_status.Writetravelers (cyclomatic 152) Tomodachi Life Save Editor/TLSE_travelers_status.vb:3427— TLSE_travelers_status.Writetravelers has cyclomatic complexity 152 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_interactions.InteractionlistEUR (cyclomatic 146) Tomodachi Life Save Editor/TLSE_interactions.vb:4977— TLSE_interactions.InteractionlistEUR has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_interactions.Select_interaction_SelectedIndexChanged (cyclomatic 146) Tomodachi Life Save Editor/TLSE_interactions.vb:6153— TLSE_interactions.Select_interaction_SelectedIndexChanged has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Select_interaction_SelectedIndexChanged (cyclomatic 146) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:25547— TL_SaveEditor.Select_interaction_SelectedIndexChanged has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged, TL_SaveEditor.InteractionlistEUR, TL_SaveEditor.InteractionlistUSA) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged (cyclomatic 146) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:25841— TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_SelectedIndexChanged, TL_SaveEditor.InteractionlistEUR, TL_SaveEditor.InteractionlistUSA) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.InteractionlistEUR (cyclomatic 146) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:119925— TL_SaveEditor.InteractionlistEUR has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_SelectedIndexChanged, TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged, TL_SaveEditor.InteractionlistUSA) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.InteractionlistUSA (cyclomatic 146) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:121219— TL_SaveEditor.InteractionlistUSA has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_SelectedIndexChanged, TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged, TL_SaveEditor.InteractionlistEUR) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.ReadsavedataArc (cyclomatic 145) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:3348— TL_SaveEditor.ReadsavedataArc has cyclomatic complexity 145 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Danger_interaction_Click (cyclomatic 145) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:29768— TL_SaveEditor.Danger_interaction_Click has cyclomatic complexity 145 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_creaislandranking.Select_spesymb_islandname_SelectedIndexChanged (cyclomatic 115) Tomodachi Life Save Editor/TLSE_creaislandranking.vb:151— TLSE_creaislandranking.Select_spesymb_islandname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_islandinfo.Select_spesymb_islandname_SelectedIndexChanged (cyclomatic 115) Tomodachi Life Save Editor/TLSE_islandinfo.vb:175— TLSE_islandinfo.Select_spesymb_islandname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged (cyclomatic 115) Tomodachi Life Save Editor/TLSE_miiprofile.vb:165— TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged (cyclomatic 115) Tomodachi Life Save Editor/TLSE_miiprofile.vb:443— TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged (cyclomatic 115) Tomodachi Life Save Editor/TLSE_miiprofile.vb:721— TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged (cyclomatic 115) Tomodachi Life Save Editor/TLSE_miiprofile.vb:992— TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged (cyclomatic 115) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:1820— TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged (cyclomatic 115) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:14122— TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged (cyclomatic 115) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:14400— TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged (cyclomatic 115) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:14678— TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged has cyclomatic complexity 115 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23169— TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23400— TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23631— TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23862— TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_5_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24093— TLSE_Jrelationships.valu_selfriend_rela_5_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_6_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24324— TLSE_Jrelationships.valu_selfriend_rela_6_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_7_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24555— TLSE_Jrelationships.valu_selfriend_rela_7_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_8_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24786— TLSE_Jrelationships.valu_selfriend_rela_8_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_9_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25017— TLSE_Jrelationships.valu_selfriend_rela_9_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_10_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25248— TLSE_Jrelationships.valu_selfriend_rela_10_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_11_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25479— TLSE_Jrelationships.valu_selfriend_rela_11_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_12_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25711— TLSE_Jrelationships.valu_selfriend_rela_12_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_13_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25942— TLSE_Jrelationships.valu_selfriend_rela_13_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_14_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26173— TLSE_Jrelationships.valu_selfriend_rela_14_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_15_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26404— TLSE_Jrelationships.valu_selfriend_rela_15_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_16_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26635— TLSE_Jrelationships.valu_selfriend_rela_16_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_17_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26866— TLSE_Jrelationships.valu_selfriend_rela_17_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_18_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27097— TLSE_Jrelationships.valu_selfriend_rela_18_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_19_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27328— TLSE_Jrelationships.valu_selfriend_rela_19_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_20_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27559— TLSE_Jrelationships.valu_selfriend_rela_20_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_21_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27790— TLSE_Jrelationships.valu_selfriend_rela_21_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_22_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28021— TLSE_Jrelationships.valu_selfriend_rela_22_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_23_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28252— TLSE_Jrelationships.valu_selfriend_rela_23_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_24_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28483— TLSE_Jrelationships.valu_selfriend_rela_24_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_25_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28714— TLSE_Jrelationships.valu_selfriend_rela_25_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_26_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28945— TLSE_Jrelationships.valu_selfriend_rela_26_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_27_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29176— TLSE_Jrelationships.valu_selfriend_rela_27_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_28_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29407— TLSE_Jrelationships.valu_selfriend_rela_28_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_29_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29638— TLSE_Jrelationships.valu_selfriend_rela_29_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_30_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29869— TLSE_Jrelationships.valu_selfriend_rela_30_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_31_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30100— TLSE_Jrelationships.valu_selfriend_rela_31_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_32_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30331— TLSE_Jrelationships.valu_selfriend_rela_32_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_33_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30562— TLSE_Jrelationships.valu_selfriend_rela_33_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_34_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30793— TLSE_Jrelationships.valu_selfriend_rela_34_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_35_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31024— TLSE_Jrelationships.valu_selfriend_rela_35_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_36_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31255— TLSE_Jrelationships.valu_selfriend_rela_36_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_37_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31486— TLSE_Jrelationships.valu_selfriend_rela_37_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_38_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31717— TLSE_Jrelationships.valu_selfriend_rela_38_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_39_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31948— TLSE_Jrelationships.valu_selfriend_rela_39_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_40_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32179— TLSE_Jrelationships.valu_selfriend_rela_40_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_41_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32410— TLSE_Jrelationships.valu_selfriend_rela_41_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_42_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32641— TLSE_Jrelationships.valu_selfriend_rela_42_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_43_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32872— TLSE_Jrelationships.valu_selfriend_rela_43_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_44_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33103— TLSE_Jrelationships.valu_selfriend_rela_44_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_45_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33334— TLSE_Jrelationships.valu_selfriend_rela_45_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_46_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33565— TLSE_Jrelationships.valu_selfriend_rela_46_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_47_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33796— TLSE_Jrelationships.valu_selfriend_rela_47_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_48_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34027— TLSE_Jrelationships.valu_selfriend_rela_48_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_49_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34258— TLSE_Jrelationships.valu_selfriend_rela_49_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_50_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34489— TLSE_Jrelationships.valu_selfriend_rela_50_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_51_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34720— TLSE_Jrelationships.valu_selfriend_rela_51_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_52_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34951— TLSE_Jrelationships.valu_selfriend_rela_52_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_53_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35182— TLSE_Jrelationships.valu_selfriend_rela_53_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_54_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35413— TLSE_Jrelationships.valu_selfriend_rela_54_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_55_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35644— TLSE_Jrelationships.valu_selfriend_rela_55_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_56_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35875— TLSE_Jrelationships.valu_selfriend_rela_56_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_57_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36106— TLSE_Jrelationships.valu_selfriend_rela_57_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_58_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36337— TLSE_Jrelationships.valu_selfriend_rela_58_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_59_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36568— TLSE_Jrelationships.valu_selfriend_rela_59_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_60_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36799— TLSE_Jrelationships.valu_selfriend_rela_60_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_61_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37030— TLSE_Jrelationships.valu_selfriend_rela_61_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_62_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37261— TLSE_Jrelationships.valu_selfriend_rela_62_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_63_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37492— TLSE_Jrelationships.valu_selfriend_rela_63_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_64_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37723— TLSE_Jrelationships.valu_selfriend_rela_64_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_65_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37954— TLSE_Jrelationships.valu_selfriend_rela_65_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_66_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38185— TLSE_Jrelationships.valu_selfriend_rela_66_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_67_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38416— TLSE_Jrelationships.valu_selfriend_rela_67_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_68_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38647— TLSE_Jrelationships.valu_selfriend_rela_68_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_69_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38878— TLSE_Jrelationships.valu_selfriend_rela_69_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_70_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39109— TLSE_Jrelationships.valu_selfriend_rela_70_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_71_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39340— TLSE_Jrelationships.valu_selfriend_rela_71_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_72_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39571— TLSE_Jrelationships.valu_selfriend_rela_72_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_73_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39802— TLSE_Jrelationships.valu_selfriend_rela_73_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_74_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40033— TLSE_Jrelationships.valu_selfriend_rela_74_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_75_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40264— TLSE_Jrelationships.valu_selfriend_rela_75_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_76_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40495— TLSE_Jrelationships.valu_selfriend_rela_76_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_77_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40726— TLSE_Jrelationships.valu_selfriend_rela_77_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_78_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40957— TLSE_Jrelationships.valu_selfriend_rela_78_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_79_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41188— TLSE_Jrelationships.valu_selfriend_rela_79_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_80_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41419— TLSE_Jrelationships.valu_selfriend_rela_80_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_81_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41650— TLSE_Jrelationships.valu_selfriend_rela_81_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_82_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41881— TLSE_Jrelationships.valu_selfriend_rela_82_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_83_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42112— TLSE_Jrelationships.valu_selfriend_rela_83_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_84_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42343— TLSE_Jrelationships.valu_selfriend_rela_84_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_85_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42574— TLSE_Jrelationships.valu_selfriend_rela_85_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_86_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42805— TLSE_Jrelationships.valu_selfriend_rela_86_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_87_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43036— TLSE_Jrelationships.valu_selfriend_rela_87_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_88_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43267— TLSE_Jrelationships.valu_selfriend_rela_88_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_89_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43498— TLSE_Jrelationships.valu_selfriend_rela_89_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_90_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43729— TLSE_Jrelationships.valu_selfriend_rela_90_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_91_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43960— TLSE_Jrelationships.valu_selfriend_rela_91_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_92_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44191— TLSE_Jrelationships.valu_selfriend_rela_92_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_93_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44422— TLSE_Jrelationships.valu_selfriend_rela_93_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_94_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44653— TLSE_Jrelationships.valu_selfriend_rela_94_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_95_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44884— TLSE_Jrelationships.valu_selfriend_rela_95_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_96_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45115— TLSE_Jrelationships.valu_selfriend_rela_96_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_97_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45346— TLSE_Jrelationships.valu_selfriend_rela_97_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_98_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45577— TLSE_Jrelationships.valu_selfriend_rela_98_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_99_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45808— TLSE_Jrelationships.valu_selfriend_rela_99_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_100_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46039— TLSE_Jrelationships.valu_selfriend_rela_100_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_1_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23171— TLSE_relationships.valu_selfriend_rela_1_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, TLSE_relationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_2_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23402— TLSE_relationships.valu_selfriend_rela_2_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, TLSE_relationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_3_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23633— TLSE_relationships.valu_selfriend_rela_3_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_4_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23864— TLSE_relationships.valu_selfriend_rela_4_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_5_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24095— TLSE_relationships.valu_selfriend_rela_5_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_6_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24326— TLSE_relationships.valu_selfriend_rela_6_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_7_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24557— TLSE_relationships.valu_selfriend_rela_7_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_8_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24788— TLSE_relationships.valu_selfriend_rela_8_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_9_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25019— TLSE_relationships.valu_selfriend_rela_9_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_10_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25250— TLSE_relationships.valu_selfriend_rela_10_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_11_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25481— TLSE_relationships.valu_selfriend_rela_11_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_12_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25713— TLSE_relationships.valu_selfriend_rela_12_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_13_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25944— TLSE_relationships.valu_selfriend_rela_13_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_14_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26175— TLSE_relationships.valu_selfriend_rela_14_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_15_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26406— TLSE_relationships.valu_selfriend_rela_15_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_16_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26637— TLSE_relationships.valu_selfriend_rela_16_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_17_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26868— TLSE_relationships.valu_selfriend_rela_17_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_18_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27099— TLSE_relationships.valu_selfriend_rela_18_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_19_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27330— TLSE_relationships.valu_selfriend_rela_19_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_20_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27561— TLSE_relationships.valu_selfriend_rela_20_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_21_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27792— TLSE_relationships.valu_selfriend_rela_21_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_22_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28023— TLSE_relationships.valu_selfriend_rela_22_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_23_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28254— TLSE_relationships.valu_selfriend_rela_23_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_24_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28485— TLSE_relationships.valu_selfriend_rela_24_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_25_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28716— TLSE_relationships.valu_selfriend_rela_25_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_26_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28947— TLSE_relationships.valu_selfriend_rela_26_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_27_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29178— TLSE_relationships.valu_selfriend_rela_27_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_28_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29409— TLSE_relationships.valu_selfriend_rela_28_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_29_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29640— TLSE_relationships.valu_selfriend_rela_29_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_30_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29871— TLSE_relationships.valu_selfriend_rela_30_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_31_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30102— TLSE_relationships.valu_selfriend_rela_31_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_32_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30333— TLSE_relationships.valu_selfriend_rela_32_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_33_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30564— TLSE_relationships.valu_selfriend_rela_33_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_34_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30795— TLSE_relationships.valu_selfriend_rela_34_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_35_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31026— TLSE_relationships.valu_selfriend_rela_35_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_36_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31257— TLSE_relationships.valu_selfriend_rela_36_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_37_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31488— TLSE_relationships.valu_selfriend_rela_37_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_38_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31719— TLSE_relationships.valu_selfriend_rela_38_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_39_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31950— TLSE_relationships.valu_selfriend_rela_39_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_40_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32181— TLSE_relationships.valu_selfriend_rela_40_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_41_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32412— TLSE_relationships.valu_selfriend_rela_41_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_42_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32643— TLSE_relationships.valu_selfriend_rela_42_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_43_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32874— TLSE_relationships.valu_selfriend_rela_43_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_44_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33105— TLSE_relationships.valu_selfriend_rela_44_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_45_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33336— TLSE_relationships.valu_selfriend_rela_45_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_46_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33567— TLSE_relationships.valu_selfriend_rela_46_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_47_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33798— TLSE_relationships.valu_selfriend_rela_47_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_48_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34029— TLSE_relationships.valu_selfriend_rela_48_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_49_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34260— TLSE_relationships.valu_selfriend_rela_49_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_50_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34491— TLSE_relationships.valu_selfriend_rela_50_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_51_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34722— TLSE_relationships.valu_selfriend_rela_51_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_52_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34953— TLSE_relationships.valu_selfriend_rela_52_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_53_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35184— TLSE_relationships.valu_selfriend_rela_53_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_54_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35415— TLSE_relationships.valu_selfriend_rela_54_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_55_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35646— TLSE_relationships.valu_selfriend_rela_55_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_56_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35877— TLSE_relationships.valu_selfriend_rela_56_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_57_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36108— TLSE_relationships.valu_selfriend_rela_57_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_58_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36339— TLSE_relationships.valu_selfriend_rela_58_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_59_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36570— TLSE_relationships.valu_selfriend_rela_59_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_60_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36801— TLSE_relationships.valu_selfriend_rela_60_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_61_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37032— TLSE_relationships.valu_selfriend_rela_61_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_62_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37263— TLSE_relationships.valu_selfriend_rela_62_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_63_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37494— TLSE_relationships.valu_selfriend_rela_63_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_64_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37725— TLSE_relationships.valu_selfriend_rela_64_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_65_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37956— TLSE_relationships.valu_selfriend_rela_65_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_66_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38187— TLSE_relationships.valu_selfriend_rela_66_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_67_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38418— TLSE_relationships.valu_selfriend_rela_67_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_68_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38649— TLSE_relationships.valu_selfriend_rela_68_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_69_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38880— TLSE_relationships.valu_selfriend_rela_69_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_70_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39111— TLSE_relationships.valu_selfriend_rela_70_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_71_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39342— TLSE_relationships.valu_selfriend_rela_71_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_72_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39573— TLSE_relationships.valu_selfriend_rela_72_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_73_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39804— TLSE_relationships.valu_selfriend_rela_73_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_74_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40035— TLSE_relationships.valu_selfriend_rela_74_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_75_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40266— TLSE_relationships.valu_selfriend_rela_75_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_76_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40497— TLSE_relationships.valu_selfriend_rela_76_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_77_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40728— TLSE_relationships.valu_selfriend_rela_77_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_78_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40959— TLSE_relationships.valu_selfriend_rela_78_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_79_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41190— TLSE_relationships.valu_selfriend_rela_79_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_80_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41421— TLSE_relationships.valu_selfriend_rela_80_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_81_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41652— TLSE_relationships.valu_selfriend_rela_81_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_82_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41883— TLSE_relationships.valu_selfriend_rela_82_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_83_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42114— TLSE_relationships.valu_selfriend_rela_83_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_84_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42345— TLSE_relationships.valu_selfriend_rela_84_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_85_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42576— TLSE_relationships.valu_selfriend_rela_85_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_86_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42807— TLSE_relationships.valu_selfriend_rela_86_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_87_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43038— TLSE_relationships.valu_selfriend_rela_87_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_88_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43269— TLSE_relationships.valu_selfriend_rela_88_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_89_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43500— TLSE_relationships.valu_selfriend_rela_89_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_90_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43731— TLSE_relationships.valu_selfriend_rela_90_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_91_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43962— TLSE_relationships.valu_selfriend_rela_91_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_92_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44193— TLSE_relationships.valu_selfriend_rela_92_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_93_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44424— TLSE_relationships.valu_selfriend_rela_93_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_94_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44655— TLSE_relationships.valu_selfriend_rela_94_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_95_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44886— TLSE_relationships.valu_selfriend_rela_95_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_96_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45117— TLSE_relationships.valu_selfriend_rela_96_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_97_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45348— TLSE_relationships.valu_selfriend_rela_97_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_98_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45579— TLSE_relationships.valu_selfriend_rela_98_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_99_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45810— TLSE_relationships.valu_selfriend_rela_99_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_100_ValueChanged (cyclomatic 113) Tomodachi Life Save Editor/TLSE_relationships.vb:46041— TLSE_relationships.valu_selfriend_rela_100_ValueChanged has cyclomatic complexity 113 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Readfriendlist (cyclomatic 104) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80579— TLSE_Jrelationships.Readfriendlist has cyclomatic complexity 104 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_relationships.Readfriendlist (cyclomatic 104) Tomodachi Life Save Editor/TLSE_relationships.vb:192202— TLSE_relationships.Readfriendlist has cyclomatic complexity 104 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Miimusic_edit.Miimusic_edit_Load (cyclomatic 104) Version 4.0.0/Tomodachi-Life-Save-Editor/Miimusic_edit.vb:210— Miimusic_edit.Miimusic_edit_Load has cyclomatic complexity 104 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_manag_travelers.Readmiidata (cyclomatic 103) Tomodachi Life Save Editor/TLSE_manag_travelers.vb:413— TLSE_manag_travelers.Readmiidata has cyclomatic complexity 103 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_dataislandranking.Readislandranking (cyclomatic 102) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1782— TLSE_dataislandranking.Readislandranking has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_dataislandranking.RestoreIslandranking) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_dataislandranking.RestoreIslandranking (cyclomatic 102) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:2245— TLSE_dataislandranking.RestoreIslandranking has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_dataislandranking.Readislandranking) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_datamiiexchange.Readislandranking (cyclomatic 102) Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:982— TLSE_datamiiexchange.Readislandranking has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_interactions.Readinteraction (cyclomatic 102) Tomodachi Life Save Editor/TLSE_interactions.vb:7453— TLSE_interactions.Readinteraction has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_interactions.Select_target1_SelectedIndexChanged (cyclomatic 102) Tomodachi Life Save Editor/TLSE_interactions.vb:8672— TLSE_interactions.Select_target1_SelectedIndexChanged has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TLSE_interactions.Select_target2_SelectedIndexChanged, TLSE_interactions.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.Select_target2_SelectedIndexChanged (cyclomatic 102) Tomodachi Life Save Editor/TLSE_interactions.vb:8878— TLSE_interactions.Select_target2_SelectedIndexChanged has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TLSE_interactions.Select_target1_SelectedIndexChanged, TLSE_interactions.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.valu_target2_ValueChanged (cyclomatic 102) Tomodachi Life Save Editor/TLSE_interactions.vb:10221— TLSE_interactions.valu_target2_ValueChanged has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TLSE_interactions.Select_target1_SelectedIndexChanged, TLSE_interactions.Select_target2_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.Writeinteraction (cyclomatic 102) Tomodachi Life Save Editor/TLSE_interactions.vb:11380— TLSE_interactions.Writeinteraction has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_manag_mii.Readmiidata (cyclomatic 102) Tomodachi Life Save Editor/TLSE_manag_mii.vb:670— TLSE_manag_mii.Readmiidata has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_manag_mii.RestoreMii) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_manag_mii.RestoreMii (cyclomatic 102) Tomodachi Life Save Editor/TLSE_manag_mii.vb:1751— TLSE_manag_mii.RestoreMii has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_manag_mii.Readmiidata) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_manag_travelers.RestoreTraveler (cyclomatic 102) Tomodachi Life Save Editor/TLSE_manag_travelers.vb:1042— TLSE_manag_travelers.RestoreTraveler has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Select_target1_SelectedIndexChanged (cyclomatic 102) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:27077— TL_SaveEditor.Select_target1_SelectedIndexChanged has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_target2_SelectedIndexChanged, TL_SaveEditor.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_target2_SelectedIndexChanged (cyclomatic 102) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:27283— TL_SaveEditor.Select_target2_SelectedIndexChanged has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_target1_SelectedIndexChanged, TL_SaveEditor.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_target2_ValueChanged (cyclomatic 102) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:28626— TL_SaveEditor.valu_target2_ValueChanged has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_target1_SelectedIndexChanged, TL_SaveEditor.Select_target2_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Button_setallfriends_Click (cyclomatic 101) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46282— TLSE_Jrelationships.Button_setallfriends_Click has cyclomatic complexity 101 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miistatus.valu_experience_ValueChanged (cyclomatic 101) Tomodachi Life Save Editor/TLSE_miistatus.vb:1339— TLSE_miistatus.valu_experience_ValueChanged has cyclomatic complexity 101 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_relationships.Button_setallfriends_Click (cyclomatic 101) Tomodachi Life Save Editor/TLSE_relationships.vb:46285— TLSE_relationships.Button_setallfriends_Click has cyclomatic complexity 101 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_travelers_status.valu_happiness_ValueChanged (cyclomatic 101) Tomodachi Life Save Editor/TLSE_travelers_status.vb:1231— TLSE_travelers_status.valu_happiness_ValueChanged has cyclomatic complexity 101 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.valu_experience_ValueChanged (cyclomatic 101) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:13803— TL_SaveEditor.valu_experience_ValueChanged has cyclomatic complexity 101 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TL_SaveEditor.Button_setallfriends_Click) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Button_setallfriends_Click (cyclomatic 101) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17433— TL_SaveEditor.Button_setallfriends_Click has cyclomatic complexity 101 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TL_SaveEditor.valu_experience_ValueChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_1_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48916— TLSE_Jrelationships.valu_friend_rela_1_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, TLSE_Jrelationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_2_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49208— TLSE_Jrelationships.valu_friend_rela_2_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, TLSE_Jrelationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_3_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49500— TLSE_Jrelationships.valu_friend_rela_3_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_4_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49792— TLSE_Jrelationships.valu_friend_rela_4_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_5_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50084— TLSE_Jrelationships.valu_friend_rela_5_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_6_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50376— TLSE_Jrelationships.valu_friend_rela_6_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_7_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50668— TLSE_Jrelationships.valu_friend_rela_7_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_8_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50960— TLSE_Jrelationships.valu_friend_rela_8_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_9_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51252— TLSE_Jrelationships.valu_friend_rela_9_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_10_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51544— TLSE_Jrelationships.valu_friend_rela_10_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_11_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51836— TLSE_Jrelationships.valu_friend_rela_11_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_12_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52128— TLSE_Jrelationships.valu_friend_rela_12_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_13_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52420— TLSE_Jrelationships.valu_friend_rela_13_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_14_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52712— TLSE_Jrelationships.valu_friend_rela_14_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_15_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53004— TLSE_Jrelationships.valu_friend_rela_15_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_16_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53296— TLSE_Jrelationships.valu_friend_rela_16_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_17_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53588— TLSE_Jrelationships.valu_friend_rela_17_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_18_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53880— TLSE_Jrelationships.valu_friend_rela_18_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_19_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54172— TLSE_Jrelationships.valu_friend_rela_19_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_20_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54464— TLSE_Jrelationships.valu_friend_rela_20_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_21_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54756— TLSE_Jrelationships.valu_friend_rela_21_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_22_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55048— TLSE_Jrelationships.valu_friend_rela_22_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_23_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55340— TLSE_Jrelationships.valu_friend_rela_23_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_24_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55632— TLSE_Jrelationships.valu_friend_rela_24_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_25_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55924— TLSE_Jrelationships.valu_friend_rela_25_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_26_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:56216— TLSE_Jrelationships.valu_friend_rela_26_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_27_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:56508— TLSE_Jrelationships.valu_friend_rela_27_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_28_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:56800— TLSE_Jrelationships.valu_friend_rela_28_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_29_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57092— TLSE_Jrelationships.valu_friend_rela_29_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_30_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57384— TLSE_Jrelationships.valu_friend_rela_30_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_31_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57676— TLSE_Jrelationships.valu_friend_rela_31_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_32_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57968— TLSE_Jrelationships.valu_friend_rela_32_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_33_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:58260— TLSE_Jrelationships.valu_friend_rela_33_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_34_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:58552— TLSE_Jrelationships.valu_friend_rela_34_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_35_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:58844— TLSE_Jrelationships.valu_friend_rela_35_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_36_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:59136— TLSE_Jrelationships.valu_friend_rela_36_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_37_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:59428— TLSE_Jrelationships.valu_friend_rela_37_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_38_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:59720— TLSE_Jrelationships.valu_friend_rela_38_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_39_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60012— TLSE_Jrelationships.valu_friend_rela_39_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_40_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60304— TLSE_Jrelationships.valu_friend_rela_40_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_41_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60596— TLSE_Jrelationships.valu_friend_rela_41_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_42_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60888— TLSE_Jrelationships.valu_friend_rela_42_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_43_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:61180— TLSE_Jrelationships.valu_friend_rela_43_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_44_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:61472— TLSE_Jrelationships.valu_friend_rela_44_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_45_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:61764— TLSE_Jrelationships.valu_friend_rela_45_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_46_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62056— TLSE_Jrelationships.valu_friend_rela_46_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_47_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62348— TLSE_Jrelationships.valu_friend_rela_47_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_48_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62640— TLSE_Jrelationships.valu_friend_rela_48_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_49_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62932— TLSE_Jrelationships.valu_friend_rela_49_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_50_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:63224— TLSE_Jrelationships.valu_friend_rela_50_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_51_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:63516— TLSE_Jrelationships.valu_friend_rela_51_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_52_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:63808— TLSE_Jrelationships.valu_friend_rela_52_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_53_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64100— TLSE_Jrelationships.valu_friend_rela_53_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_54_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64392— TLSE_Jrelationships.valu_friend_rela_54_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_55_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64684— TLSE_Jrelationships.valu_friend_rela_55_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_56_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64976— TLSE_Jrelationships.valu_friend_rela_56_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_57_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:65268— TLSE_Jrelationships.valu_friend_rela_57_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_58_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:65560— TLSE_Jrelationships.valu_friend_rela_58_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_59_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:65852— TLSE_Jrelationships.valu_friend_rela_59_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_60_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:66144— TLSE_Jrelationships.valu_friend_rela_60_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_61_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:66436— TLSE_Jrelationships.valu_friend_rela_61_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_62_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:66728— TLSE_Jrelationships.valu_friend_rela_62_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_63_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67020— TLSE_Jrelationships.valu_friend_rela_63_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_64_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67312— TLSE_Jrelationships.valu_friend_rela_64_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_65_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67604— TLSE_Jrelationships.valu_friend_rela_65_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_66_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67896— TLSE_Jrelationships.valu_friend_rela_66_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_67_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:68188— TLSE_Jrelationships.valu_friend_rela_67_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_68_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:68480— TLSE_Jrelationships.valu_friend_rela_68_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_69_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:68772— TLSE_Jrelationships.valu_friend_rela_69_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_70_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69064— TLSE_Jrelationships.valu_friend_rela_70_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_71_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69356— TLSE_Jrelationships.valu_friend_rela_71_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_72_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69648— TLSE_Jrelationships.valu_friend_rela_72_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_73_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69940— TLSE_Jrelationships.valu_friend_rela_73_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_74_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:70232— TLSE_Jrelationships.valu_friend_rela_74_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_75_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:70524— TLSE_Jrelationships.valu_friend_rela_75_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_76_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:70816— TLSE_Jrelationships.valu_friend_rela_76_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_77_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71108— TLSE_Jrelationships.valu_friend_rela_77_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_78_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71400— TLSE_Jrelationships.valu_friend_rela_78_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_79_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71692— TLSE_Jrelationships.valu_friend_rela_79_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_80_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71984— TLSE_Jrelationships.valu_friend_rela_80_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_81_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:72276— TLSE_Jrelationships.valu_friend_rela_81_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_82_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:72568— TLSE_Jrelationships.valu_friend_rela_82_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_83_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:72860— TLSE_Jrelationships.valu_friend_rela_83_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_84_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:73152— TLSE_Jrelationships.valu_friend_rela_84_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_85_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:73444— TLSE_Jrelationships.valu_friend_rela_85_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_86_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:73736— TLSE_Jrelationships.valu_friend_rela_86_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_87_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74028— TLSE_Jrelationships.valu_friend_rela_87_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_88_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74320— TLSE_Jrelationships.valu_friend_rela_88_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_89_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74612— TLSE_Jrelationships.valu_friend_rela_89_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_90_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74904— TLSE_Jrelationships.valu_friend_rela_90_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_91_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:75196— TLSE_Jrelationships.valu_friend_rela_91_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_92_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:75488— TLSE_Jrelationships.valu_friend_rela_92_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_93_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:75780— TLSE_Jrelationships.valu_friend_rela_93_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_94_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76072— TLSE_Jrelationships.valu_friend_rela_94_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_95_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76364— TLSE_Jrelationships.valu_friend_rela_95_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_96_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76656— TLSE_Jrelationships.valu_friend_rela_96_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_97_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76948— TLSE_Jrelationships.valu_friend_rela_97_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_98_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:77240— TLSE_Jrelationships.valu_friend_rela_98_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_99_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:77532— TLSE_Jrelationships.valu_friend_rela_99_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_100_ValueChanged (cyclomatic 99) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:77824— TLSE_Jrelationships.valu_friend_rela_100_ValueChanged has cyclomatic complexity 99 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_itemsedit.Writesshatsitems (cyclomatic 74) Tomodachi Life Save Editor/TLSE_itemsedit.vb:2827— TLSE_itemsedit.Writesshatsitems has cyclomatic complexity 74 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Writesshatsitems (cyclomatic 74) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:12339— TL_SaveEditor.Writesshatsitems has cyclomatic complexity 74 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Advanceitemsedit.Checkitems (cyclomatic 55) Version 4.0.0/Tomodachi-Life-Save-Editor/Advanceitemsedit.vb:508— Advanceitemsedit.Checkitems has cyclomatic complexity 55 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_manag_travelers.RestoreMii (cyclomatic 52) Tomodachi Life Save Editor/TLSE_manag_travelers.vb:1603— TLSE_manag_travelers.RestoreMii has cyclomatic complexity 52 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_travelers_status.Readtravelers (cyclomatic 52) Tomodachi Life Save Editor/TLSE_travelers_status.vb:1718— TLSE_travelers_status.Readtravelers has cyclomatic complexity 52 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_concertedit.Select_songs_SelectedIndexChanged (cyclomatic 51) Tomodachi Life Save Editor/TLSE_concertedit.vb:131— TLSE_concertedit.Select_songs_SelectedIndexChanged has cyclomatic complexity 51 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Select_songs_SelectedIndexChanged (cyclomatic 51) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:8786— TL_SaveEditor.Select_songs_SelectedIndexChanged has cyclomatic complexity 51 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_miihouse_SelectedIndexChanged, TL_SaveEditor.valu_miihouse_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.Select_miihouse_SelectedIndexChanged (cyclomatic 51) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:47257— TL_SaveEditor.Select_miihouse_SelectedIndexChanged has cyclomatic complexity 51 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_songs_SelectedIndexChanged, TL_SaveEditor.valu_miihouse_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_miihouse_ValueChanged (cyclomatic 51) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:47361— TL_SaveEditor.valu_miihouse_ValueChanged has cyclomatic complexity 51 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_songs_SelectedIndexChanged, TL_SaveEditor.Select_miihouse_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.Text_save_editsongs_Click (cyclomatic 36) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:9106— TL_SaveEditor.Text_save_editsongs_Click has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TLSE_concertedit.Text_save_editsongs_Click (cyclomatic 33) Tomodachi Life Save Editor/TLSE_concertedit.vb:439— TLSE_concertedit.Text_save_editsongs_Click has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Miimusic_edit.Text_save_Click (cyclomatic 33) Version 4.0.0/Tomodachi-Life-Save-Editor/Miimusic_edit.vb:469— Miimusic_edit.Text_save_Click has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_Jrelationships.Writefriendlist4 (cyclomatic 32) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:165387— TLSE_Jrelationships.Writefriendlist4 has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_relationships.Writefriendlist4 (cyclomatic 32) Tomodachi Life Save Editor/TLSE_relationships.vb:277010— TLSE_relationships.Writefriendlist4 has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_itemsedit.Text_menu_save_Click (cyclomatic 31) Tomodachi Life Save Editor/TLSE_itemsedit.vb:3504— TLSE_itemsedit.Text_menu_save_Click has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miiinventory.valu_itemmii_1_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2657— TLSE_miiinventory.valu_itemmii_1_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, TLSE_miiinventory.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_2_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2719— TLSE_miiinventory.valu_itemmii_2_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, TLSE_miiinventory.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_3_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2781— TLSE_miiinventory.valu_itemmii_3_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_4_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2843— TLSE_miiinventory.valu_itemmii_4_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_5_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2905— TLSE_miiinventory.valu_itemmii_5_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_6_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2967— TLSE_miiinventory.valu_itemmii_6_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_7_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:3029— TLSE_miiinventory.valu_itemmii_7_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_8_ValueChanged (cyclomatic 30) Tomodachi Life Save Editor/TLSE_miiinventory.vb:3091— TLSE_miiinventory.valu_itemmii_8_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_1_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:16844— TL_SaveEditor.valu_itemmii_1_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, TL_SaveEditor.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_itemmii_2_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:16906— TL_SaveEditor.valu_itemmii_2_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, TL_SaveEditor.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_itemmii_3_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:16968— TL_SaveEditor.valu_itemmii_3_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_itemmii_4_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17030— TL_SaveEditor.valu_itemmii_4_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_itemmii_5_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17092— TL_SaveEditor.valu_itemmii_5_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_itemmii_6_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17154— TL_SaveEditor.valu_itemmii_6_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_itemmii_7_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17216— TL_SaveEditor.valu_itemmii_7_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TL_SaveEditor.valu_itemmii_8_ValueChanged (cyclomatic 30) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17278— TL_SaveEditor.valu_itemmii_8_ValueChanged has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TLSE_Jrelationships.Writefriendlist2 (cyclomatic 29) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:135257— TLSE_Jrelationships.Writefriendlist2 has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_Jrelationships.Writefriendlist3) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Writefriendlist3 (cyclomatic 29) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:150322— TLSE_Jrelationships.Writefriendlist3 has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_Jrelationships.Writefriendlist2) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.Writefriendlist2 (cyclomatic 29) Tomodachi Life Save Editor/TLSE_relationships.vb:246880— TLSE_relationships.Writefriendlist2 has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_relationships.Writefriendlist3) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.Writefriendlist3 (cyclomatic 29) Tomodachi Life Save Editor/TLSE_relationships.vb:261945— TLSE_relationships.Writefriendlist3 has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This shape REPEATS in the file: one other method here (TLSE_relationships.Writefriendlist2) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Writemii (cyclomatic 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:51383— TL_SaveEditor.Writemii has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: TL_SaveEditor.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TLSE_Jrelationships.Writefriendlist (cyclomatic 28) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:120794— TLSE_Jrelationships.Writefriendlist has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_relationships.Writefriendlist (cyclomatic 28) Tomodachi Life Save Editor/TLSE_relationships.vb:232417— TLSE_relationships.Writefriendlist has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_extras.Check_timetravel_CheckedChanged (cyclomatic 23) Tomodachi Life Save Editor/TLSE_extras.vb:123— TLSE_extras.Check_timetravel_CheckedChanged has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TLSE_miistatus.Writemiistatus (cyclomatic 17) Tomodachi Life Save Editor/TLSE_miistatus.vb:4585— TLSE_miistatus.Writemiistatus has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: TLSE_miistatus.valu_haircolor_ValueChanged (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TLSE_extras.Check_resetnewsflash_CheckedChanged (cyclomatic 16) Tomodachi Life Save Editor/TLSE_extras.vb:1481— TLSE_extras.Check_resetnewsflash_CheckedChanged has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TL_SaveEditor.Namerelavalu (cognitive 7175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:53327— TL_SaveEditor.Namerelavalu has cognitive complexity 7175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu2, TL_SaveEditor.Namerelavalu3, TL_SaveEditor.Namerelavalu4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Namerelavalu2 (cognitive 7175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:64405— TL_SaveEditor.Namerelavalu2 has cognitive complexity 7175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu, TL_SaveEditor.Namerelavalu3, TL_SaveEditor.Namerelavalu4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Namerelavalu3 (cognitive 7175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:75482— TL_SaveEditor.Namerelavalu3 has cognitive complexity 7175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu, TL_SaveEditor.Namerelavalu2, TL_SaveEditor.Namerelavalu4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Namerelavalu4 (cognitive 7175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:86559— TL_SaveEditor.Namerelavalu4 has cognitive complexity 7175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Namerelavalu, TL_SaveEditor.Namerelavalu2, TL_SaveEditor.Namerelavalu3) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS (cognitive 1925) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:97636— TL_SaveEditor.NamerelavaluUS has cognitive complexity 1925 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS2, TL_SaveEditor.NamerelavaluUS3, TL_SaveEditor.NamerelavaluUS4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS2 (cognitive 1925) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:101689— TL_SaveEditor.NamerelavaluUS2 has cognitive complexity 1925 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS, TL_SaveEditor.NamerelavaluUS3, TL_SaveEditor.NamerelavaluUS4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS3 (cognitive 1925) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:105742— TL_SaveEditor.NamerelavaluUS3 has cognitive complexity 1925 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS, TL_SaveEditor.NamerelavaluUS2, TL_SaveEditor.NamerelavaluUS4) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluUS4 (cognitive 1925) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:109795— TL_SaveEditor.NamerelavaluUS4 has cognitive complexity 1925 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.NamerelavaluUS, TL_SaveEditor.NamerelavaluUS2, TL_SaveEditor.NamerelavaluUS3) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_extras.settummyfullempt (cognitive 1604) Tomodachi Life Save Editor/TLSE_extras.vb:2499— TLSE_extras.settummyfullempt has cognitive complexity 1604 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.settummyfullempt (cognitive 1604) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:7123— TL_SaveEditor.settummyfullempt has cognitive complexity 1604 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_relationships.valu_friend_rela_1_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:48919— TLSE_relationships.valu_friend_rela_1_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, TLSE_relationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_2_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:50327— TLSE_relationships.valu_friend_rela_2_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, TLSE_relationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_3_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:51735— TLSE_relationships.valu_friend_rela_3_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_4_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:53143— TLSE_relationships.valu_friend_rela_4_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_5_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:54551— TLSE_relationships.valu_friend_rela_5_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_6_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:55959— TLSE_relationships.valu_friend_rela_6_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_7_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:57367— TLSE_relationships.valu_friend_rela_7_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_8_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:58775— TLSE_relationships.valu_friend_rela_8_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_9_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:60183— TLSE_relationships.valu_friend_rela_9_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_10_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:61591— TLSE_relationships.valu_friend_rela_10_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_11_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:62999— TLSE_relationships.valu_friend_rela_11_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_12_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:64407— TLSE_relationships.valu_friend_rela_12_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_13_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:65815— TLSE_relationships.valu_friend_rela_13_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_14_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:67223— TLSE_relationships.valu_friend_rela_14_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_15_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:68631— TLSE_relationships.valu_friend_rela_15_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_16_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:70039— TLSE_relationships.valu_friend_rela_16_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_17_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:71447— TLSE_relationships.valu_friend_rela_17_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_18_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:72855— TLSE_relationships.valu_friend_rela_18_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_19_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:74263— TLSE_relationships.valu_friend_rela_19_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_20_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:75671— TLSE_relationships.valu_friend_rela_20_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_21_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:77079— TLSE_relationships.valu_friend_rela_21_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_22_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:78487— TLSE_relationships.valu_friend_rela_22_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_23_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:79895— TLSE_relationships.valu_friend_rela_23_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_24_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:81303— TLSE_relationships.valu_friend_rela_24_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_25_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:82711— TLSE_relationships.valu_friend_rela_25_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_26_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:84119— TLSE_relationships.valu_friend_rela_26_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_27_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:85527— TLSE_relationships.valu_friend_rela_27_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_28_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:86935— TLSE_relationships.valu_friend_rela_28_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_29_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:88343— TLSE_relationships.valu_friend_rela_29_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_30_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:89751— TLSE_relationships.valu_friend_rela_30_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_31_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:91159— TLSE_relationships.valu_friend_rela_31_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_32_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:92567— TLSE_relationships.valu_friend_rela_32_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_33_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:93975— TLSE_relationships.valu_friend_rela_33_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_34_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:95383— TLSE_relationships.valu_friend_rela_34_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_35_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:96791— TLSE_relationships.valu_friend_rela_35_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_36_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:98199— TLSE_relationships.valu_friend_rela_36_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_37_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:99607— TLSE_relationships.valu_friend_rela_37_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_38_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:101015— TLSE_relationships.valu_friend_rela_38_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_39_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:102423— TLSE_relationships.valu_friend_rela_39_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_40_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:103831— TLSE_relationships.valu_friend_rela_40_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_41_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:105239— TLSE_relationships.valu_friend_rela_41_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_42_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:106647— TLSE_relationships.valu_friend_rela_42_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_43_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:108055— TLSE_relationships.valu_friend_rela_43_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_44_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:109463— TLSE_relationships.valu_friend_rela_44_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_45_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:110871— TLSE_relationships.valu_friend_rela_45_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_46_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:112279— TLSE_relationships.valu_friend_rela_46_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_47_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:113687— TLSE_relationships.valu_friend_rela_47_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_48_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:115095— TLSE_relationships.valu_friend_rela_48_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_49_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:116503— TLSE_relationships.valu_friend_rela_49_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_50_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:117911— TLSE_relationships.valu_friend_rela_50_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_51_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:119319— TLSE_relationships.valu_friend_rela_51_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_52_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:120727— TLSE_relationships.valu_friend_rela_52_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_53_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:122135— TLSE_relationships.valu_friend_rela_53_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_54_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:123543— TLSE_relationships.valu_friend_rela_54_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_55_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:124951— TLSE_relationships.valu_friend_rela_55_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_56_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:126359— TLSE_relationships.valu_friend_rela_56_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_57_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:127767— TLSE_relationships.valu_friend_rela_57_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_58_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:129175— TLSE_relationships.valu_friend_rela_58_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_59_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:130583— TLSE_relationships.valu_friend_rela_59_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_60_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:131991— TLSE_relationships.valu_friend_rela_60_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_61_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:133399— TLSE_relationships.valu_friend_rela_61_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_62_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:134807— TLSE_relationships.valu_friend_rela_62_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_63_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:136215— TLSE_relationships.valu_friend_rela_63_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_64_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:137623— TLSE_relationships.valu_friend_rela_64_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_65_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:139031— TLSE_relationships.valu_friend_rela_65_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_66_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:140439— TLSE_relationships.valu_friend_rela_66_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_67_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:141847— TLSE_relationships.valu_friend_rela_67_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_68_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:143255— TLSE_relationships.valu_friend_rela_68_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_69_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:144663— TLSE_relationships.valu_friend_rela_69_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_70_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:146071— TLSE_relationships.valu_friend_rela_70_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_71_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:147479— TLSE_relationships.valu_friend_rela_71_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_72_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:148887— TLSE_relationships.valu_friend_rela_72_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_73_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:150295— TLSE_relationships.valu_friend_rela_73_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_74_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:151703— TLSE_relationships.valu_friend_rela_74_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_75_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:153111— TLSE_relationships.valu_friend_rela_75_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_76_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:154519— TLSE_relationships.valu_friend_rela_76_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_77_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:155927— TLSE_relationships.valu_friend_rela_77_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_78_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:157335— TLSE_relationships.valu_friend_rela_78_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_79_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:158743— TLSE_relationships.valu_friend_rela_79_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_80_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:160151— TLSE_relationships.valu_friend_rela_80_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_81_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:161559— TLSE_relationships.valu_friend_rela_81_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_82_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:162967— TLSE_relationships.valu_friend_rela_82_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_83_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:164375— TLSE_relationships.valu_friend_rela_83_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_84_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:165783— TLSE_relationships.valu_friend_rela_84_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_85_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:167191— TLSE_relationships.valu_friend_rela_85_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_86_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:168599— TLSE_relationships.valu_friend_rela_86_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_87_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:170007— TLSE_relationships.valu_friend_rela_87_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_88_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:171415— TLSE_relationships.valu_friend_rela_88_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_89_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:172823— TLSE_relationships.valu_friend_rela_89_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_90_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:174231— TLSE_relationships.valu_friend_rela_90_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_91_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:175639— TLSE_relationships.valu_friend_rela_91_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_92_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:177047— TLSE_relationships.valu_friend_rela_92_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_93_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:178455— TLSE_relationships.valu_friend_rela_93_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_94_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:179863— TLSE_relationships.valu_friend_rela_94_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_95_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:181271— TLSE_relationships.valu_friend_rela_95_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_96_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:182679— TLSE_relationships.valu_friend_rela_96_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_97_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:184087— TLSE_relationships.valu_friend_rela_97_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_98_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:185495— TLSE_relationships.valu_friend_rela_98_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_99_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:186903— TLSE_relationships.valu_friend_rela_99_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_friend_rela_100_ValueChanged (cognitive 1475) Tomodachi Life Save Editor/TLSE_relationships.vb:188311— TLSE_relationships.valu_friend_rela_100_ValueChanged has cognitive complexity 1475 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_friend_rela_1_ValueChanged, TLSE_relationships.valu_friend_rela_2_ValueChanged, TLSE_relationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Button_setallrelation_Click (cognitive 1407) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46585— TLSE_Jrelationships.Button_setallrelation_Click has cognitive complexity 1407 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_relationships.Button_setallrelation_Click (cognitive 1407) Tomodachi Life Save Editor/TLSE_relationships.vb:46588— TLSE_relationships.Button_setallrelation_Click has cognitive complexity 1407 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Button_setallrelation_Click (cognitive 1407) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17736— TL_SaveEditor.Button_setallrelation_Click has cognitive complexity 1407 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_itemsedit.Writehatsitems (cognitive 987) Tomodachi Life Save Editor/TLSE_itemsedit.vb:1325— TLSE_itemsedit.Writehatsitems has cognitive complexity 987 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Writehatsitems (cognitive 987) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:10837— TL_SaveEditor.Writehatsitems has cognitive complexity 987 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_extras.Check_resetmiiapart_CheckedChanged (cognitive 816) Tomodachi Life Save Editor/TLSE_extras.vb:227— TLSE_extras.Check_resetmiiapart_CheckedChanged has cognitive complexity 816 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_extras.Check_resetrelationship_CheckedChanged (cognitive 616) Tomodachi Life Save Editor/TLSE_extras.vb:1551— TLSE_extras.Check_resetrelationship_CheckedChanged has cognitive complexity 616 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.resetmiiapart (cognitive 604) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:5322— TL_SaveEditor.resetmiiapart has cognitive complexity 604 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_itemsedit.Writessclothesitems (cognitive 594) Tomodachi Life Save Editor/TLSE_itemsedit.vb:524— TLSE_itemsedit.Writessclothesitems has cognitive complexity 594 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Writessclothesitems (cognitive 594) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:10036— TL_SaveEditor.Writessclothesitems has cognitive complexity 594 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_interactions.valu_target1_ValueChanged (cognitive 565) Tomodachi Life Save Editor/TLSE_interactions.vb:9084— TLSE_interactions.valu_target1_ValueChanged has cognitive complexity 565 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.valu_target1_ValueChanged (cognitive 565) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:27489— TL_SaveEditor.valu_target1_ValueChanged has cognitive complexity 565 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miifoods.valu_fav_1_ValueChanged (cognitive 470) Tomodachi Life Save Editor/TLSE_miifoods.vb:6145— TLSE_miifoods.valu_fav_1_ValueChanged has cognitive complexity 470 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TLSE_miifoods.valu_fav_2_ValueChanged, TLSE_miifoods.valu_fav_3_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_fav_2_ValueChanged (cognitive 470) Tomodachi Life Save Editor/TLSE_miifoods.vb:7086— TLSE_miifoods.valu_fav_2_ValueChanged has cognitive complexity 470 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TLSE_miifoods.valu_fav_1_ValueChanged, TLSE_miifoods.valu_fav_3_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_fav_3_ValueChanged (cognitive 470) Tomodachi Life Save Editor/TLSE_miifoods.vb:8027— TLSE_miifoods.valu_fav_3_ValueChanged has cognitive complexity 470 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TLSE_miifoods.valu_fav_1_ValueChanged, TLSE_miifoods.valu_fav_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_allfav_1_ValueChanged (cognitive 468) Tomodachi Life Save Editor/TLSE_miifoods.vb:4271— TLSE_miifoods.valu_allfav_1_ValueChanged has cognitive complexity 468 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_2_ValueChanged, TLSE_miifoods.valu_worst_1_ValueChanged, TLSE_miifoods.valu_worst_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_allfav_2_ValueChanged (cognitive 468) Tomodachi Life Save Editor/TLSE_miifoods.vb:5208— TLSE_miifoods.valu_allfav_2_ValueChanged has cognitive complexity 468 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_1_ValueChanged, TLSE_miifoods.valu_worst_1_ValueChanged, TLSE_miifoods.valu_worst_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_worst_1_ValueChanged (cognitive 468) Tomodachi Life Save Editor/TLSE_miifoods.vb:8968— TLSE_miifoods.valu_worst_1_ValueChanged has cognitive complexity 468 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_1_ValueChanged, TLSE_miifoods.valu_allfav_2_ValueChanged, TLSE_miifoods.valu_worst_2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.valu_worst_2_ValueChanged (cognitive 468) Tomodachi Life Save Editor/TLSE_miifoods.vb:9905— TLSE_miifoods.valu_worst_2_ValueChanged has cognitive complexity 468 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miifoods.valu_allfav_1_ValueChanged, TLSE_miifoods.valu_allfav_2_ValueChanged, TLSE_miifoods.valu_worst_1_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_allfav_1_ValueChanged (cognitive 464) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:40473— TL_SaveEditor.valu_allfav_1_ValueChanged has cognitive complexity 464 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, TL_SaveEditor.valu_fav_2_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_allfav_2_ValueChanged (cognitive 464) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:41407— TL_SaveEditor.valu_allfav_2_ValueChanged has cognitive complexity 464 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, TL_SaveEditor.valu_fav_2_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_fav_1_ValueChanged (cognitive 464) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:42341— TL_SaveEditor.valu_fav_1_ValueChanged has cognitive complexity 464 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_2_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_fav_2_ValueChanged (cognitive 464) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:43275— TL_SaveEditor.valu_fav_2_ValueChanged has cognitive complexity 464 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_fav_3_ValueChanged (cognitive 464) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:44209— TL_SaveEditor.valu_fav_3_ValueChanged has cognitive complexity 464 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_worst_1_ValueChanged (cognitive 464) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:45143— TL_SaveEditor.valu_worst_1_ValueChanged has cognitive complexity 464 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_worst_2_ValueChanged (cognitive 464) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:46077— TL_SaveEditor.valu_worst_2_ValueChanged has cognitive complexity 464 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 6 other methods here (TL_SaveEditor.valu_allfav_1_ValueChanged, TL_SaveEditor.valu_allfav_2_ValueChanged, TL_SaveEditor.valu_fav_1_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 7 times rather than 7 independent problems. Splitting this body alone leaves the other 6 exactly as they are. Where these are variations on one operation, the change that clears all 7 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.readfriendlist (cognitive 407) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:49416— TL_SaveEditor.readfriendlist has cognitive complexity 407 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Resetallrela (cognitive 404) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:6169— TL_SaveEditor.Resetallrela has cognitive complexity 404 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.WritesavedataArc (cognitive 257) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:4160— TL_SaveEditor.WritesavedataArc has cognitive complexity 257 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_travelers_status.Writetravelers (cognitive 251) Tomodachi Life Save Editor/TLSE_travelers_status.vb:3427— TLSE_travelers_status.Writetravelers has cognitive complexity 251 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_interactions.Select_target1_foodUS_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_interactions.vb:10427— TLSE_interactions.Select_target1_foodUS_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_interactions.Select_target1_foodEU_SelectedIndexChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.Select_target1_foodEU_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_interactions.vb:10895— TLSE_interactions.Select_target1_foodEU_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_interactions.Select_target1_foodUS_SelectedIndexChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_1_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:1935— TLSE_miifoods.Select_fav_1_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, TLSE_miifoods.Select_fav_1US_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_2_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:2403— TLSE_miifoods.Select_fav_2_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, TLSE_miifoods.Select_fav_1US_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_3_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:2871— TLSE_miifoods.Select_fav_3_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_1US_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_1US_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:14855— TLSE_miifoods.Select_fav_1US_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_2US_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:15323— TLSE_miifoods.Select_fav_2US_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_fav_3US_SelectedIndexChanged (cognitive 232) Tomodachi Life Save Editor/TLSE_miifoods.vb:15791— TLSE_miifoods.Select_fav_3US_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 5 other methods here (TLSE_miifoods.Select_fav_1_SelectedIndexChanged, TLSE_miifoods.Select_fav_2_SelectedIndexChanged, TLSE_miifoods.Select_fav_3_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 6 times rather than 6 independent problems. Splitting this body alone leaves the other 5 exactly as they are. Where these are variations on one operation, the change that clears all 6 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:28832— TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:29300— TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:30203— TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:30671— TL_SaveEditor.Select_allfav_US2_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_US1_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:31139— TL_SaveEditor.Select_fav_US1_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_US2_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:31607— TL_SaveEditor.Select_fav_US2_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_US3_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:32075— TL_SaveEditor.Select_fav_US3_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_US1_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:32543— TL_SaveEditor.Select_worst_US1_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_US2_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:33011— TL_SaveEditor.Select_worst_US2_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_1_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:37197— TL_SaveEditor.Select_allfav_1_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_allfav_2_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:37665— TL_SaveEditor.Select_allfav_2_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_1_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:38133— TL_SaveEditor.Select_fav_1_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_2_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:38601— TL_SaveEditor.Select_fav_2_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_fav_3_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:39069— TL_SaveEditor.Select_fav_3_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_1_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:39537— TL_SaveEditor.Select_worst_1_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_worst_2_SelectedIndexChanged (cognitive 232) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:40005— TL_SaveEditor.Select_worst_2_SelectedIndexChanged has cognitive complexity 232 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 15 other methods here (TL_SaveEditor.Select_target1_foodUS_SelectedIndexChanged, TL_SaveEditor.Select_target1_foodEU_SelectedIndexChanged, TL_SaveEditor.Select_allfav_US1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 16 times rather than 16 independent problems. Splitting this body alone leaves the other 15 exactly as they are. Where these are variations on one operation, the change that clears all 16 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_1_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:1003— TLSE_miifoods.Select_allfav_1_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, TLSE_miifoods.Select_worst_2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_2_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:1469— TLSE_miifoods.Select_allfav_2_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, TLSE_miifoods.Select_worst_2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_1_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:3339— TLSE_miifoods.Select_worst_1_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_2_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_2_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:3805— TLSE_miifoods.Select_worst_2_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_1US_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:12991— TLSE_miifoods.Select_allfav_1US_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_allfav_2US_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:13457— TLSE_miifoods.Select_allfav_2US_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_1US_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:13923— TLSE_miifoods.Select_worst_1US_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miifoods.Select_worst_2US_SelectedIndexChanged (cognitive 231) Tomodachi Life Save Editor/TLSE_miifoods.vb:14389— TLSE_miifoods.Select_worst_2US_SelectedIndexChanged has cognitive complexity 231 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miifoods.Select_allfav_1_SelectedIndexChanged, TLSE_miifoods.Select_allfav_2_SelectedIndexChanged, TLSE_miifoods.Select_worst_1_SelectedIndexChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_itemsedit.Writesshatsitems (cognitive 213) Tomodachi Life Save Editor/TLSE_itemsedit.vb:2827— TLSE_itemsedit.Writesshatsitems has cognitive complexity 213 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Writesshatsitems (cognitive 213) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:12339— TL_SaveEditor.Writesshatsitems has cognitive complexity 213 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Readmii (cognitive 211) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:48419— TL_SaveEditor.Readmii has cognitive complexity 211 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Patchfriendlist (cognitive 207) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:51702— TL_SaveEditor.Patchfriendlist has cognitive complexity 207 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miiprofile.Savefileregion (cognitive 205) Tomodachi Life Save Editor/TLSE_miiprofile.vb:1674— TLSE_miiprofile.Savefileregion has cognitive complexity 205 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_crcxmodem.readmiidata (cognitive 204) Tomodachi Life Save Editor/TLSE_crcxmodem.vb:163— TLSE_crcxmodem.readmiidata has cognitive complexity 204 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miifoods.Savefileregion (cognitive 204) Tomodachi Life Save Editor/TLSE_miifoods.vb:10909— TLSE_miifoods.Savefileregion has cognitive complexity 204 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miiinventory.Savefileregion (cognitive 204) Tomodachi Life Save Editor/TLSE_miiinventory.vb:3153— TLSE_miiinventory.Savefileregion has cognitive complexity 204 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miistatus.Savefileregion (cognitive 204) Tomodachi Life Save Editor/TLSE_miistatus.vb:1716— TLSE_miistatus.Savefileregion has cognitive complexity 204 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_voicepersonnality.Savefileregion (cognitive 204) Tomodachi Life Save Editor/TLSE_voicepersonnality.vb:1343— TLSE_voicepersonnality.Savefileregion has cognitive complexity 204 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.valu_miiapart_ValueChanged (cognitive 204) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:26604— TL_SaveEditor.valu_miiapart_ValueChanged has cognitive complexity 204 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_manag_travelers.Readmiidata (cognitive 203) Tomodachi Life Save Editor/TLSE_manag_travelers.vb:413— TLSE_manag_travelers.Readmiidata has cognitive complexity 203 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_datamiiexchange.Readislandranking (cognitive 201) Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:982— TLSE_datamiiexchange.Readislandranking has cognitive complexity 201 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_manag_travelers.RestoreTraveler (cognitive 201) Tomodachi Life Save Editor/TLSE_manag_travelers.vb:1042— TLSE_manag_travelers.RestoreTraveler has cognitive complexity 201 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.ReadsavedataArc (cognitive 194) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:3348— TL_SaveEditor.ReadsavedataArc has cognitive complexity 194 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Danger_interaction_Click (cognitive 192) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:29768— TL_SaveEditor.Danger_interaction_Click has cognitive complexity 192 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_Jrelationships.valu_friend_rela_1_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48916— TLSE_Jrelationships.valu_friend_rela_1_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, TLSE_Jrelationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_2_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49208— TLSE_Jrelationships.valu_friend_rela_2_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, TLSE_Jrelationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_3_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49500— TLSE_Jrelationships.valu_friend_rela_3_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_4_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:49792— TLSE_Jrelationships.valu_friend_rela_4_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_5_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50084— TLSE_Jrelationships.valu_friend_rela_5_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_6_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50376— TLSE_Jrelationships.valu_friend_rela_6_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_7_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50668— TLSE_Jrelationships.valu_friend_rela_7_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_8_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:50960— TLSE_Jrelationships.valu_friend_rela_8_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_9_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51252— TLSE_Jrelationships.valu_friend_rela_9_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_10_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51544— TLSE_Jrelationships.valu_friend_rela_10_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_11_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:51836— TLSE_Jrelationships.valu_friend_rela_11_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_12_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52128— TLSE_Jrelationships.valu_friend_rela_12_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_13_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52420— TLSE_Jrelationships.valu_friend_rela_13_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_14_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:52712— TLSE_Jrelationships.valu_friend_rela_14_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_15_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53004— TLSE_Jrelationships.valu_friend_rela_15_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_16_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53296— TLSE_Jrelationships.valu_friend_rela_16_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_17_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53588— TLSE_Jrelationships.valu_friend_rela_17_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_18_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:53880— TLSE_Jrelationships.valu_friend_rela_18_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_19_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54172— TLSE_Jrelationships.valu_friend_rela_19_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_20_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54464— TLSE_Jrelationships.valu_friend_rela_20_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_21_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:54756— TLSE_Jrelationships.valu_friend_rela_21_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_22_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55048— TLSE_Jrelationships.valu_friend_rela_22_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_23_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55340— TLSE_Jrelationships.valu_friend_rela_23_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_24_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55632— TLSE_Jrelationships.valu_friend_rela_24_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_25_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:55924— TLSE_Jrelationships.valu_friend_rela_25_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_26_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:56216— TLSE_Jrelationships.valu_friend_rela_26_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_27_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:56508— TLSE_Jrelationships.valu_friend_rela_27_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_28_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:56800— TLSE_Jrelationships.valu_friend_rela_28_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_29_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57092— TLSE_Jrelationships.valu_friend_rela_29_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_30_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57384— TLSE_Jrelationships.valu_friend_rela_30_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_31_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57676— TLSE_Jrelationships.valu_friend_rela_31_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_32_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:57968— TLSE_Jrelationships.valu_friend_rela_32_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_33_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:58260— TLSE_Jrelationships.valu_friend_rela_33_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_34_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:58552— TLSE_Jrelationships.valu_friend_rela_34_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_35_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:58844— TLSE_Jrelationships.valu_friend_rela_35_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_36_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:59136— TLSE_Jrelationships.valu_friend_rela_36_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_37_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:59428— TLSE_Jrelationships.valu_friend_rela_37_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_38_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:59720— TLSE_Jrelationships.valu_friend_rela_38_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_39_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60012— TLSE_Jrelationships.valu_friend_rela_39_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_40_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60304— TLSE_Jrelationships.valu_friend_rela_40_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_41_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60596— TLSE_Jrelationships.valu_friend_rela_41_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_42_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:60888— TLSE_Jrelationships.valu_friend_rela_42_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_43_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:61180— TLSE_Jrelationships.valu_friend_rela_43_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_44_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:61472— TLSE_Jrelationships.valu_friend_rela_44_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_45_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:61764— TLSE_Jrelationships.valu_friend_rela_45_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_46_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62056— TLSE_Jrelationships.valu_friend_rela_46_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_47_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62348— TLSE_Jrelationships.valu_friend_rela_47_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_48_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62640— TLSE_Jrelationships.valu_friend_rela_48_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_49_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:62932— TLSE_Jrelationships.valu_friend_rela_49_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_50_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:63224— TLSE_Jrelationships.valu_friend_rela_50_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_51_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:63516— TLSE_Jrelationships.valu_friend_rela_51_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_52_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:63808— TLSE_Jrelationships.valu_friend_rela_52_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_53_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64100— TLSE_Jrelationships.valu_friend_rela_53_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_54_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64392— TLSE_Jrelationships.valu_friend_rela_54_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_55_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64684— TLSE_Jrelationships.valu_friend_rela_55_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_56_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:64976— TLSE_Jrelationships.valu_friend_rela_56_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_57_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:65268— TLSE_Jrelationships.valu_friend_rela_57_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_58_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:65560— TLSE_Jrelationships.valu_friend_rela_58_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_59_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:65852— TLSE_Jrelationships.valu_friend_rela_59_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_60_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:66144— TLSE_Jrelationships.valu_friend_rela_60_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_61_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:66436— TLSE_Jrelationships.valu_friend_rela_61_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_62_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:66728— TLSE_Jrelationships.valu_friend_rela_62_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_63_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67020— TLSE_Jrelationships.valu_friend_rela_63_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_64_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67312— TLSE_Jrelationships.valu_friend_rela_64_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_65_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67604— TLSE_Jrelationships.valu_friend_rela_65_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_66_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:67896— TLSE_Jrelationships.valu_friend_rela_66_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_67_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:68188— TLSE_Jrelationships.valu_friend_rela_67_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_68_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:68480— TLSE_Jrelationships.valu_friend_rela_68_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_69_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:68772— TLSE_Jrelationships.valu_friend_rela_69_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_70_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69064— TLSE_Jrelationships.valu_friend_rela_70_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_71_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69356— TLSE_Jrelationships.valu_friend_rela_71_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_72_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69648— TLSE_Jrelationships.valu_friend_rela_72_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_73_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:69940— TLSE_Jrelationships.valu_friend_rela_73_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_74_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:70232— TLSE_Jrelationships.valu_friend_rela_74_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_75_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:70524— TLSE_Jrelationships.valu_friend_rela_75_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_76_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:70816— TLSE_Jrelationships.valu_friend_rela_76_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_77_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71108— TLSE_Jrelationships.valu_friend_rela_77_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_78_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71400— TLSE_Jrelationships.valu_friend_rela_78_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_79_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71692— TLSE_Jrelationships.valu_friend_rela_79_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_80_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:71984— TLSE_Jrelationships.valu_friend_rela_80_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_81_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:72276— TLSE_Jrelationships.valu_friend_rela_81_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_82_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:72568— TLSE_Jrelationships.valu_friend_rela_82_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_83_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:72860— TLSE_Jrelationships.valu_friend_rela_83_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_84_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:73152— TLSE_Jrelationships.valu_friend_rela_84_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_85_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:73444— TLSE_Jrelationships.valu_friend_rela_85_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_86_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:73736— TLSE_Jrelationships.valu_friend_rela_86_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_87_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74028— TLSE_Jrelationships.valu_friend_rela_87_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_88_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74320— TLSE_Jrelationships.valu_friend_rela_88_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_89_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74612— TLSE_Jrelationships.valu_friend_rela_89_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_90_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:74904— TLSE_Jrelationships.valu_friend_rela_90_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_91_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:75196— TLSE_Jrelationships.valu_friend_rela_91_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_92_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:75488— TLSE_Jrelationships.valu_friend_rela_92_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_93_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:75780— TLSE_Jrelationships.valu_friend_rela_93_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_94_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76072— TLSE_Jrelationships.valu_friend_rela_94_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_95_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76364— TLSE_Jrelationships.valu_friend_rela_95_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_96_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76656— TLSE_Jrelationships.valu_friend_rela_96_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_97_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:76948— TLSE_Jrelationships.valu_friend_rela_97_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_98_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:77240— TLSE_Jrelationships.valu_friend_rela_98_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_99_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:77532— TLSE_Jrelationships.valu_friend_rela_99_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_friend_rela_100_ValueChanged (cognitive 183) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:77824— TLSE_Jrelationships.valu_friend_rela_100_ValueChanged has cognitive complexity 183 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_friend_rela_1_ValueChanged, TLSE_Jrelationships.valu_friend_rela_2_ValueChanged, TLSE_Jrelationships.valu_friend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluJP (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:113848— TL_SaveEditor.NamerelavaluJP has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, TL_SaveEditor.NamerelavaluJP4, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluJP2 (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:114226— TL_SaveEditor.NamerelavaluJP2 has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP3, TL_SaveEditor.NamerelavaluJP4, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluJP3 (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:114604— TL_SaveEditor.NamerelavaluJP3 has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP4, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluJP4 (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:114982— TL_SaveEditor.NamerelavaluJP4 has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:115360— TL_SaveEditor.NamerelavaluKR has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR2 (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:115738— TL_SaveEditor.NamerelavaluKR2 has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR3 (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:116116— TL_SaveEditor.NamerelavaluKR3 has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.NamerelavaluKR4 (cognitive 175) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:116494— TL_SaveEditor.NamerelavaluKR4 has cognitive complexity 175 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.NamerelavaluJP, TL_SaveEditor.NamerelavaluJP2, TL_SaveEditor.NamerelavaluJP3, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.InteractionlistEUR (cognitive 146) Tomodachi Life Save Editor/TLSE_interactions.vb:4977— TLSE_interactions.InteractionlistEUR has cognitive complexity 146 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_interactions.Select_interaction_SelectedIndexChanged (cognitive 145) Tomodachi Life Save Editor/TLSE_interactions.vb:6153— TLSE_interactions.Select_interaction_SelectedIndexChanged has cognitive complexity 145 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Select_interaction_SelectedIndexChanged (cognitive 145) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:25547— TL_SaveEditor.Select_interaction_SelectedIndexChanged has cognitive complexity 145 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged, TL_SaveEditor.InteractionlistEUR, TL_SaveEditor.InteractionlistUSA) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged (cognitive 145) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:25841— TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged has cognitive complexity 145 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_SelectedIndexChanged, TL_SaveEditor.InteractionlistEUR, TL_SaveEditor.InteractionlistUSA) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.InteractionlistEUR (cognitive 145) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:119925— TL_SaveEditor.InteractionlistEUR has cognitive complexity 145 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_SelectedIndexChanged, TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged, TL_SaveEditor.InteractionlistUSA) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.InteractionlistUSA (cognitive 145) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:121219— TL_SaveEditor.InteractionlistUSA has cognitive complexity 145 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_interaction_SelectedIndexChanged, TL_SaveEditor.Select_interaction_USA_SelectedIndexChanged, TL_SaveEditor.InteractionlistEUR) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_creaislandranking.Select_spesymb_islandname_SelectedIndexChanged (cognitive 114) Tomodachi Life Save Editor/TLSE_creaislandranking.vb:151— TLSE_creaislandranking.Select_spesymb_islandname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_islandinfo.Select_spesymb_islandname_SelectedIndexChanged (cognitive 114) Tomodachi Life Save Editor/TLSE_islandinfo.vb:175— TLSE_islandinfo.Select_spesymb_islandname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged (cognitive 114) Tomodachi Life Save Editor/TLSE_miiprofile.vb:165— TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged (cognitive 114) Tomodachi Life Save Editor/TLSE_miiprofile.vb:443— TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged (cognitive 114) Tomodachi Life Save Editor/TLSE_miiprofile.vb:721— TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged (cognitive 114) Tomodachi Life Save Editor/TLSE_miiprofile.vb:992— TLSE_miiprofile.Select_spesymb_creator_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_miiprofile.Select_spesymb_firstname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_lastname_SelectedIndexChanged, TLSE_miiprofile.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged (cognitive 114) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:1820— TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged (cognitive 114) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:14122— TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged (cognitive 114) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:14400— TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged (cognitive 114) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:14678— TL_SaveEditor.Select_spesymb_nickname_SelectedIndexChanged has cognitive complexity 114 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Select_spesymb_islandname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_firstname_SelectedIndexChanged, TL_SaveEditor.Select_spesymb_lastname_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23169— TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23400— TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23631— TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:23862— TLSE_Jrelationships.valu_selfriend_rela_4_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_5_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24093— TLSE_Jrelationships.valu_selfriend_rela_5_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_6_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24324— TLSE_Jrelationships.valu_selfriend_rela_6_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_7_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24555— TLSE_Jrelationships.valu_selfriend_rela_7_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_8_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:24786— TLSE_Jrelationships.valu_selfriend_rela_8_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_9_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25017— TLSE_Jrelationships.valu_selfriend_rela_9_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_10_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25248— TLSE_Jrelationships.valu_selfriend_rela_10_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_11_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25479— TLSE_Jrelationships.valu_selfriend_rela_11_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_12_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25711— TLSE_Jrelationships.valu_selfriend_rela_12_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_13_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:25942— TLSE_Jrelationships.valu_selfriend_rela_13_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_14_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26173— TLSE_Jrelationships.valu_selfriend_rela_14_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_15_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26404— TLSE_Jrelationships.valu_selfriend_rela_15_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_16_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26635— TLSE_Jrelationships.valu_selfriend_rela_16_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_17_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:26866— TLSE_Jrelationships.valu_selfriend_rela_17_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_18_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27097— TLSE_Jrelationships.valu_selfriend_rela_18_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_19_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27328— TLSE_Jrelationships.valu_selfriend_rela_19_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_20_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27559— TLSE_Jrelationships.valu_selfriend_rela_20_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_21_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:27790— TLSE_Jrelationships.valu_selfriend_rela_21_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_22_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28021— TLSE_Jrelationships.valu_selfriend_rela_22_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_23_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28252— TLSE_Jrelationships.valu_selfriend_rela_23_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_24_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28483— TLSE_Jrelationships.valu_selfriend_rela_24_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_25_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28714— TLSE_Jrelationships.valu_selfriend_rela_25_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_26_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:28945— TLSE_Jrelationships.valu_selfriend_rela_26_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_27_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29176— TLSE_Jrelationships.valu_selfriend_rela_27_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_28_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29407— TLSE_Jrelationships.valu_selfriend_rela_28_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_29_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29638— TLSE_Jrelationships.valu_selfriend_rela_29_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_30_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:29869— TLSE_Jrelationships.valu_selfriend_rela_30_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_31_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30100— TLSE_Jrelationships.valu_selfriend_rela_31_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_32_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30331— TLSE_Jrelationships.valu_selfriend_rela_32_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_33_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30562— TLSE_Jrelationships.valu_selfriend_rela_33_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_34_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:30793— TLSE_Jrelationships.valu_selfriend_rela_34_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_35_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31024— TLSE_Jrelationships.valu_selfriend_rela_35_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_36_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31255— TLSE_Jrelationships.valu_selfriend_rela_36_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_37_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31486— TLSE_Jrelationships.valu_selfriend_rela_37_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_38_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31717— TLSE_Jrelationships.valu_selfriend_rela_38_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_39_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:31948— TLSE_Jrelationships.valu_selfriend_rela_39_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_40_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32179— TLSE_Jrelationships.valu_selfriend_rela_40_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_41_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32410— TLSE_Jrelationships.valu_selfriend_rela_41_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_42_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32641— TLSE_Jrelationships.valu_selfriend_rela_42_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_43_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:32872— TLSE_Jrelationships.valu_selfriend_rela_43_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_44_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33103— TLSE_Jrelationships.valu_selfriend_rela_44_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_45_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33334— TLSE_Jrelationships.valu_selfriend_rela_45_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_46_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33565— TLSE_Jrelationships.valu_selfriend_rela_46_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_47_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:33796— TLSE_Jrelationships.valu_selfriend_rela_47_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_48_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34027— TLSE_Jrelationships.valu_selfriend_rela_48_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_49_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34258— TLSE_Jrelationships.valu_selfriend_rela_49_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_50_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34489— TLSE_Jrelationships.valu_selfriend_rela_50_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_51_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34720— TLSE_Jrelationships.valu_selfriend_rela_51_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_52_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:34951— TLSE_Jrelationships.valu_selfriend_rela_52_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_53_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35182— TLSE_Jrelationships.valu_selfriend_rela_53_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_54_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35413— TLSE_Jrelationships.valu_selfriend_rela_54_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_55_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35644— TLSE_Jrelationships.valu_selfriend_rela_55_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_56_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:35875— TLSE_Jrelationships.valu_selfriend_rela_56_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_57_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36106— TLSE_Jrelationships.valu_selfriend_rela_57_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_58_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36337— TLSE_Jrelationships.valu_selfriend_rela_58_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_59_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36568— TLSE_Jrelationships.valu_selfriend_rela_59_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_60_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:36799— TLSE_Jrelationships.valu_selfriend_rela_60_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_61_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37030— TLSE_Jrelationships.valu_selfriend_rela_61_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_62_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37261— TLSE_Jrelationships.valu_selfriend_rela_62_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_63_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37492— TLSE_Jrelationships.valu_selfriend_rela_63_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_64_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37723— TLSE_Jrelationships.valu_selfriend_rela_64_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_65_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:37954— TLSE_Jrelationships.valu_selfriend_rela_65_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_66_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38185— TLSE_Jrelationships.valu_selfriend_rela_66_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_67_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38416— TLSE_Jrelationships.valu_selfriend_rela_67_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_68_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38647— TLSE_Jrelationships.valu_selfriend_rela_68_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_69_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:38878— TLSE_Jrelationships.valu_selfriend_rela_69_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_70_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39109— TLSE_Jrelationships.valu_selfriend_rela_70_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_71_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39340— TLSE_Jrelationships.valu_selfriend_rela_71_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_72_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39571— TLSE_Jrelationships.valu_selfriend_rela_72_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_73_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:39802— TLSE_Jrelationships.valu_selfriend_rela_73_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_74_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40033— TLSE_Jrelationships.valu_selfriend_rela_74_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_75_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40264— TLSE_Jrelationships.valu_selfriend_rela_75_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_76_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40495— TLSE_Jrelationships.valu_selfriend_rela_76_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_77_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40726— TLSE_Jrelationships.valu_selfriend_rela_77_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_78_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:40957— TLSE_Jrelationships.valu_selfriend_rela_78_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_79_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41188— TLSE_Jrelationships.valu_selfriend_rela_79_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_80_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41419— TLSE_Jrelationships.valu_selfriend_rela_80_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_81_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41650— TLSE_Jrelationships.valu_selfriend_rela_81_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_82_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:41881— TLSE_Jrelationships.valu_selfriend_rela_82_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_83_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42112— TLSE_Jrelationships.valu_selfriend_rela_83_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_84_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42343— TLSE_Jrelationships.valu_selfriend_rela_84_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_85_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42574— TLSE_Jrelationships.valu_selfriend_rela_85_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_86_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:42805— TLSE_Jrelationships.valu_selfriend_rela_86_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_87_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43036— TLSE_Jrelationships.valu_selfriend_rela_87_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_88_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43267— TLSE_Jrelationships.valu_selfriend_rela_88_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_89_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43498— TLSE_Jrelationships.valu_selfriend_rela_89_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_90_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43729— TLSE_Jrelationships.valu_selfriend_rela_90_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_91_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:43960— TLSE_Jrelationships.valu_selfriend_rela_91_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_92_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44191— TLSE_Jrelationships.valu_selfriend_rela_92_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_93_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44422— TLSE_Jrelationships.valu_selfriend_rela_93_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_94_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44653— TLSE_Jrelationships.valu_selfriend_rela_94_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_95_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:44884— TLSE_Jrelationships.valu_selfriend_rela_95_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_96_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45115— TLSE_Jrelationships.valu_selfriend_rela_96_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_97_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45346— TLSE_Jrelationships.valu_selfriend_rela_97_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_98_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45577— TLSE_Jrelationships.valu_selfriend_rela_98_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_99_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:45808— TLSE_Jrelationships.valu_selfriend_rela_99_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.valu_selfriend_rela_100_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46039— TLSE_Jrelationships.valu_selfriend_rela_100_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_Jrelationships.valu_selfriend_rela_1_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_2_ValueChanged, TLSE_Jrelationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_1_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23171— TLSE_relationships.valu_selfriend_rela_1_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, TLSE_relationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_2_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23402— TLSE_relationships.valu_selfriend_rela_2_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, TLSE_relationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_3_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23633— TLSE_relationships.valu_selfriend_rela_3_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_4_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:23864— TLSE_relationships.valu_selfriend_rela_4_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_5_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24095— TLSE_relationships.valu_selfriend_rela_5_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_6_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24326— TLSE_relationships.valu_selfriend_rela_6_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_7_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24557— TLSE_relationships.valu_selfriend_rela_7_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_8_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:24788— TLSE_relationships.valu_selfriend_rela_8_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_9_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25019— TLSE_relationships.valu_selfriend_rela_9_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_10_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25250— TLSE_relationships.valu_selfriend_rela_10_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_11_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25481— TLSE_relationships.valu_selfriend_rela_11_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_12_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25713— TLSE_relationships.valu_selfriend_rela_12_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_13_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:25944— TLSE_relationships.valu_selfriend_rela_13_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_14_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26175— TLSE_relationships.valu_selfriend_rela_14_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_15_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26406— TLSE_relationships.valu_selfriend_rela_15_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_16_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26637— TLSE_relationships.valu_selfriend_rela_16_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_17_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:26868— TLSE_relationships.valu_selfriend_rela_17_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_18_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27099— TLSE_relationships.valu_selfriend_rela_18_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_19_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27330— TLSE_relationships.valu_selfriend_rela_19_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_20_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27561— TLSE_relationships.valu_selfriend_rela_20_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_21_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:27792— TLSE_relationships.valu_selfriend_rela_21_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_22_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28023— TLSE_relationships.valu_selfriend_rela_22_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_23_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28254— TLSE_relationships.valu_selfriend_rela_23_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_24_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28485— TLSE_relationships.valu_selfriend_rela_24_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_25_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28716— TLSE_relationships.valu_selfriend_rela_25_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_26_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:28947— TLSE_relationships.valu_selfriend_rela_26_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_27_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29178— TLSE_relationships.valu_selfriend_rela_27_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_28_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29409— TLSE_relationships.valu_selfriend_rela_28_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_29_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29640— TLSE_relationships.valu_selfriend_rela_29_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_30_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:29871— TLSE_relationships.valu_selfriend_rela_30_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_31_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30102— TLSE_relationships.valu_selfriend_rela_31_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_32_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30333— TLSE_relationships.valu_selfriend_rela_32_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_33_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30564— TLSE_relationships.valu_selfriend_rela_33_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_34_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:30795— TLSE_relationships.valu_selfriend_rela_34_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_35_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31026— TLSE_relationships.valu_selfriend_rela_35_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_36_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31257— TLSE_relationships.valu_selfriend_rela_36_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_37_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31488— TLSE_relationships.valu_selfriend_rela_37_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_38_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31719— TLSE_relationships.valu_selfriend_rela_38_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_39_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:31950— TLSE_relationships.valu_selfriend_rela_39_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_40_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32181— TLSE_relationships.valu_selfriend_rela_40_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_41_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32412— TLSE_relationships.valu_selfriend_rela_41_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_42_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32643— TLSE_relationships.valu_selfriend_rela_42_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_43_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:32874— TLSE_relationships.valu_selfriend_rela_43_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_44_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33105— TLSE_relationships.valu_selfriend_rela_44_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_45_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33336— TLSE_relationships.valu_selfriend_rela_45_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_46_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33567— TLSE_relationships.valu_selfriend_rela_46_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_47_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:33798— TLSE_relationships.valu_selfriend_rela_47_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_48_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34029— TLSE_relationships.valu_selfriend_rela_48_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_49_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34260— TLSE_relationships.valu_selfriend_rela_49_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_50_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34491— TLSE_relationships.valu_selfriend_rela_50_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_51_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34722— TLSE_relationships.valu_selfriend_rela_51_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_52_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:34953— TLSE_relationships.valu_selfriend_rela_52_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_53_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35184— TLSE_relationships.valu_selfriend_rela_53_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_54_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35415— TLSE_relationships.valu_selfriend_rela_54_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_55_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35646— TLSE_relationships.valu_selfriend_rela_55_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_56_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:35877— TLSE_relationships.valu_selfriend_rela_56_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_57_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36108— TLSE_relationships.valu_selfriend_rela_57_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_58_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36339— TLSE_relationships.valu_selfriend_rela_58_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_59_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36570— TLSE_relationships.valu_selfriend_rela_59_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_60_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:36801— TLSE_relationships.valu_selfriend_rela_60_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_61_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37032— TLSE_relationships.valu_selfriend_rela_61_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_62_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37263— TLSE_relationships.valu_selfriend_rela_62_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_63_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37494— TLSE_relationships.valu_selfriend_rela_63_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_64_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37725— TLSE_relationships.valu_selfriend_rela_64_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_65_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:37956— TLSE_relationships.valu_selfriend_rela_65_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_66_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38187— TLSE_relationships.valu_selfriend_rela_66_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_67_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38418— TLSE_relationships.valu_selfriend_rela_67_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_68_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38649— TLSE_relationships.valu_selfriend_rela_68_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_69_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:38880— TLSE_relationships.valu_selfriend_rela_69_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_70_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39111— TLSE_relationships.valu_selfriend_rela_70_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_71_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39342— TLSE_relationships.valu_selfriend_rela_71_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_72_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39573— TLSE_relationships.valu_selfriend_rela_72_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_73_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:39804— TLSE_relationships.valu_selfriend_rela_73_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_74_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40035— TLSE_relationships.valu_selfriend_rela_74_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_75_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40266— TLSE_relationships.valu_selfriend_rela_75_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_76_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40497— TLSE_relationships.valu_selfriend_rela_76_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_77_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40728— TLSE_relationships.valu_selfriend_rela_77_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_78_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:40959— TLSE_relationships.valu_selfriend_rela_78_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_79_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41190— TLSE_relationships.valu_selfriend_rela_79_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_80_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41421— TLSE_relationships.valu_selfriend_rela_80_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_81_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41652— TLSE_relationships.valu_selfriend_rela_81_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_82_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:41883— TLSE_relationships.valu_selfriend_rela_82_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_83_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42114— TLSE_relationships.valu_selfriend_rela_83_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_84_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42345— TLSE_relationships.valu_selfriend_rela_84_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_85_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42576— TLSE_relationships.valu_selfriend_rela_85_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_86_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:42807— TLSE_relationships.valu_selfriend_rela_86_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_87_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43038— TLSE_relationships.valu_selfriend_rela_87_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_88_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43269— TLSE_relationships.valu_selfriend_rela_88_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_89_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43500— TLSE_relationships.valu_selfriend_rela_89_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_90_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43731— TLSE_relationships.valu_selfriend_rela_90_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_91_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:43962— TLSE_relationships.valu_selfriend_rela_91_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_92_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44193— TLSE_relationships.valu_selfriend_rela_92_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_93_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44424— TLSE_relationships.valu_selfriend_rela_93_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_94_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44655— TLSE_relationships.valu_selfriend_rela_94_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_95_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:44886— TLSE_relationships.valu_selfriend_rela_95_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_96_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45117— TLSE_relationships.valu_selfriend_rela_96_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_97_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45348— TLSE_relationships.valu_selfriend_rela_97_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_98_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45579— TLSE_relationships.valu_selfriend_rela_98_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_99_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:45810— TLSE_relationships.valu_selfriend_rela_99_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.valu_selfriend_rela_100_ValueChanged (cognitive 113) Tomodachi Life Save Editor/TLSE_relationships.vb:46041— TLSE_relationships.valu_selfriend_rela_100_ValueChanged has cognitive complexity 113 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 99 other methods here (TLSE_relationships.valu_selfriend_rela_1_ValueChanged, TLSE_relationships.valu_selfriend_rela_2_ValueChanged, TLSE_relationships.valu_selfriend_rela_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 100 times rather than 100 independent problems. Splitting this body alone leaves the other 99 exactly as they are. Where these are variations on one operation, the change that clears all 100 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Readfriendlist (cognitive 105) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80579— TLSE_Jrelationships.Readfriendlist has cognitive complexity 105 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_relationships.Readfriendlist (cognitive 105) Tomodachi Life Save Editor/TLSE_relationships.vb:192202— TLSE_relationships.Readfriendlist has cognitive complexity 105 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Miimusic_edit.Miimusic_edit_Load (cognitive 104) Version 4.0.0/Tomodachi-Life-Save-Editor/Miimusic_edit.vb:210— Miimusic_edit.Miimusic_edit_Load has cognitive complexity 104 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_dataislandranking.Readislandranking (cognitive 101) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1782— TLSE_dataislandranking.Readislandranking has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_dataislandranking.RestoreIslandranking) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_dataislandranking.RestoreIslandranking (cognitive 101) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:2245— TLSE_dataislandranking.RestoreIslandranking has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_dataislandranking.Readislandranking) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.Readinteraction (cognitive 101) Tomodachi Life Save Editor/TLSE_interactions.vb:7453— TLSE_interactions.Readinteraction has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_interactions.Select_target1_SelectedIndexChanged (cognitive 101) Tomodachi Life Save Editor/TLSE_interactions.vb:8672— TLSE_interactions.Select_target1_SelectedIndexChanged has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TLSE_interactions.Select_target2_SelectedIndexChanged, TLSE_interactions.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.Select_target2_SelectedIndexChanged (cognitive 101) Tomodachi Life Save Editor/TLSE_interactions.vb:8878— TLSE_interactions.Select_target2_SelectedIndexChanged has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TLSE_interactions.Select_target1_SelectedIndexChanged, TLSE_interactions.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.valu_target2_ValueChanged (cognitive 101) Tomodachi Life Save Editor/TLSE_interactions.vb:10221— TLSE_interactions.valu_target2_ValueChanged has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TLSE_interactions.Select_target1_SelectedIndexChanged, TLSE_interactions.Select_target2_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_interactions.Writeinteraction (cognitive 101) Tomodachi Life Save Editor/TLSE_interactions.vb:11380— TLSE_interactions.Writeinteraction has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_manag_mii.Readmiidata (cognitive 101) Tomodachi Life Save Editor/TLSE_manag_mii.vb:670— TLSE_manag_mii.Readmiidata has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_manag_mii.RestoreMii) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_manag_mii.RestoreMii (cognitive 101) Tomodachi Life Save Editor/TLSE_manag_mii.vb:1751— TLSE_manag_mii.RestoreMii has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_manag_mii.Readmiidata) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_target1_SelectedIndexChanged (cognitive 101) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:27077— TL_SaveEditor.Select_target1_SelectedIndexChanged has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_target2_SelectedIndexChanged, TL_SaveEditor.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_target2_SelectedIndexChanged (cognitive 101) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:27283— TL_SaveEditor.Select_target2_SelectedIndexChanged has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_target1_SelectedIndexChanged, TL_SaveEditor.valu_target2_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_target2_ValueChanged (cognitive 101) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:28626— TL_SaveEditor.valu_target2_ValueChanged has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_target1_SelectedIndexChanged, TL_SaveEditor.Select_target2_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Button_setallfriends_Click (cognitive 100) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46282— TLSE_Jrelationships.Button_setallfriends_Click has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miistatus.valu_experience_ValueChanged (cognitive 100) Tomodachi Life Save Editor/TLSE_miistatus.vb:1339— TLSE_miistatus.valu_experience_ValueChanged has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_relationships.Button_setallfriends_Click (cognitive 100) Tomodachi Life Save Editor/TLSE_relationships.vb:46285— TLSE_relationships.Button_setallfriends_Click has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_travelers_status.valu_happiness_ValueChanged (cognitive 100) Tomodachi Life Save Editor/TLSE_travelers_status.vb:1231— TLSE_travelers_status.valu_happiness_ValueChanged has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.valu_experience_ValueChanged (cognitive 100) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:13803— TL_SaveEditor.valu_experience_ValueChanged has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TL_SaveEditor.Button_setallfriends_Click) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Button_setallfriends_Click (cognitive 100) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17433— TL_SaveEditor.Button_setallfriends_Click has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TL_SaveEditor.valu_experience_ValueChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Text_save_editsongs_Click (cognitive 58) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:9106— TL_SaveEditor.Text_save_editsongs_Click has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Advanceitemsedit.Checkitems (cognitive 54) Version 4.0.0/Tomodachi-Life-Save-Editor/Advanceitemsedit.vb:508— Advanceitemsedit.Checkitems has cognitive complexity 54 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_manag_travelers.RestoreMii (cognitive 51) Tomodachi Life Save Editor/TLSE_manag_travelers.vb:1603— TLSE_manag_travelers.RestoreMii has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_travelers_status.Readtravelers (cognitive 51) Tomodachi Life Save Editor/TLSE_travelers_status.vb:1718— TLSE_travelers_status.Readtravelers has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_concertedit.Select_songs_SelectedIndexChanged (cognitive 50) Tomodachi Life Save Editor/TLSE_concertedit.vb:131— TLSE_concertedit.Select_songs_SelectedIndexChanged has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_extras.Check_timetravel_CheckedChanged (cognitive 50) Tomodachi Life Save Editor/TLSE_extras.vb:123— TLSE_extras.Check_timetravel_CheckedChanged has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Select_songs_SelectedIndexChanged (cognitive 50) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:8786— TL_SaveEditor.Select_songs_SelectedIndexChanged has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_miihouse_SelectedIndexChanged, TL_SaveEditor.valu_miihouse_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Select_miihouse_SelectedIndexChanged (cognitive 50) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:47257— TL_SaveEditor.Select_miihouse_SelectedIndexChanged has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_songs_SelectedIndexChanged, TL_SaveEditor.valu_miihouse_ValueChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_miihouse_ValueChanged (cognitive 50) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:47361— TL_SaveEditor.valu_miihouse_ValueChanged has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 2 other methods here (TL_SaveEditor.Select_songs_SelectedIndexChanged, TL_SaveEditor.Select_miihouse_SelectedIndexChanged) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_concertedit.Text_save_editsongs_Click (cognitive 47) Tomodachi Life Save Editor/TLSE_concertedit.vb:439— TLSE_concertedit.Text_save_editsongs_Click has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Miimusic_edit.Text_save_Click (cognitive 47) Version 4.0.0/Tomodachi-Life-Save-Editor/Miimusic_edit.vb:469— Miimusic_edit.Text_save_Click has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Writemii (cognitive 40) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:51383— TL_SaveEditor.Writemii has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_itemsedit.Text_menu_save_Click (cognitive 39) Tomodachi Life Save Editor/TLSE_itemsedit.vb:3504— TLSE_itemsedit.Text_menu_save_Click has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_extras.Check_resetnewsflash_CheckedChanged (cognitive 35) Tomodachi Life Save Editor/TLSE_extras.vb:1481— TLSE_extras.Check_resetnewsflash_CheckedChanged has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_Jrelationships.Writefriendlist4 (cognitive 33) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:165387— TLSE_Jrelationships.Writefriendlist4 has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_relationships.Writefriendlist4 (cognitive 33) Tomodachi Life Save Editor/TLSE_relationships.vb:277010— TLSE_relationships.Writefriendlist4 has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_Jrelationships.Writefriendlist2 (cognitive 30) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:135257— TLSE_Jrelationships.Writefriendlist2 has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_Jrelationships.Writefriendlist3) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Writefriendlist3 (cognitive 30) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:150322— TLSE_Jrelationships.Writefriendlist3 has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_Jrelationships.Writefriendlist2) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miistatus.Writemiistatus (cognitive 30) Tomodachi Life Save Editor/TLSE_miistatus.vb:4585— TLSE_miistatus.Writemiistatus has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_relationships.Writefriendlist2 (cognitive 30) Tomodachi Life Save Editor/TLSE_relationships.vb:246880— TLSE_relationships.Writefriendlist2 has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_relationships.Writefriendlist3) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.Writefriendlist3 (cognitive 30) Tomodachi Life Save Editor/TLSE_relationships.vb:261945— TLSE_relationships.Writefriendlist3 has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_relationships.Writefriendlist2) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_Jrelationships.Writefriendlist (cognitive 29) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:120794— TLSE_Jrelationships.Writefriendlist has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_miiinventory.valu_itemmii_1_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2657— TLSE_miiinventory.valu_itemmii_1_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, TLSE_miiinventory.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_2_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2719— TLSE_miiinventory.valu_itemmii_2_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, TLSE_miiinventory.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_3_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2781— TLSE_miiinventory.valu_itemmii_3_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_4_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2843— TLSE_miiinventory.valu_itemmii_4_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_5_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2905— TLSE_miiinventory.valu_itemmii_5_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_6_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:2967— TLSE_miiinventory.valu_itemmii_6_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_7_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:3029— TLSE_miiinventory.valu_itemmii_7_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_miiinventory.valu_itemmii_8_ValueChanged (cognitive 29) Tomodachi Life Save Editor/TLSE_miiinventory.vb:3091— TLSE_miiinventory.valu_itemmii_8_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TLSE_miiinventory.valu_itemmii_1_ValueChanged, TLSE_miiinventory.valu_itemmii_2_ValueChanged, TLSE_miiinventory.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_relationships.Writefriendlist (cognitive 29) Tomodachi Life Save Editor/TLSE_relationships.vb:232417— TLSE_relationships.Writefriendlist has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.valu_itemmii_1_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:16844— TL_SaveEditor.valu_itemmii_1_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, TL_SaveEditor.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_2_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:16906— TL_SaveEditor.valu_itemmii_2_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, TL_SaveEditor.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_3_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:16968— TL_SaveEditor.valu_itemmii_3_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_4_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_4_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17030— TL_SaveEditor.valu_itemmii_4_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_5_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17092— TL_SaveEditor.valu_itemmii_5_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_6_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17154— TL_SaveEditor.valu_itemmii_6_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_7_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17216— TL_SaveEditor.valu_itemmii_7_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.valu_itemmii_8_ValueChanged (cognitive 29) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:17278— TL_SaveEditor.valu_itemmii_8_ValueChanged has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 7 other methods here (TL_SaveEditor.valu_itemmii_1_ValueChanged, TL_SaveEditor.valu_itemmii_2_ValueChanged, TL_SaveEditor.valu_itemmii_3_ValueChanged, …) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 8 times rather than 8 independent problems. Splitting this body alone leaves the other 7 exactly as they are. Where these are variations on one operation, the change that clears all 8 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_manag_allmiis.Text_restore_Click (cognitive 26) Tomodachi Life Save Editor/TLSE_manag_allmiis.vb:601— TLSE_manag_allmiis.Text_restore_Click has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_extras.Check_resetstpspp_CheckedChanged (cognitive 23) Tomodachi Life Save Editor/TLSE_extras.vb:190— TLSE_extras.Check_resetstpspp_CheckedChanged has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_itemsedit.Writefoodsitems (cognitive 21) Tomodachi Life Save Editor/TLSE_itemsedit.vb:461— TLSE_itemsedit.Writefoodsitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_itemsedit.Writeclothesitems, TLSE_itemsedit.Writetreasuresitems, TLSE_itemsedit.Writespefoodsitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_itemsedit.Writeclothesitems (cognitive 21) Tomodachi Life Save Editor/TLSE_itemsedit.vb:491— TLSE_itemsedit.Writeclothesitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_itemsedit.Writefoodsitems, TLSE_itemsedit.Writetreasuresitems, TLSE_itemsedit.Writespefoodsitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_itemsedit.Writetreasuresitems (cognitive 21) Tomodachi Life Save Editor/TLSE_itemsedit.vb:3170— TLSE_itemsedit.Writetreasuresitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_itemsedit.Writefoodsitems, TLSE_itemsedit.Writeclothesitems, TLSE_itemsedit.Writespefoodsitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_itemsedit.Writespefoodsitems (cognitive 21) Tomodachi Life Save Editor/TLSE_itemsedit.vb:3203— TLSE_itemsedit.Writespefoodsitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TLSE_itemsedit.Writefoodsitems, TLSE_itemsedit.Writeclothesitems, TLSE_itemsedit.Writetreasuresitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Writefoodsitems (cognitive 21) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:9973— TL_SaveEditor.Writefoodsitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Writeclothesitems, TL_SaveEditor.Writetreasuresitems, TL_SaveEditor.Writespefoodsitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Writeclothesitems (cognitive 21) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:10003— TL_SaveEditor.Writeclothesitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Writefoodsitems, TL_SaveEditor.Writetreasuresitems, TL_SaveEditor.Writespefoodsitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Writetreasuresitems (cognitive 21) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:12682— TL_SaveEditor.Writetreasuresitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Writefoodsitems, TL_SaveEditor.Writeclothesitems, TL_SaveEditor.Writespefoodsitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Writespefoodsitems (cognitive 21) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:12715— TL_SaveEditor.Writespefoodsitems has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: 3 other methods here (TL_SaveEditor.Writefoodsitems, TL_SaveEditor.Writeclothesitems, TL_SaveEditor.Writetreasuresitems) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_hub.Checkupdates (cognitive 18) Tomodachi Life Save Editor/TLSE_hub.vb:892— TLSE_hub.Checkupdates has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_itemsedit.Writeinteriorsitems (cognitive 18) Tomodachi Life Save Editor/TLSE_itemsedit.vb:3116— TLSE_itemsedit.Writeinteriorsitems has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_itemsedit.Writegoodsitems) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_itemsedit.Writegoodsitems (cognitive 18) Tomodachi Life Save Editor/TLSE_itemsedit.vb:3143— TLSE_itemsedit.Writegoodsitems has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TLSE_itemsedit.Writeinteriorsitems) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Checkupdates (cognitive 18) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:409— TL_SaveEditor.Checkupdates has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Resetnewsflash (cognitive 18) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:6133— TL_SaveEditor.Resetnewsflash has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Writeinteriorsitems (cognitive 18) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:12628— TL_SaveEditor.Writeinteriorsitems has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TL_SaveEditor.Writegoodsitems) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TL_SaveEditor.Writegoodsitems (cognitive 18) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:12655— TL_SaveEditor.Writegoodsitems has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (TL_SaveEditor.Writeinteriorsitems) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
TLSE_manag_travelers.Text_restoremii_Click (cognitive 17) Tomodachi Life Save Editor/TLSE_manag_travelers.vb:966— TLSE_manag_travelers.Text_restoremii_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.Text_menu_open_Click (cognitive 17) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:3294— TL_SaveEditor.Text_menu_open_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TLSE_hub.Text_menu_open_Click (cognitive 16) Tomodachi Life Save Editor/TLSE_hub.vb:816— TLSE_hub.Text_menu_open_Click has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TL_SaveEditor.readmusic (cognitive 16) Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:8891— TL_SaveEditor.readmusic has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Near-duplicate member pair (408 shared lines) Tomodachi Life Save Editor/TLSE_crcxmodem.vb:975— Tomodachi Life Save Editor/TLSE_crcxmodem.vb:975-1390 | Tomodachi Life Save Editor/TLSE_interactions.vb:4345-4959 — These two members are variants of one another: 408 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (180 shared lines) Tomodachi Life Save Editor/TLSE_extras.vb:1060— Tomodachi Life Save Editor/TLSE_extras.vb:1060-1478 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48697-48909 — These two members are variants of one another: 180 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (15 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (15 members, 50+ identical tokens) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80017— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80017-80034 | Tomodachi Life Save Editor/TLSE_concertedit.vb:110-124 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:64-81 | Tomodachi Life Save Editor/TLSE_creaislandranking.vb:81-96 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:183-199 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:133-149 | Tomodachi Life Save Editor/TLSE_extras.vb:83-97 | Tomodachi Life Save Editor/TLSE_hub.vb:738-754 | Tomodachi Life Save Editor/TLSE_interactions.vb:583-599 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:118-133 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:93-109 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:84-99 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:81-95 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:81-95 | Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:82-97 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication· Members sharing a duplicated core (14 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (14 members, 50+ identical tokens) Tomodachi Life Save Editor/TLSE_concertedit.vb:878— Tomodachi Life Save Editor/TLSE_concertedit.vb:878-893 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:85-101 | Tomodachi Life Save Editor/TLSE_creaislandranking.vb:100-115 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:203-218 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:153-168 | Tomodachi Life Save Editor/TLSE_extras.vb:101-116 | Tomodachi Life Save Editor/TLSE_hub.vb:966-981 | Tomodachi Life Save Editor/TLSE_interactions.vb:603-618 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:137-152 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:113-128 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:103-118 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:99-114 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:99-114 | Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:101-116 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
Duplicated block (500 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:6449— Tomodachi Life Save Editor/TLSE_interactions.vb:6449-6948 | Tomodachi Life Save Editor/TLSE_interactions.vb:6950-7449 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (229 lines × 2) Tomodachi Life Save Editor/TLSE_creaislandranking.vb:152— Tomodachi Life Save Editor/TLSE_creaislandranking.vb:152-380 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:176-404 — before extracting anything, compare `Tomodachi Life Save Editor/TLSE_creaislandranking.vb` and `Tomodachi Life Save Editor/TLSE_islandinfo.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 287 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (199 lines × 5) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80064— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80064-80262 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:979-1177 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:1180-1378 | Tomodachi Life Save Editor/TLSE_interactions.vb:4349-4547 | Tomodachi Life Save Editor/TLSE_interactions.vb:4550-4748 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (199 lines × 3) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:238— Tomodachi Life Save Editor/TLSE_dataislandranking.vb:238-436 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:439-637 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:640-838 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (199 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:3928— Tomodachi Life Save Editor/TLSE_interactions.vb:3928-4126 | Tomodachi Life Save Editor/TLSE_interactions.vb:4129-4327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (100 lines × 3) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1475— Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1475-1574 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1576-1675 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1677-1776 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (99 lines × 3) Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:188— Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:188-286 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:289-387 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:390-488 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (50 lines × 3) Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:825— Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:825-874 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:876-925 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:927-976 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23–29 lines × 4) Tomodachi Life Save Editor/TLSE_itemsedit.vb:1450— Tomodachi Life Save Editor/TLSE_itemsedit.vb:1450-1478 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1880-1908 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2284-2306 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2586-2608 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (22 lines × 2) Tomodachi Life Save Editor/TLSE_concertedit.vb:643— Tomodachi Life Save Editor/TLSE_concertedit.vb:643-664 | Tomodachi Life Save Editor/TLSE_concertedit.vb:694-715 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 3) Tomodachi Life Save Editor/TLSE_islandconfig.vb:186— Tomodachi Life Save Editor/TLSE_islandconfig.vb:186-206 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:224-244 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:262-282 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (20 lines × 2) Tomodachi Life Save Editor/TLSE_extras.vb:2503— Tomodachi Life Save Editor/TLSE_extras.vb:2503-2522 | Tomodachi Life Save Editor/TLSE_extras.vb:3305-3324 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) Tomodachi Life Save Editor/TLSE_extras.vb:137— Tomodachi Life Save Editor/TLSE_extras.vb:137-153 | Tomodachi Life Save Editor/TLSE_extras.vb:155-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 4) Tomodachi Life Save Editor/TLSE_interactions.vb:5958— Tomodachi Life Save Editor/TLSE_interactions.vb:5958-5974 | Tomodachi Life Save Editor/TLSE_interactions.vb:5978-5994 | Tomodachi Life Save Editor/TLSE_interactions.vb:5998-6014 | Tomodachi Life Save Editor/TLSE_interactions.vb:6018-6034 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5153— Tomodachi Life Save Editor/TLSE_interactions.vb:5153-5167 | Tomodachi Life Save Editor/TLSE_interactions.vb:5185-5199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) Tomodachi Life Save Editor/TLSE_extras.vb:233— Tomodachi Life Save Editor/TLSE_extras.vb:233-248 | Tomodachi Life Save Editor/TLSE_extras.vb:635-650 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 14) Tomodachi Life Save Editor/TLSE_concertedit.vb:878— Tomodachi Life Save Editor/TLSE_concertedit.vb:878-893 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:85-100 | Tomodachi Life Save Editor/TLSE_creaislandranking.vb:100-115 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:203-218 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:153-168 | Tomodachi Life Save Editor/TLSE_extras.vb:101-116 | Tomodachi Life Save Editor/TLSE_hub.vb:966-981 | Tomodachi Life Save Editor/TLSE_interactions.vb:603-618 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:137-152 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:113-128 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:103-118 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:99-114 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:99-114 | Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:101-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 14 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Tomodachi Life Save Editor/TLSE_islandinfo.vb:131` calls `Icon_problemsolved_Click` and `Tomodachi Life Save Editor/TLSE_crcxmodem.vb:101` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 7) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46589— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46589-46602 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:46890-46903 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:47191-47204 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:47492-47505 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:47793-47806 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48094-48107 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48395-48408 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–14 lines × 4) Tomodachi Life Save Editor/TLSE_itemsedit.vb:1327— Tomodachi Life Save Editor/TLSE_itemsedit.vb:1327-1340 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1772-1785 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2197-2208 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2503-2514 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5759— Tomodachi Life Save Editor/TLSE_interactions.vb:5759-5772 | Tomodachi Life Save Editor/TLSE_interactions.vb:5777-5790 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 98) Tomodachi Life Save Editor/TLSE_extras.vb:2515— Tomodachi Life Save Editor/TLSE_extras.vb:2515-2526 | Tomodachi Life Save Editor/TLSE_extras.vb:2531-2542 | Tomodachi Life Save Editor/TLSE_extras.vb:2547-2558 | Tomodachi Life Save Editor/TLSE_extras.vb:2563-2574 | Tomodachi Life Save Editor/TLSE_extras.vb:2579-2590 | Tomodachi Life Save Editor/TLSE_extras.vb:2595-2606 | Tomodachi Life Save Editor/TLSE_extras.vb:2611-2622 | Tomodachi Life Save Editor/TLSE_extras.vb:2627-2638 | Tomodachi Life Save Editor/TLSE_extras.vb:2643-2654 | Tomodachi Life Save Editor/TLSE_extras.vb:2659-2670 | Tomodachi Life Save Editor/TLSE_extras.vb:2675-2686 | Tomodachi Life Save Editor/TLSE_extras.vb:2691-2702 | Tomodachi Life Save Editor/TLSE_extras.vb:2707-2718 | Tomodachi Life Save Editor/TLSE_extras.vb:2723-2734 | Tomodachi Life Save Editor/TLSE_extras.vb:2739-2750 | Tomodachi Life Save Editor/TLSE_extras.vb:2755-2766 | Tomodachi Life Save Editor/TLSE_extras.vb:2771-2782 | Tomodachi Life Save Editor/TLSE_extras.vb:2787-2798 | Tomodachi Life Save Editor/TLSE_extras.vb:2803-2814 | Tomodachi Life Save Editor/TLSE_extras.vb:2819-2830 | Tomodachi Life Save Editor/TLSE_extras.vb:2835-2846 | Tomodachi Life Save Editor/TLSE_extras.vb:2851-2862 | Tomodachi Life Save Editor/TLSE_extras.vb:2867-2878 | Tomodachi Life Save Editor/TLSE_extras.vb:2883-2894 | Tomodachi Life Save Editor/TLSE_extras.vb:2899-2910 | Tomodachi Life Save Editor/TLSE_extras.vb:2915-2926 | Tomodachi Life Save Editor/TLSE_extras.vb:2931-2942 | Tomodachi Life Save Editor/TLSE_extras.vb:2947-2958 | Tomodachi Life Save Editor/TLSE_extras.vb:2963-2974 | Tomodachi Life Save Editor/TLSE_extras.vb:2979-2990 | Tomodachi Life Save Editor/TLSE_extras.vb:2995-3006 | Tomodachi Life Save Editor/TLSE_extras.vb:3011-3022 | Tomodachi Life Save Editor/TLSE_extras.vb:3027-3038 | Tomodachi Life Save Editor/TLSE_extras.vb:3043-3054 | Tomodachi Life Save Editor/TLSE_extras.vb:3059-3070 | Tomodachi Life Save Editor/TLSE_extras.vb:3075-3086 | Tomodachi Life Save Editor/TLSE_extras.vb:3091-3102 | Tomodachi Life Save Editor/TLSE_extras.vb:3107-3118 | Tomodachi Life Save Editor/TLSE_extras.vb:3123-3134 | Tomodachi Life Save Editor/TLSE_extras.vb:3139-3150 | Tomodachi Life Save Editor/TLSE_extras.vb:3155-3166 | Tomodachi Life Save Editor/TLSE_extras.vb:3171-3182 | Tomodachi Life Save Editor/TLSE_extras.vb:3187-3198 | Tomodachi Life Save Editor/TLSE_extras.vb:3203-3214 | Tomodachi Life Save Editor/TLSE_extras.vb:3219-3230 | Tomodachi Life Save Editor/TLSE_extras.vb:3235-3246 | Tomodachi Life Save Editor/TLSE_extras.vb:3251-3262 | Tomodachi Life Save Editor/TLSE_extras.vb:3267-3278 | Tomodachi Life Save Editor/TLSE_extras.vb:3283-3294 | Tomodachi Life Save Editor/TLSE_extras.vb:3317-3328 | Tomodachi Life Save Editor/TLSE_extras.vb:3333-3344 | Tomodachi Life Save Editor/TLSE_extras.vb:3349-3360 | Tomodachi Life Save Editor/TLSE_extras.vb:3365-3376 | Tomodachi Life Save Editor/TLSE_extras.vb:3381-3392 | Tomodachi Life Save Editor/TLSE_extras.vb:3397-3408 | Tomodachi Life Save Editor/TLSE_extras.vb:3413-3424 | Tomodachi Life Save Editor/TLSE_extras.vb:3429-3440 | Tomodachi Life Save Editor/TLSE_extras.vb:3445-3456 | Tomodachi Life Save Editor/TLSE_extras.vb:3461-3472 | Tomodachi Life Save Editor/TLSE_extras.vb:3477-3488 | Tomodachi Life Save Editor/TLSE_extras.vb:3493-3504 | Tomodachi Life Save Editor/TLSE_extras.vb:3509-3520 | Tomodachi Life Save Editor/TLSE_extras.vb:3525-3536 | Tomodachi Life Save Editor/TLSE_extras.vb:3541-3552 | Tomodachi Life Save Editor/TLSE_extras.vb:3557-3568 | Tomodachi Life Save Editor/TLSE_extras.vb:3573-3584 | Tomodachi Life Save Editor/TLSE_extras.vb:3589-3600 | Tomodachi Life Save Editor/TLSE_extras.vb:3605-3616 | Tomodachi Life Save Editor/TLSE_extras.vb:3621-3632 | Tomodachi Life Save Editor/TLSE_extras.vb:3637-3648 | Tomodachi Life Save Editor/TLSE_extras.vb:3653-3664 | Tomodachi Life Save Editor/TLSE_extras.vb:3669-3680 | Tomodachi Life Save Editor/TLSE_extras.vb:3685-3696 | Tomodachi Life Save Editor/TLSE_extras.vb:3701-3712 | Tomodachi Life Save Editor/TLSE_extras.vb:3717-3728 | Tomodachi Life Save Editor/TLSE_extras.vb:3733-3744 | Tomodachi Life Save Editor/TLSE_extras.vb:3749-3760 | Tomodachi Life Save Editor/TLSE_extras.vb:3765-3776 | Tomodachi Life Save Editor/TLSE_extras.vb:3781-3792 | Tomodachi Life Save Editor/TLSE_extras.vb:3797-3808 | Tomodachi Life Save Editor/TLSE_extras.vb:3813-3824 | Tomodachi Life Save Editor/TLSE_extras.vb:3829-3840 | Tomodachi Life Save Editor/TLSE_extras.vb:3845-3856 | Tomodachi Life Save Editor/TLSE_extras.vb:3861-3872 | Tomodachi Life Save Editor/TLSE_extras.vb:3877-3888 | Tomodachi Life Save Editor/TLSE_extras.vb:3893-3904 | Tomodachi Life Save Editor/TLSE_extras.vb:3909-3920 | Tomodachi Life Save Editor/TLSE_extras.vb:3925-3936 | Tomodachi Life Save Editor/TLSE_extras.vb:3941-3952 | Tomodachi Life Save Editor/TLSE_extras.vb:3957-3968 | Tomodachi Life Save Editor/TLSE_extras.vb:3973-3984 | Tomodachi Life Save Editor/TLSE_extras.vb:3989-4000 | Tomodachi Life Save Editor/TLSE_extras.vb:4005-4016 | Tomodachi Life Save Editor/TLSE_extras.vb:4021-4032 | Tomodachi Life Save Editor/TLSE_extras.vb:4037-4048 | Tomodachi Life Save Editor/TLSE_extras.vb:4053-4064 | Tomodachi Life Save Editor/TLSE_extras.vb:4069-4080 | Tomodachi Life Save Editor/TLSE_extras.vb:4085-4096 — all 98 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) Tomodachi Life Save Editor/TLSE_concertedit.vb:666— Tomodachi Life Save Editor/TLSE_concertedit.vb:666-678 | Tomodachi Life Save Editor/TLSE_concertedit.vb:680-692 | Tomodachi Life Save Editor/TLSE_concertedit.vb:862-874 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 102) Tomodachi Life Save Editor/TLSE_itemsedit.vb:1330— Tomodachi Life Save Editor/TLSE_itemsedit.vb:1330-1344 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1345-1359 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1360-1374 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1375-1389 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1390-1404 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1405-1419 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1420-1434 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1435-1449 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1468-1482 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1483-1497 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1498-1512 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1513-1527 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1528-1542 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1543-1557 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1558-1572 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1573-1587 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1588-1602 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1603-1617 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1618-1632 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1633-1647 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1648-1662 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1663-1677 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1678-1692 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1693-1707 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1708-1722 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1723-1737 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1738-1752 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1753-1767 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1775-1789 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1790-1804 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1805-1819 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1820-1834 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1835-1849 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1850-1864 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1865-1879 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1898-1912 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1913-1927 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1928-1942 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1943-1957 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1958-1972 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1973-1987 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1988-2002 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2003-2017 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2018-2032 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2033-2047 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2048-2062 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2063-2077 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2078-2092 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2093-2107 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2108-2122 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2123-2137 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2138-2152 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2153-2167 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2168-2182 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2200-2211 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2212-2223 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2224-2235 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2236-2247 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2248-2259 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2260-2271 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2272-2283 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2298-2309 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2310-2321 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2322-2333 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2334-2345 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2346-2357 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2358-2369 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2370-2381 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2382-2393 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2394-2405 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2406-2417 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2418-2429 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2430-2441 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2442-2453 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2454-2465 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2466-2477 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2478-2489 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2506-2517 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2518-2529 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2530-2541 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2542-2553 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2554-2565 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2566-2577 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2578-2589 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2600-2611 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2612-2623 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2624-2635 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2636-2647 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2648-2659 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2660-2671 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2672-2683 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2684-2695 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2696-2707 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2708-2719 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2720-2731 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2732-2743 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2744-2755 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2756-2767 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2768-2779 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2780-2791 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2792-2803 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2804-2815 — all 102 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Tomodachi Life Save Editor/TLSE_itemsedit.vb:1465` calls `WriteByte` and `Tomodachi Life Save Editor/TLSE_itemsedit.vb:1342` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 64) Tomodachi Life Save Editor/TLSE_extras.vb:240— Tomodachi Life Save Editor/TLSE_extras.vb:240-248 | Tomodachi Life Save Editor/TLSE_extras.vb:252-260 | Tomodachi Life Save Editor/TLSE_extras.vb:264-272 | Tomodachi Life Save Editor/TLSE_extras.vb:276-284 | Tomodachi Life Save Editor/TLSE_extras.vb:288-296 | Tomodachi Life Save Editor/TLSE_extras.vb:300-308 | Tomodachi Life Save Editor/TLSE_extras.vb:312-320 | Tomodachi Life Save Editor/TLSE_extras.vb:324-332 | Tomodachi Life Save Editor/TLSE_extras.vb:336-344 | Tomodachi Life Save Editor/TLSE_extras.vb:348-356 | Tomodachi Life Save Editor/TLSE_extras.vb:360-368 | Tomodachi Life Save Editor/TLSE_extras.vb:372-380 | Tomodachi Life Save Editor/TLSE_extras.vb:384-392 | Tomodachi Life Save Editor/TLSE_extras.vb:396-404 | Tomodachi Life Save Editor/TLSE_extras.vb:408-416 | Tomodachi Life Save Editor/TLSE_extras.vb:420-428 | Tomodachi Life Save Editor/TLSE_extras.vb:432-440 | Tomodachi Life Save Editor/TLSE_extras.vb:444-452 | Tomodachi Life Save Editor/TLSE_extras.vb:456-464 | Tomodachi Life Save Editor/TLSE_extras.vb:468-476 | Tomodachi Life Save Editor/TLSE_extras.vb:480-488 | Tomodachi Life Save Editor/TLSE_extras.vb:492-500 | Tomodachi Life Save Editor/TLSE_extras.vb:504-512 | Tomodachi Life Save Editor/TLSE_extras.vb:516-524 | Tomodachi Life Save Editor/TLSE_extras.vb:528-536 | Tomodachi Life Save Editor/TLSE_extras.vb:540-548 | Tomodachi Life Save Editor/TLSE_extras.vb:552-560 | Tomodachi Life Save Editor/TLSE_extras.vb:564-572 | Tomodachi Life Save Editor/TLSE_extras.vb:576-584 | Tomodachi Life Save Editor/TLSE_extras.vb:588-596 | Tomodachi Life Save Editor/TLSE_extras.vb:600-608 | Tomodachi Life Save Editor/TLSE_extras.vb:612-620 | Tomodachi Life Save Editor/TLSE_extras.vb:642-650 | Tomodachi Life Save Editor/TLSE_extras.vb:654-662 | Tomodachi Life Save Editor/TLSE_extras.vb:666-674 | Tomodachi Life Save Editor/TLSE_extras.vb:678-686 | Tomodachi Life Save Editor/TLSE_extras.vb:690-698 | Tomodachi Life Save Editor/TLSE_extras.vb:702-710 | Tomodachi Life Save Editor/TLSE_extras.vb:714-722 | Tomodachi Life Save Editor/TLSE_extras.vb:726-734 | Tomodachi Life Save Editor/TLSE_extras.vb:738-746 | Tomodachi Life Save Editor/TLSE_extras.vb:750-758 | Tomodachi Life Save Editor/TLSE_extras.vb:762-770 | Tomodachi Life Save Editor/TLSE_extras.vb:774-782 | Tomodachi Life Save Editor/TLSE_extras.vb:786-794 | Tomodachi Life Save Editor/TLSE_extras.vb:798-806 | Tomodachi Life Save Editor/TLSE_extras.vb:810-818 | Tomodachi Life Save Editor/TLSE_extras.vb:822-830 | Tomodachi Life Save Editor/TLSE_extras.vb:834-842 | Tomodachi Life Save Editor/TLSE_extras.vb:846-854 | Tomodachi Life Save Editor/TLSE_extras.vb:858-866 | Tomodachi Life Save Editor/TLSE_extras.vb:870-878 | Tomodachi Life Save Editor/TLSE_extras.vb:882-890 | Tomodachi Life Save Editor/TLSE_extras.vb:894-902 | Tomodachi Life Save Editor/TLSE_extras.vb:906-914 | Tomodachi Life Save Editor/TLSE_extras.vb:918-926 | Tomodachi Life Save Editor/TLSE_extras.vb:930-938 | Tomodachi Life Save Editor/TLSE_extras.vb:942-950 | Tomodachi Life Save Editor/TLSE_extras.vb:954-962 | Tomodachi Life Save Editor/TLSE_extras.vb:966-974 | Tomodachi Life Save Editor/TLSE_extras.vb:978-986 | Tomodachi Life Save Editor/TLSE_extras.vb:990-998 | Tomodachi Life Save Editor/TLSE_extras.vb:1002-1010 | Tomodachi Life Save Editor/TLSE_extras.vb:1014-1022 — all 64 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 62) Tomodachi Life Save Editor/TLSE_itemsedit.vb:530— Tomodachi Life Save Editor/TLSE_itemsedit.vb:530-539 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:542-551 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:554-563 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:566-575 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:578-587 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:590-599 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:602-611 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:614-623 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:626-635 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:638-647 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:650-659 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:662-671 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:674-683 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:686-695 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:698-707 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:729-738 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:741-750 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:753-762 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:765-774 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:777-786 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:789-798 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:801-810 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:813-822 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:825-834 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:837-846 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:849-858 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:861-870 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:873-882 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:885-894 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:897-906 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:920-929 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:932-941 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:944-953 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:956-965 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:968-977 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:980-989 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:992-1001 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1004-1013 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1016-1025 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1028-1037 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1040-1049 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1052-1061 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1064-1073 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1076-1085 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1088-1097 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1115-1124 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1127-1136 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1139-1148 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1151-1160 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1163-1172 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1175-1184 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1187-1196 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1199-1208 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1211-1220 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1223-1232 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1235-1244 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1247-1256 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1259-1268 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1271-1280 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1283-1292 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1295-1304 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:1307-1316 — all 62 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 20) Tomodachi Life Save Editor/TLSE_itemsedit.vb:2833— Tomodachi Life Save Editor/TLSE_itemsedit.vb:2833-2842 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2845-2854 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2857-2866 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2869-2878 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2881-2890 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2908-2917 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2920-2929 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2932-2941 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2944-2953 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2956-2965 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2979-2988 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2991-3000 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3003-3012 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3015-3024 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3027-3036 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3050-3059 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3062-3071 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3074-3083 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3086-3095 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3098-3107 — all 20 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 6) Tomodachi Life Save Editor/TLSE_concertedit.vb:643— Tomodachi Life Save Editor/TLSE_concertedit.vb:643-652 | Tomodachi Life Save Editor/TLSE_concertedit.vb:655-664 | Tomodachi Life Save Editor/TLSE_concertedit.vb:680-689 | Tomodachi Life Save Editor/TLSE_concertedit.vb:694-703 | Tomodachi Life Save Editor/TLSE_concertedit.vb:706-715 | Tomodachi Life Save Editor/TLSE_concertedit.vb:718-727 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) Tomodachi Life Save Editor/TLSE_itemsedit.vb:1758— Tomodachi Life Save Editor/TLSE_itemsedit.vb:1758-1771 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2183-2196 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2490-2502 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:2812-2823 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 48) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:859— Tomodachi Life Save Editor/TLSE_dataislandranking.vb:859-867 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:871-879 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:883-891 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:895-903 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:907-915 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:919-927 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:931-939 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:943-951 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:955-963 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:967-975 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:979-987 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:991-999 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1003-1011 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1015-1023 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1027-1035 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1039-1047 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1060-1068 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1072-1080 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1084-1092 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1096-1104 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1108-1116 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1120-1128 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1132-1140 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1144-1152 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1156-1164 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1168-1176 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1180-1188 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1192-1200 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1204-1212 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1216-1224 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1228-1236 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1240-1248 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1261-1269 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1273-1281 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1285-1293 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1297-1305 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1309-1317 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1321-1329 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1333-1341 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1345-1353 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1357-1365 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1369-1377 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1381-1389 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1393-1401 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1405-1413 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1417-1425 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1429-1437 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1441-1449 — all 48 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 40) Tomodachi Life Save Editor/TLSE_interactions.vb:5009— Tomodachi Life Save Editor/TLSE_interactions.vb:5009-5018 | Tomodachi Life Save Editor/TLSE_interactions.vb:5021-5030 | Tomodachi Life Save Editor/TLSE_interactions.vb:5033-5042 | Tomodachi Life Save Editor/TLSE_interactions.vb:5045-5054 | Tomodachi Life Save Editor/TLSE_interactions.vb:5057-5066 | Tomodachi Life Save Editor/TLSE_interactions.vb:5069-5078 | Tomodachi Life Save Editor/TLSE_interactions.vb:5081-5090 | Tomodachi Life Save Editor/TLSE_interactions.vb:5093-5102 | Tomodachi Life Save Editor/TLSE_interactions.vb:5105-5114 | Tomodachi Life Save Editor/TLSE_interactions.vb:5117-5126 | Tomodachi Life Save Editor/TLSE_interactions.vb:5129-5138 | Tomodachi Life Save Editor/TLSE_interactions.vb:5164-5173 | Tomodachi Life Save Editor/TLSE_interactions.vb:5176-5185 | Tomodachi Life Save Editor/TLSE_interactions.vb:5196-5205 | Tomodachi Life Save Editor/TLSE_interactions.vb:5208-5217 | Tomodachi Life Save Editor/TLSE_interactions.vb:5220-5229 | Tomodachi Life Save Editor/TLSE_interactions.vb:5242-5251 | Tomodachi Life Save Editor/TLSE_interactions.vb:5254-5263 | Tomodachi Life Save Editor/TLSE_interactions.vb:5266-5275 | Tomodachi Life Save Editor/TLSE_interactions.vb:5278-5287 | Tomodachi Life Save Editor/TLSE_interactions.vb:5290-5299 | Tomodachi Life Save Editor/TLSE_interactions.vb:5302-5311 | Tomodachi Life Save Editor/TLSE_interactions.vb:5314-5323 | Tomodachi Life Save Editor/TLSE_interactions.vb:5326-5335 | Tomodachi Life Save Editor/TLSE_interactions.vb:5348-5357 | Tomodachi Life Save Editor/TLSE_interactions.vb:5360-5369 | Tomodachi Life Save Editor/TLSE_interactions.vb:5372-5381 | Tomodachi Life Save Editor/TLSE_interactions.vb:5384-5393 | Tomodachi Life Save Editor/TLSE_interactions.vb:5396-5405 | Tomodachi Life Save Editor/TLSE_interactions.vb:5408-5417 | Tomodachi Life Save Editor/TLSE_interactions.vb:5420-5429 | Tomodachi Life Save Editor/TLSE_interactions.vb:5432-5441 | Tomodachi Life Save Editor/TLSE_interactions.vb:5794-5803 | Tomodachi Life Save Editor/TLSE_interactions.vb:5806-5815 | Tomodachi Life Save Editor/TLSE_interactions.vb:5818-5827 | Tomodachi Life Save Editor/TLSE_interactions.vb:5830-5839 | Tomodachi Life Save Editor/TLSE_interactions.vb:5860-5869 | Tomodachi Life Save Editor/TLSE_interactions.vb:5872-5881 | Tomodachi Life Save Editor/TLSE_interactions.vb:5940-5949 | Tomodachi Life Save Editor/TLSE_interactions.vb:6100-6109 — all 40 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 24) Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:509— Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:509-517 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:521-529 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:533-541 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:545-553 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:557-565 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:569-577 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:581-589 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:593-601 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:610-618 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:622-630 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:634-642 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:646-654 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:658-666 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:670-678 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:682-690 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:694-702 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:711-719 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:723-731 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:735-743 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:747-755 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:759-767 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:771-779 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:783-791 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:795-803 — all 24 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 14) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80018— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80018-80027 | Tomodachi Life Save Editor/TLSE_concertedit.vb:111-120 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:65-74 | Tomodachi Life Save Editor/TLSE_creaislandranking.vb:82-91 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:184-193 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:134-143 | Tomodachi Life Save Editor/TLSE_extras.vb:84-93 | Tomodachi Life Save Editor/TLSE_interactions.vb:584-593 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:119-128 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:94-103 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:85-94 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:82-91 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:82-91 | Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:83-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 14 call sites, so a change lands once.
Duplicated block (8 lines × 42) Tomodachi Life Save Editor/TLSE_interactions.vb:4989— Tomodachi Life Save Editor/TLSE_interactions.vb:4989-4996 | Tomodachi Life Save Editor/TLSE_interactions.vb:5011-5018 | Tomodachi Life Save Editor/TLSE_interactions.vb:5023-5030 | Tomodachi Life Save Editor/TLSE_interactions.vb:5035-5042 | Tomodachi Life Save Editor/TLSE_interactions.vb:5047-5054 | Tomodachi Life Save Editor/TLSE_interactions.vb:5059-5066 | Tomodachi Life Save Editor/TLSE_interactions.vb:5071-5078 | Tomodachi Life Save Editor/TLSE_interactions.vb:5083-5090 | Tomodachi Life Save Editor/TLSE_interactions.vb:5095-5102 | Tomodachi Life Save Editor/TLSE_interactions.vb:5107-5114 | Tomodachi Life Save Editor/TLSE_interactions.vb:5119-5126 | Tomodachi Life Save Editor/TLSE_interactions.vb:5131-5138 | Tomodachi Life Save Editor/TLSE_interactions.vb:5166-5173 | Tomodachi Life Save Editor/TLSE_interactions.vb:5178-5185 | Tomodachi Life Save Editor/TLSE_interactions.vb:5198-5205 | Tomodachi Life Save Editor/TLSE_interactions.vb:5210-5217 | Tomodachi Life Save Editor/TLSE_interactions.vb:5222-5229 | Tomodachi Life Save Editor/TLSE_interactions.vb:5244-5251 | Tomodachi Life Save Editor/TLSE_interactions.vb:5256-5263 | Tomodachi Life Save Editor/TLSE_interactions.vb:5268-5275 | Tomodachi Life Save Editor/TLSE_interactions.vb:5280-5287 | Tomodachi Life Save Editor/TLSE_interactions.vb:5292-5299 | Tomodachi Life Save Editor/TLSE_interactions.vb:5304-5311 | Tomodachi Life Save Editor/TLSE_interactions.vb:5316-5323 | Tomodachi Life Save Editor/TLSE_interactions.vb:5328-5335 | Tomodachi Life Save Editor/TLSE_interactions.vb:5350-5357 | Tomodachi Life Save Editor/TLSE_interactions.vb:5362-5369 | Tomodachi Life Save Editor/TLSE_interactions.vb:5374-5381 | Tomodachi Life Save Editor/TLSE_interactions.vb:5386-5393 | Tomodachi Life Save Editor/TLSE_interactions.vb:5398-5405 | Tomodachi Life Save Editor/TLSE_interactions.vb:5410-5417 | Tomodachi Life Save Editor/TLSE_interactions.vb:5422-5429 | Tomodachi Life Save Editor/TLSE_interactions.vb:5434-5441 | Tomodachi Life Save Editor/TLSE_interactions.vb:5790-5797 | Tomodachi Life Save Editor/TLSE_interactions.vb:5802-5809 | Tomodachi Life Save Editor/TLSE_interactions.vb:5814-5821 | Tomodachi Life Save Editor/TLSE_interactions.vb:5826-5833 | Tomodachi Life Save Editor/TLSE_interactions.vb:5838-5845 | Tomodachi Life Save Editor/TLSE_interactions.vb:5862-5869 | Tomodachi Life Save Editor/TLSE_interactions.vb:5874-5881 | Tomodachi Life Save Editor/TLSE_interactions.vb:5942-5949 | Tomodachi Life Save Editor/TLSE_interactions.vb:6102-6109 — all 42 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 41) Tomodachi Life Save Editor/TLSE_interactions.vb:5009— Tomodachi Life Save Editor/TLSE_interactions.vb:5009-5018 | Tomodachi Life Save Editor/TLSE_interactions.vb:5021-5030 | Tomodachi Life Save Editor/TLSE_interactions.vb:5033-5042 | Tomodachi Life Save Editor/TLSE_interactions.vb:5045-5054 | Tomodachi Life Save Editor/TLSE_interactions.vb:5057-5066 | Tomodachi Life Save Editor/TLSE_interactions.vb:5069-5078 | Tomodachi Life Save Editor/TLSE_interactions.vb:5081-5090 | Tomodachi Life Save Editor/TLSE_interactions.vb:5093-5102 | Tomodachi Life Save Editor/TLSE_interactions.vb:5105-5114 | Tomodachi Life Save Editor/TLSE_interactions.vb:5117-5126 | Tomodachi Life Save Editor/TLSE_interactions.vb:5129-5138 | Tomodachi Life Save Editor/TLSE_interactions.vb:5141-5150 | Tomodachi Life Save Editor/TLSE_interactions.vb:5164-5173 | Tomodachi Life Save Editor/TLSE_interactions.vb:5176-5185 | Tomodachi Life Save Editor/TLSE_interactions.vb:5196-5205 | Tomodachi Life Save Editor/TLSE_interactions.vb:5208-5217 | Tomodachi Life Save Editor/TLSE_interactions.vb:5220-5229 | Tomodachi Life Save Editor/TLSE_interactions.vb:5242-5251 | Tomodachi Life Save Editor/TLSE_interactions.vb:5254-5263 | Tomodachi Life Save Editor/TLSE_interactions.vb:5266-5275 | Tomodachi Life Save Editor/TLSE_interactions.vb:5278-5287 | Tomodachi Life Save Editor/TLSE_interactions.vb:5290-5299 | Tomodachi Life Save Editor/TLSE_interactions.vb:5302-5311 | Tomodachi Life Save Editor/TLSE_interactions.vb:5314-5323 | Tomodachi Life Save Editor/TLSE_interactions.vb:5326-5335 | Tomodachi Life Save Editor/TLSE_interactions.vb:5348-5357 | Tomodachi Life Save Editor/TLSE_interactions.vb:5360-5369 | Tomodachi Life Save Editor/TLSE_interactions.vb:5372-5381 | Tomodachi Life Save Editor/TLSE_interactions.vb:5384-5393 | Tomodachi Life Save Editor/TLSE_interactions.vb:5396-5405 | Tomodachi Life Save Editor/TLSE_interactions.vb:5408-5417 | Tomodachi Life Save Editor/TLSE_interactions.vb:5420-5429 | Tomodachi Life Save Editor/TLSE_interactions.vb:5432-5441 | Tomodachi Life Save Editor/TLSE_interactions.vb:5794-5803 | Tomodachi Life Save Editor/TLSE_interactions.vb:5806-5815 | Tomodachi Life Save Editor/TLSE_interactions.vb:5818-5827 | Tomodachi Life Save Editor/TLSE_interactions.vb:5830-5839 | Tomodachi Life Save Editor/TLSE_interactions.vb:5860-5869 | Tomodachi Life Save Editor/TLSE_interactions.vb:5872-5881 | Tomodachi Life Save Editor/TLSE_interactions.vb:5940-5949 | Tomodachi Life Save Editor/TLSE_interactions.vb:6100-6109 — all 41 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 5) Tomodachi Life Save Editor/TLSE_interactions.vb:5725— Tomodachi Life Save Editor/TLSE_interactions.vb:5725-5731 | Tomodachi Life Save Editor/TLSE_interactions.vb:5735-5741 | Tomodachi Life Save Editor/TLSE_interactions.vb:5745-5751 | Tomodachi Life Save Editor/TLSE_interactions.vb:5755-5761 | Tomodachi Life Save Editor/TLSE_interactions.vb:5901-5907 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 2) Tomodachi Life Save Editor/TLSE_interactions.vb:5645— Tomodachi Life Save Editor/TLSE_interactions.vb:5645-5652 | Tomodachi Life Save Editor/TLSE_interactions.vb:5673-5680 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 66) Tomodachi Life Save Editor/TLSE_crcxmodem.vb:168— Tomodachi Life Save Editor/TLSE_crcxmodem.vb:168-172 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:180-184 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:192-196 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:204-208 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:216-220 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:228-232 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:240-244 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:252-256 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:264-268 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:276-280 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:288-292 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:300-304 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:312-316 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:324-328 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:336-340 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:348-352 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:360-364 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:372-376 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:384-388 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:396-400 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:408-412 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:420-424 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:432-436 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:444-448 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:456-460 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:468-472 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:480-484 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:492-496 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:504-508 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:516-520 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:528-532 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:540-544 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:552-556 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:572-576 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:584-588 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:596-600 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:608-612 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:620-624 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:632-636 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:644-648 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:656-660 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:668-672 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:680-684 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:692-696 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:704-708 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:716-720 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:728-732 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:740-744 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:752-756 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:764-768 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:776-780 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:788-792 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:800-804 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:812-816 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:824-828 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:836-840 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:848-852 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:860-864 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:872-876 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:884-888 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:896-900 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:908-912 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:920-924 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:932-936 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:944-948 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:956-960 — all 66 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6–9 lines × 50) Tomodachi Life Save Editor/TLSE_extras.vb:1575— Tomodachi Life Save Editor/TLSE_extras.vb:1575-1583 | Tomodachi Life Save Editor/TLSE_extras.vb:1591-1599 | Tomodachi Life Save Editor/TLSE_extras.vb:1607-1615 | Tomodachi Life Save Editor/TLSE_extras.vb:1623-1631 | Tomodachi Life Save Editor/TLSE_extras.vb:1639-1647 | Tomodachi Life Save Editor/TLSE_extras.vb:1655-1663 | Tomodachi Life Save Editor/TLSE_extras.vb:1671-1679 | Tomodachi Life Save Editor/TLSE_extras.vb:1687-1695 | Tomodachi Life Save Editor/TLSE_extras.vb:1703-1711 | Tomodachi Life Save Editor/TLSE_extras.vb:1719-1727 | Tomodachi Life Save Editor/TLSE_extras.vb:1735-1743 | Tomodachi Life Save Editor/TLSE_extras.vb:1751-1759 | Tomodachi Life Save Editor/TLSE_extras.vb:1767-1775 | Tomodachi Life Save Editor/TLSE_extras.vb:1783-1791 | Tomodachi Life Save Editor/TLSE_extras.vb:1799-1807 | Tomodachi Life Save Editor/TLSE_extras.vb:1815-1823 | Tomodachi Life Save Editor/TLSE_extras.vb:1831-1839 | Tomodachi Life Save Editor/TLSE_extras.vb:1847-1855 | Tomodachi Life Save Editor/TLSE_extras.vb:1863-1871 | Tomodachi Life Save Editor/TLSE_extras.vb:1879-1887 | Tomodachi Life Save Editor/TLSE_extras.vb:1895-1903 | Tomodachi Life Save Editor/TLSE_extras.vb:1911-1919 | Tomodachi Life Save Editor/TLSE_extras.vb:1927-1935 | Tomodachi Life Save Editor/TLSE_extras.vb:1943-1951 | Tomodachi Life Save Editor/TLSE_extras.vb:1959-1967 | Tomodachi Life Save Editor/TLSE_extras.vb:1975-1983 | Tomodachi Life Save Editor/TLSE_extras.vb:1991-1999 | Tomodachi Life Save Editor/TLSE_extras.vb:2007-2015 | Tomodachi Life Save Editor/TLSE_extras.vb:2023-2031 | Tomodachi Life Save Editor/TLSE_extras.vb:2039-2047 | Tomodachi Life Save Editor/TLSE_extras.vb:2055-2063 | Tomodachi Life Save Editor/TLSE_extras.vb:2071-2079 | Tomodachi Life Save Editor/TLSE_extras.vb:2087-2095 | Tomodachi Life Save Editor/TLSE_extras.vb:2103-2111 | Tomodachi Life Save Editor/TLSE_extras.vb:2119-2127 | Tomodachi Life Save Editor/TLSE_extras.vb:2135-2143 | Tomodachi Life Save Editor/TLSE_extras.vb:2151-2159 | Tomodachi Life Save Editor/TLSE_extras.vb:2167-2175 | Tomodachi Life Save Editor/TLSE_extras.vb:2183-2191 | Tomodachi Life Save Editor/TLSE_extras.vb:2199-2207 | Tomodachi Life Save Editor/TLSE_extras.vb:2215-2223 | Tomodachi Life Save Editor/TLSE_extras.vb:2231-2239 | Tomodachi Life Save Editor/TLSE_extras.vb:2247-2255 | Tomodachi Life Save Editor/TLSE_extras.vb:2263-2271 | Tomodachi Life Save Editor/TLSE_extras.vb:2279-2287 | Tomodachi Life Save Editor/TLSE_extras.vb:2295-2303 | Tomodachi Life Save Editor/TLSE_extras.vb:2311-2319 | Tomodachi Life Save Editor/TLSE_extras.vb:2327-2335 | Tomodachi Life Save Editor/TLSE_extras.vb:2343-2351 | Tomodachi Life Save Editor/TLSE_extras.vb:2355-2360 — all 50 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 4) Tomodachi Life Save Editor/TLSE_itemsedit.vb:3206— Tomodachi Life Save Editor/TLSE_itemsedit.vb:3206-3213 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3215-3222 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3224-3231 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:3233-3240 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 72) Tomodachi Life Save Editor/TLSE_extras.vb:1066— Tomodachi Life Save Editor/TLSE_extras.vb:1066-1072 | Tomodachi Life Save Editor/TLSE_extras.vb:1074-1080 | Tomodachi Life Save Editor/TLSE_extras.vb:1082-1088 | Tomodachi Life Save Editor/TLSE_extras.vb:1090-1096 | Tomodachi Life Save Editor/TLSE_extras.vb:1098-1104 | Tomodachi Life Save Editor/TLSE_extras.vb:1106-1112 | Tomodachi Life Save Editor/TLSE_extras.vb:1114-1120 | Tomodachi Life Save Editor/TLSE_extras.vb:1122-1128 | Tomodachi Life Save Editor/TLSE_extras.vb:1130-1136 | Tomodachi Life Save Editor/TLSE_extras.vb:1138-1144 | Tomodachi Life Save Editor/TLSE_extras.vb:1146-1152 | Tomodachi Life Save Editor/TLSE_extras.vb:1154-1160 | Tomodachi Life Save Editor/TLSE_extras.vb:1162-1168 | Tomodachi Life Save Editor/TLSE_extras.vb:1170-1176 | Tomodachi Life Save Editor/TLSE_extras.vb:1178-1184 | Tomodachi Life Save Editor/TLSE_extras.vb:1186-1192 | Tomodachi Life Save Editor/TLSE_extras.vb:1194-1200 | Tomodachi Life Save Editor/TLSE_extras.vb:1202-1208 | Tomodachi Life Save Editor/TLSE_extras.vb:1210-1216 | Tomodachi Life Save Editor/TLSE_extras.vb:1218-1224 | Tomodachi Life Save Editor/TLSE_extras.vb:1226-1232 | Tomodachi Life Save Editor/TLSE_extras.vb:1234-1240 | Tomodachi Life Save Editor/TLSE_extras.vb:1242-1248 | Tomodachi Life Save Editor/TLSE_extras.vb:1250-1256 | Tomodachi Life Save Editor/TLSE_extras.vb:1269-1275 | Tomodachi Life Save Editor/TLSE_extras.vb:1277-1283 | Tomodachi Life Save Editor/TLSE_extras.vb:1285-1291 | Tomodachi Life Save Editor/TLSE_extras.vb:1293-1299 | Tomodachi Life Save Editor/TLSE_extras.vb:1301-1307 | Tomodachi Life Save Editor/TLSE_extras.vb:1309-1315 | Tomodachi Life Save Editor/TLSE_extras.vb:1317-1323 | Tomodachi Life Save Editor/TLSE_extras.vb:1325-1331 | Tomodachi Life Save Editor/TLSE_extras.vb:1333-1339 | Tomodachi Life Save Editor/TLSE_extras.vb:1341-1347 | Tomodachi Life Save Editor/TLSE_extras.vb:1349-1355 | Tomodachi Life Save Editor/TLSE_extras.vb:1357-1363 | Tomodachi Life Save Editor/TLSE_extras.vb:1365-1371 | Tomodachi Life Save Editor/TLSE_extras.vb:1373-1379 | Tomodachi Life Save Editor/TLSE_extras.vb:1381-1387 | Tomodachi Life Save Editor/TLSE_extras.vb:1389-1395 | Tomodachi Life Save Editor/TLSE_extras.vb:1397-1403 | Tomodachi Life Save Editor/TLSE_extras.vb:1405-1411 | Tomodachi Life Save Editor/TLSE_extras.vb:1413-1419 | Tomodachi Life Save Editor/TLSE_extras.vb:1421-1427 | Tomodachi Life Save Editor/TLSE_extras.vb:1429-1435 | Tomodachi Life Save Editor/TLSE_extras.vb:1437-1443 | Tomodachi Life Save Editor/TLSE_extras.vb:1445-1451 | Tomodachi Life Save Editor/TLSE_extras.vb:1453-1459 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48702-48708 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48710-48716 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48718-48724 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48726-48732 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48734-48740 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48742-48748 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48750-48756 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48758-48764 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48766-48772 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48774-48780 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48782-48788 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48790-48796 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48798-48804 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48806-48812 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48814-48820 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48822-48828 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48830-48836 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48838-48844 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48846-48852 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48854-48860 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48862-48868 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48870-48876 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48878-48884 | Tomodachi Life Save Editor/TLSE_Jrelationships.vb:48886-48892 — there are 72 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 72 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 42) Tomodachi Life Save Editor/TLSE_interactions.vb:4993— Tomodachi Life Save Editor/TLSE_interactions.vb:4993-4999 | Tomodachi Life Save Editor/TLSE_interactions.vb:5009-5015 | Tomodachi Life Save Editor/TLSE_interactions.vb:5021-5027 | Tomodachi Life Save Editor/TLSE_interactions.vb:5033-5039 | Tomodachi Life Save Editor/TLSE_interactions.vb:5045-5051 | Tomodachi Life Save Editor/TLSE_interactions.vb:5057-5063 | Tomodachi Life Save Editor/TLSE_interactions.vb:5069-5075 | Tomodachi Life Save Editor/TLSE_interactions.vb:5081-5087 | Tomodachi Life Save Editor/TLSE_interactions.vb:5093-5099 | Tomodachi Life Save Editor/TLSE_interactions.vb:5105-5111 | Tomodachi Life Save Editor/TLSE_interactions.vb:5117-5123 | Tomodachi Life Save Editor/TLSE_interactions.vb:5129-5135 | Tomodachi Life Save Editor/TLSE_interactions.vb:5141-5147 | Tomodachi Life Save Editor/TLSE_interactions.vb:5164-5170 | Tomodachi Life Save Editor/TLSE_interactions.vb:5176-5182 | Tomodachi Life Save Editor/TLSE_interactions.vb:5196-5202 | Tomodachi Life Save Editor/TLSE_interactions.vb:5208-5214 | Tomodachi Life Save Editor/TLSE_interactions.vb:5220-5226 | Tomodachi Life Save Editor/TLSE_interactions.vb:5242-5248 | Tomodachi Life Save Editor/TLSE_interactions.vb:5254-5260 | Tomodachi Life Save Editor/TLSE_interactions.vb:5266-5272 | Tomodachi Life Save Editor/TLSE_interactions.vb:5278-5284 | Tomodachi Life Save Editor/TLSE_interactions.vb:5290-5296 | Tomodachi Life Save Editor/TLSE_interactions.vb:5302-5308 | Tomodachi Life Save Editor/TLSE_interactions.vb:5314-5320 | Tomodachi Life Save Editor/TLSE_interactions.vb:5326-5332 | Tomodachi Life Save Editor/TLSE_interactions.vb:5348-5354 | Tomodachi Life Save Editor/TLSE_interactions.vb:5360-5366 | Tomodachi Life Save Editor/TLSE_interactions.vb:5372-5378 | Tomodachi Life Save Editor/TLSE_interactions.vb:5384-5390 | Tomodachi Life Save Editor/TLSE_interactions.vb:5396-5402 | Tomodachi Life Save Editor/TLSE_interactions.vb:5408-5414 | Tomodachi Life Save Editor/TLSE_interactions.vb:5420-5426 | Tomodachi Life Save Editor/TLSE_interactions.vb:5432-5438 | Tomodachi Life Save Editor/TLSE_interactions.vb:5794-5800 | Tomodachi Life Save Editor/TLSE_interactions.vb:5806-5812 | Tomodachi Life Save Editor/TLSE_interactions.vb:5818-5824 | Tomodachi Life Save Editor/TLSE_interactions.vb:5830-5836 | Tomodachi Life Save Editor/TLSE_interactions.vb:5860-5866 | Tomodachi Life Save Editor/TLSE_interactions.vb:5872-5878 | Tomodachi Life Save Editor/TLSE_interactions.vb:5940-5946 | Tomodachi Life Save Editor/TLSE_interactions.vb:6100-6106 — all 42 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 36) Tomodachi Life Save Editor/TLSE_interactions.vb:6154— Tomodachi Life Save Editor/TLSE_interactions.vb:6154-6161 | Tomodachi Life Save Editor/TLSE_interactions.vb:6162-6169 | Tomodachi Life Save Editor/TLSE_interactions.vb:6170-6177 | Tomodachi Life Save Editor/TLSE_interactions.vb:6178-6185 | Tomodachi Life Save Editor/TLSE_interactions.vb:6186-6193 | Tomodachi Life Save Editor/TLSE_interactions.vb:6194-6201 | Tomodachi Life Save Editor/TLSE_interactions.vb:6202-6209 | Tomodachi Life Save Editor/TLSE_interactions.vb:6210-6217 | Tomodachi Life Save Editor/TLSE_interactions.vb:6218-6225 | Tomodachi Life Save Editor/TLSE_interactions.vb:6226-6233 | Tomodachi Life Save Editor/TLSE_interactions.vb:6234-6241 | Tomodachi Life Save Editor/TLSE_interactions.vb:6242-6249 | Tomodachi Life Save Editor/TLSE_interactions.vb:6250-6257 | Tomodachi Life Save Editor/TLSE_interactions.vb:6258-6265 | Tomodachi Life Save Editor/TLSE_interactions.vb:6266-6273 | Tomodachi Life Save Editor/TLSE_interactions.vb:6274-6281 | Tomodachi Life Save Editor/TLSE_interactions.vb:6282-6289 | Tomodachi Life Save Editor/TLSE_interactions.vb:6290-6297 | Tomodachi Life Save Editor/TLSE_interactions.vb:6298-6305 | Tomodachi Life Save Editor/TLSE_interactions.vb:6306-6313 | Tomodachi Life Save Editor/TLSE_interactions.vb:6314-6321 | Tomodachi Life Save Editor/TLSE_interactions.vb:6322-6329 | Tomodachi Life Save Editor/TLSE_interactions.vb:6330-6337 | Tomodachi Life Save Editor/TLSE_interactions.vb:6338-6345 | Tomodachi Life Save Editor/TLSE_interactions.vb:6346-6353 | Tomodachi Life Save Editor/TLSE_interactions.vb:6354-6361 | Tomodachi Life Save Editor/TLSE_interactions.vb:6362-6369 | Tomodachi Life Save Editor/TLSE_interactions.vb:6370-6377 | Tomodachi Life Save Editor/TLSE_interactions.vb:6378-6385 | Tomodachi Life Save Editor/TLSE_interactions.vb:6386-6393 | Tomodachi Life Save Editor/TLSE_interactions.vb:6394-6401 | Tomodachi Life Save Editor/TLSE_interactions.vb:6402-6409 | Tomodachi Life Save Editor/TLSE_interactions.vb:6410-6417 | Tomodachi Life Save Editor/TLSE_interactions.vb:6418-6425 | Tomodachi Life Save Editor/TLSE_interactions.vb:6426-6433 | Tomodachi Life Save Editor/TLSE_interactions.vb:6434-6441 — all 36 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 15) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80017— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:80017-80024 | Tomodachi Life Save Editor/TLSE_concertedit.vb:110-117 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:64-71 | Tomodachi Life Save Editor/TLSE_creaislandranking.vb:81-88 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:183-190 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:133-140 | Tomodachi Life Save Editor/TLSE_extras.vb:83-90 | Tomodachi Life Save Editor/TLSE_hub.vb:738-745 | Tomodachi Life Save Editor/TLSE_interactions.vb:583-590 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:118-125 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:93-100 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:84-91 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:81-88 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:81-88 | Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:82-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 15 call sites, so a change lands once.
Duplicated block (8 lines × 12) Tomodachi Life Save Editor/TLSE_concertedit.vb:135— Tomodachi Life Save Editor/TLSE_concertedit.vb:135-142 | Tomodachi Life Save Editor/TLSE_concertedit.vb:143-150 | Tomodachi Life Save Editor/TLSE_concertedit.vb:151-158 | Tomodachi Life Save Editor/TLSE_concertedit.vb:159-166 | Tomodachi Life Save Editor/TLSE_concertedit.vb:167-174 | Tomodachi Life Save Editor/TLSE_concertedit.vb:175-182 | Tomodachi Life Save Editor/TLSE_concertedit.vb:183-190 | Tomodachi Life Save Editor/TLSE_concertedit.vb:191-198 | Tomodachi Life Save Editor/TLSE_concertedit.vb:199-206 | Tomodachi Life Save Editor/TLSE_concertedit.vb:207-214 | Tomodachi Life Save Editor/TLSE_concertedit.vb:215-222 | Tomodachi Life Save Editor/TLSE_concertedit.vb:223-230 — all 12 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 2) Tomodachi Life Save Editor/TLSE_dataislandranking.vb:2201— Tomodachi Life Save Editor/TLSE_dataislandranking.vb:2201-2205 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:1405-1409 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 3) Tomodachi Life Save Editor/TLSE_creaislandranking.vb:427— Tomodachi Life Save Editor/TLSE_creaislandranking.vb:427-432 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:2200-2205 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:1404-1409 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (7 lines × 15) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20038— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20038-20044 | Tomodachi Life Save Editor/TLSE_concertedit.vb:69-75 | Tomodachi Life Save Editor/TLSE_crcxmodem.vb:40-46 | Tomodachi Life Save Editor/TLSE_creaislandranking.vb:40-46 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:142-148 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:92-98 | Tomodachi Life Save Editor/TLSE_extras.vb:42-48 | Tomodachi Life Save Editor/TLSE_hub.vb:39-45 | Tomodachi Life Save Editor/TLSE_interactions.vb:542-548 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:77-83 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:52-58 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:43-49 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:40-46 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:40-46 | Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:41-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 15 call sites, so a change lands once.
Duplicated block (7 lines × 13) Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20070— Tomodachi Life Save Editor/TLSE_Jrelationships.vb:20070-20076 | Tomodachi Life Save Editor/TLSE_concertedit.vb:100-106 | Tomodachi Life Save Editor/TLSE_creaislandranking.vb:71-77 | Tomodachi Life Save Editor/TLSE_dataislandranking.vb:173-179 | Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:123-129 | Tomodachi Life Save Editor/TLSE_extras.vb:73-79 | Tomodachi Life Save Editor/TLSE_interactions.vb:573-579 | Tomodachi Life Save Editor/TLSE_islandconfig.vb:108-114 | Tomodachi Life Save Editor/TLSE_islandinfo.vb:83-89 | Tomodachi Life Save Editor/TLSE_islandsettings.vb:74-80 | Tomodachi Life Save Editor/TLSE_issueslegends.vb:71-77 | Tomodachi Life Save Editor/TLSE_itemsedit.vb:71-77 | Tomodachi Life Save Editor/TLSE_itemsprovenance.vb:72-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 13 call sites, so a change lands once.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Orphaned file Tomodachi Life Save Editor/TLSE_miifoods.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_interactions.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_miiprofile.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_travelers_status.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_miiinventory.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_miistatus.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_extras.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_voicepersonnality.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_dataislandranking.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_itemsedit.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_manag_mii.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_manag_travelers.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_datamiiexchange.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_crcxmodem.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Version 4.0.0/Tomodachi-Life-Save-Editor/Advanceitemsedit.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_islandconfig.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_hub.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_repairsave.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_islandinfo.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_manag_allmiis.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_concertedit.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Version 4.0.0/Tomodachi-Life-Save-Editor/Miimusic_edit.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_creaislandranking.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_islandsettings.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file Tomodachi Life Save Editor/TLSE_settings.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 4 more in this group — see findings.md.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file Tomodachi Life Save Editor/TLSE_relationships.vb:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Tomodachi Life Save Editor/TLSE_Jrelationships.vb:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file Version 4.0.0/Tomodachi-Life-Save-Editor/Form1.vb:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
Dormant codebase — 32 of 32 significant files have no living knowledge — the codebase as a whole is dormant, not 32 separate risks. Counted over 32 of the 37 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
Thin README — The root README is 79 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a1793c-0d35-7c43-9d40-8c377882d576 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 47 · Warnings: 2826 · Recommendations: 41 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 17:22 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.